Re: [cisco-voip] COBRAS import PIN issue
Affected probably 20% of users overall - wasn't a universal issue which is why we didn't catch it immediately with our testing. From: Bill Talley [mailto:btal...@gmail.com] Sent: Tuesday, March 04, 2014 9:42 AM To: Salisbury, Charles Cc: Justin Steinberg; Cisco VOIP Subject: Re: [cisco-voip] COBRAS import PIN issue Some users having not changed their PINS affected all users on the system? Sent from an Apple iOS device with very tiny touchscreen input keys. Please excude my typtos. On Mar 4, 2014, at 8:18 AM, Salisbury, Charles charles.salisb...@gentex.commailto:charles.salisb...@gentex.com wrote: I just did an upgrade from 7.1.5 to 9.1(2) and had this exact same issue - TAC traced it to be users that had not changed their PIN for a while. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Justin Steinberg Sent: Monday, March 03, 2014 11:13 PM To: Bill Talley Cc: Cisco VOIP Subject: Re: [cisco-voip] COBRAS import PIN issue I ran into this issue once and tracked it down to the time when the user had last changed/set their pin. In my situation only about 20% of the users were affected. The other 80% were fine. I tracked the issue down by running a user data dump, and all the users that had reported the problem had the last pin changed time of much older than everyone else. In my case, the authentication rules on this system did not expire the pins, so some users had the same pins for years. Instead of rolling back, I opted to run a bulk pin reset to the default for these users and then sent a mass email to all of them telling them that their PIN had been reset. If you don't expire your pins this might be your problem. While I didn't try this, you could go into the current 7 system and set the password policy to force users to change their pin on the next login and let everyone update their pin before you run the upgrade again. I believe the aggravating factor is that the users in question last changed their pin on an older version of connection that used a different encryption type, that is not supported by v9. On Mar 3, 2014 8:57 PM, Bill Talley btal...@gmail.commailto:btal...@gmail.com wrote: I interpreted the issue as being from or to version 7.0 as it also suggests upgrading to 7.1.3 prior (IIRC) to using COBRAS. Sent from an Apple iOS device with very tiny touchscreen input keys. Please excude my typtos. On Mar 3, 2014, at 5:48 PM, Ed Leatherman ealeather...@gmail.commailto:ealeather...@gmail.com wrote: Hello! This weekend I exported some voice mail accounts from Connection 7.0.2 and imported them into 9.1(2) using COBRAS tool. When I did this, the users were not able to sign into their mailbox, as if PIN was changed. Retracing my steps, I did have this in the COBRAS log during the import: [Thread 001], [14/03/02 08:51:34], Updating subscriber phone PIN from Connection backup [Thread 001], [14/03/02 08:51:34], (warning) unable to find mapping for MDBObjectId=051ee60c-4e21-42f6-bea4-9f845e6e96c8, ObjectType=CredentialPolicy in GetNewObjectId on DirectoryBackupDatabaseFunctions.cs Unfortunately I had did not have a whole lot of time to troubleshoot on live 9.1 server - weather emergency dictated that I swing them back the 7.0 version asap so that users could update various greetings and info prompts. Right now i'm working with the 9.1 VM in a isolated network. My hypothesis is that the old system had PIN set to not expire, and the new system has PIN set to expire in 120 days - and this somehow caused the PIN to not get updated somehow. I can't see any other difference related to credential policy. Anyone know if this is the case or why PINs might not have carried over, or if I'm barking up the wrong tree? I had read that there was some issues importing PINs into version 7.0, but exporting from 7.0 TO a version 7.1.3+ was not cited as a problem. Thanks! -- Ed Leatherman THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE AND ANY ATTACHMENTS SENT FROM GENTEX CORPORATION IS GENTEX CONFIDENTIAL INFORMATION INTENDED ONLY FOR THE PERSONAL USE OF THE INDIVIDUAL OR ENTITY NAMED ABOVE. If you are not the intended recipient, you are hereby notified that any review, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail, and delete this e-mail message and any attachments from your computer. ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net
Re: [cisco-voip] COBRAS import PIN issue
Thanks Ed. Because we ran into a problem with passwords during our migration from v4 to v7, we had to force people to change their password . My current version is 7.1(3)ES11, but my inactive version shows 7.1(2)ES3 - this is the version I upgraded to from Unity v4. I suspect that since the majority of people have changed their password within a v7.1 system, my upgrade should be fine. I'll probably post a followup and see what Jeff says. Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.ca www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 - Original Message - From: Ed Leatherman ealeather...@gmail.com To: Lelio Fulgenzi le...@uoguelph.ca Cc: Jason Aarons (AM) jason.aar...@dimensiondata.com, Cisco VOIP cisco-voip@puck.nether.net Sent: Tuesday, March 4, 2014 11:21:57 AM Subject: Re: [cisco-voip] COBRAS import PIN issue I got a pretty good reply from Jeff on my thread: https://supportforums.cisco.com/message/4181654 On Tue, Mar 4, 2014 at 10:40 AM, Lelio Fulgenzi le...@uoguelph.ca wrote: Jason, Can you share the forum thread link? I'd like to post a follow up question to Jeff. Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.ca www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 From: Jason Aarons (AM) jason.aar...@dimensiondata.com To: Charles Salisbury charles.salisb...@gentex.com , Justin Steinberg jsteinb...@gmail.com , Bill Talley btal...@gmail.com Cc: Cisco VOIP cisco-voip@puck.nether.net Sent: Tuesday, March 4, 2014 9:59:45 AM Subject: Re: [cisco-voip] COBRAS import PIN issue From the Cobras developer; Yeah… if you don’t change your PINs for years and port them multiple times without changing them you will have problems… Unity and early versions of Connection and then later versions of Connection all used different hashes or PWs and PINs… nothing any client can do about that – Maybe a separate “everything you ever wanted to know about PINs and passwords” section could pull all that into a single section might help… From: cisco-voip [mailto: cisco-voip-boun...@puck.nether.net ] On Behalf Of Salisbury, Charles Sent: Tuesday, March 04, 2014 9:18 AM To: Justin Steinberg; Bill Talley Cc: Cisco VOIP Subject: Re: [cisco-voip] COBRAS import PIN issue I just did an upgrade from 7.1.5 to 9.1(2) and had this exact same issue – TAC traced it to be users that had not changed their PIN for a while. From: cisco-voip [ mailto:cisco-voip-boun...@puck.nether.net ] On Behalf Of Justin Steinberg Sent: Monday, March 03, 2014 11:13 PM To: Bill Talley Cc: Cisco VOIP Subject: Re: [cisco-voip] COBRAS import PIN issue I ran into this issue once and tracked it down to the time when the user had last changed/set their pin. In my situation only about 20% of the users were affected. The other 80% were fine. I tracked the issue down by running a user data dump, and all the users that had reported the problem had the last pin changed time of much older than everyone else. In my case, the authentication rules on this system did not expire the pins, so some users had the same pins for years. Instead of rolling back, I opted to run a bulk pin reset to the default for these users and then sent a mass email to all of them telling them that their PIN had been reset. If you don't expire your pins this might be your problem. While I didn't try this, you could go into the current 7 system and set the password policy to force users to change their pin on the next login and let everyone update their pin before you run the upgrade again. I believe the aggravating factor is that the users in question last changed their pin on an older version of connection that used a different encryption type, that is not supported by v9. On Mar 3, 2014 8:57 PM, Bill Talley btal...@gmail.com wrote: I interpreted the issue as being from or to version 7.0 as it also suggests upgrading to 7.1.3 prior (IIRC) to using COBRAS. Sent from an Apple iOS device with very tiny touchscreen input keys. Please excude my typtos. On Mar 3, 2014, at 5:48 PM, Ed Leatherman ealeather...@gmail.com wrote: Hello! This weekend I exported some voice mail accounts from Connection 7.0.2 and imported them into 9.1(2) using COBRAS tool. When I did this, the users were not able to sign into their mailbox, as if PIN was changed. Retracing my steps, I did have this in the COBRAS log during the import: [Thread 001], [14/03/02 08:51:34], Updating subscriber phone PIN from Connection backup [Thread 001], [14/03/02 08:51:34], (warning) unable to find mapping for
Re: [cisco-voip] Directory URI in LDAP sync
Just following up on this Erick... After upgrading from v7 to v9, the Directory URI field is blank as you suggest. I thought I could simply add another host in the existing relationship, but that does not work. It looks like I have to create a new directory relationship. Is it dangerous to create two directory relationships to the same active directory source? Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.ca www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 - Original Message - From: Erick B. erick...@gmail.com To: Lelio Fulgenzi le...@uoguelph.ca Cc: cisco-voip voyp list cisco-voip@puck.nether.net Sent: Monday, November 18, 2013 2:46:57 PM Subject: Re: [cisco-voip] Directory URI in LDAP sync After upgrade from 8.x to 9.x, the field is not mapped to LDAP attribute (is blank). You need to add new LDAP directory entry to get that field mapped or go under Call Routing - Directory Number and Directory URI and set each DN and Directory URI setting there. The SIP URI is used for telepresence mainly so people call you at use...@domainname.com from a video device. Still learning this... On Mon, Nov 18, 2013 at 11:27 AM, Lelio Fulgenzi le...@uoguelph.ca wrote: Can anyone comment/elaborate on what the Directory URI is used for in the LDAP sync setup screen in v9? It's set to msRTCSIP-primaryuseraddress by default. Unfortunately it's not modifiable after the relationship is setup and I'm not sure what to set it to. I'll also have to see what value it takes during an upgrade http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_0_1/ccmcfg/CUCM_BK_CDF59AFB_00_admin-guide_chapter_01100.html#CUCM_RF_LE051F5C_00 Sent from my iPhone ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] DTMF from CUEAC
If doing something in the Software I’m guessing it uses JTAPI to send the DTMF, and you need to enable the JTAPI traces. Have you tried using the phone TUI mid-call? From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick Wellnitz Sent: Tuesday, March 04, 2014 2:16 PM To: cisco-voip Subject: [cisco-voip] DTMF from CUEAC Maybe I'm missing something but for the life of me I can't get mid call DTMF to work on CUEAC 9.1.1.10 Tried holding down the control key but no luck. itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] DTMF from CUEAC
Works as expected from the phone. Does it use JTAPI? It has the TSP installed. On Tue, Mar 4, 2014 at 2:27 PM, Jason Aarons (AM) jason.aar...@dimensiondata.com wrote: If doing something in the Software I'm guessing it uses JTAPI to send the DTMF, and you need to enable the JTAPI traces. Have you tried using the phone TUI mid-call? *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Erick Wellnitz *Sent:* Tuesday, March 04, 2014 2:16 PM *To:* cisco-voip *Subject:* [cisco-voip] DTMF from CUEAC Maybe I'm missing something but for the life of me I can't get mid call DTMF to work on CUEAC 9.1.1.10 Tried holding down the control key but no luck. itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] DTMF from CUEAC
Excellent. Thanks fpor the great information. On Tue, Mar 4, 2014 at 2:59 PM, Jamie Gale -X (jamgale - ARC SOLUTIONS INTERNATIONAL LTD at Cisco) jamg...@cisco.com wrote: It used TSP on the server. This is actually a bug in the CUEAC client, if you raise a TAC case and reference the bug ID CSCuj33939, they should be able to get you the fix. Kind Regards Jamie Gale Professional Services Engineer Arc Solutions, onsite at Cisco jamg...@cisco.com On Mar 4, 2014, at 3:43 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Works as expected from the phone. Does it use JTAPI? It has the TSP installed. On Tue, Mar 4, 2014 at 2:27 PM, Jason Aarons (AM) jason.aar...@dimensiondata.com wrote: If doing something in the Software I'm guessing it uses JTAPI to send the DTMF, and you need to enable the JTAPI traces. Have you tried using the phone TUI mid-call? *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Erick Wellnitz *Sent:* Tuesday, March 04, 2014 2:16 PM *To:* cisco-voip *Subject:* [cisco-voip] DTMF from CUEAC Maybe I'm missing something but for the life of me I can't get mid call DTMF to work on CUEAC 9.1.1.10 Tried holding down the control key but no luck. itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] Setting up ICM Sprawler 8.x
I have a couple questions on the ICM Sprawler setup. 1. Does SQL need to be installed on the Sprawler? 2. Can AD/DNS be installed on the Sprawler? Sincerely, Ryan Burtch ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
