[cisco-voip] ILS multiple Hubs with SME
hi all, bit unclear about having a primary and secondary hubs for a single spoke in ILS. with us - there are ( or will be ) SMEs acting as Hubs for their region. have seen a leaf can point to redundant SME in case of a failure but if you run ILS on top of that - then similarly we can have a redundant HUB in the far side SME. thanks PS. when go to the configuration - can see step 1. configure hub step 2. configure additional hubs does that mean hubs from different cluster or same -- ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] Prompt change on unsuccessful transfer from Call handler
Hi all, CUC 10.5.1.1-7 I have a system call handler and have enabled the during greeting option of Allow Transfers to Numbers Not Associated with Users or Call Handlers [cid:image001.png@01D0CF83.FA0CC270] The problem we are experiencing is when the caller enters a extension number during the prompt that is engaged/busy and they don’t have a voicemail box the caller is played the prompt “You cannot be transferred to this number, check the number and try again”. So the end users keep trying the same number. I can’t seem to find out where that specific prompt is recorded to amend to a custom recording stating the number could be busy. Thanks in advance Regards Matthew ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] clarification on devices of same Jabber type
Correct, you can have multiple devices register the same CSF, BOT, TAB, etc device just don’t have them running at the same time. Nothing good happens when apps fight over the registration. -Ryan On Aug 4, 2015, at 5:02 PM, Lelio Fulgenzi le...@uoguelph.camailto:le...@uoguelph.ca wrote: I guess, technically, they can have multiple devices of each type, but only one logged in at a time. Sent from my iPhone On Aug 4, 2015, at 4:29 PM, Matthew Loraditch mloradi...@heliontechnologies.commailto:mloradi...@heliontechnologies.com wrote: Yes you are correct, one CSF, TCT, TAB and BOT per user. The only time this is really a problem is If you have both types of tablets. I believe they are thinking about working on this but not a priority. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA Network Engineer Direct Voice: 443.541.1518 Facebookhttps://www.facebook.com/heliontech?ref=hl | Twitterhttps://twitter.com/HelionTech | LinkedInhttps://www.linkedin.com/company/helion-technologies?trk=top_nav_home | G+https://plus.google.com/+Heliontechnologies/posts From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lelio Fulgenzi Sent: Tuesday, August 4, 2015 4:21 PM To: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net Subject: [cisco-voip] clarification on devices of same Jabber type I'm pretty sure that multiple devices of the same Jabber type are not supported, but I did a quick search, and found this information from the v10 deployment guide: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_voice_and_video_communication.html#JABI_RF_T95996B7_00 Can represent only one device. If a single user has Cisco Jabber on multiple devices (for example, an iPhone and an iPod Touch), configure separate Cisco Dual Mode for iPhone devices for each in Cisco Unified Communications Manager. It has something similar for BOT devices... Can represent only one device. If a single user has Cisco Jabber for Android on multiple devices, configure separate Cisco Dual Mode for Android devices for each in Cisco Unified Communications Manager. But when I try to find the same information in the v11 deployment guide, it doesn't mention this ability at all. Weirder even, when I look at the 10.6 PDF, the paragraphs are gone. So as far as I can tell, a user can have a maximum ONE of each Jabber type installed, so, one TCT (iphone or ipod), one BOT (android phone), one TAB (android tablet or iPad). I understand that people have managed to configure a second android phone as an android tablet, but that reduces the features. Am I on the right track here? Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.camailto:le...@uoguelph.ca www.uoguelph.ca/ccshttp://www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ___ 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 https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Prompt change on unsuccessful transfer from Call handler
Most if not all of the system default prompts are stored in the local filesystem and can’t be accessed without root permission. These prompts (two different files play to form that message) are two of those /PHGreet/ .wav files and cannot be changed. Unfortunately I’m unware of any method for changing this specific behavior aside from replacing the files by hand with a file using the same name via root - a request I worked on for a customer once…. Once ☺ Of course the files are overwritten after a patch or upgrade and I doubt TAC would assist with this again (but I can be wrong…) Daniel From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Matthew Collins Sent: Wednesday, August 05, 2015 8:40 AM To: cisco-voip@puck.nether.net Subject: [cisco-voip] Prompt change on unsuccessful transfer from Call handler Hi all, CUC 10.5.1.1-7 I have a system call handler and have enabled the during greeting option of Allow Transfers to Numbers Not Associated with Users or Call Handlers [cid:image001.png@01D0CF62.8CD1D1D0] The problem we are experiencing is when the caller enters a extension number during the prompt that is engaged/busy and they don’t have a voicemail box the caller is played the prompt “You cannot be transferred to this number, check the number and try again”. So the end users keep trying the same number. I can’t seem to find out where that specific prompt is recorded to amend to a custom recording stating the number could be busy. Thanks in advance Regards Matthew ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] ILS multiple Hubs with SME
That configuration is on one hub cluster to add another hub cluster for connecting SME clusters in different regions. On Wed, Aug 5, 2015 at 7:39 AM, abbas Wali abba...@gmail.com wrote: hi all, bit unclear about having a primary and secondary hubs for a single spoke in ILS. with us - there are ( or will be ) SMEs acting as Hubs for their region. have seen a leaf can point to redundant SME in case of a failure but if you run ILS on top of that - then similarly we can have a redundant HUB in the far side SME. thanks PS. when go to the configuration - can see step 1. configure hub step 2. configure additional hubs does that mean hubs from different cluster or same -- ___ 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] jabber directory lookup attributes (UDS)
Trying to find a way around the way telephone numbers are stored in our Active Directory so Jabber users can search by DN. Right now, we're using UDS so that way the experience is the same on premise and off-premise. CUCM is LDAP integrated with Active Directory. Unfortunately, our telephone numbers are stored as follows: +1-NPA-NXX- xY. (small x is a literal x, big X and Y are 0-9) The dashes and blank are ignored, but the little x is interpreted as a 9, so in Jabber, a directory search using the user name shows +1NPANXX9Y For the most part, I can build dial rules to work around this, dropping a whole bunch of digits before dialing so that way only the extension is dialed. But searching for extensions is gonna be almost impossible since I can't write a directory lookup rule to include the spaces, etc. I'd like to be able to use the other attributes mentioned here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00 I'm just wondering if I simply use otherTelephone and otherTelephone in the custom LDAP synchronization fields. Will it only take the first one? Anyone else play with this? 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 ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] jabber directory lookup attributes (UDS)
Thanks Justin, I'm gathering options, so that might definitely be a possibility. Not sure how I would handle that though, basically, having to create a new LDAP sync without deleting the existing users. I'm also trying to resolve how Jabber does a search on the UDS contacts with an inbound caller ID (extension). Apparently, that's the only time the directory lookup rules are used? ugh. this was supposed to be easy. :) 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: Justin Steinberg jsteinb...@gmail.com To: Lelio Fulgenzi le...@uoguelph.ca Cc: cisco-voip@puck.nether.net Sent: Wednesday, August 5, 2015 2:29:12 PM Subject: Re: [cisco-voip] jabber directory lookup attributes (UDS) someone correct my if I'm wrong, but I don't think Jabber will search any of the custom LDAP attributes as part of cucm dirsync. I would recommend configuring your directory numbers in AD in the ipPhone field in the format Y. then change your cucm dirsync so that cucm imports the ipPhone field into CUCM as the CUCM telephone number. that why you won't need any dial rules or lookup rules for this setup. On Wed, Aug 5, 2015 at 10:54 AM, Lelio Fulgenzi le...@uoguelph.ca wrote: Trying to find a way around the way telephone numbers are stored in our Active Directory so Jabber users can search by DN. Right now, we're using UDS so that way the experience is the same on premise and off-premise. CUCM is LDAP integrated with Active Directory. Unfortunately, our telephone numbers are stored as follows: +1-NPA-NXX- xY. (small x is a literal x, big X and Y are 0-9) The dashes and blank are ignored, but the little x is interpreted as a 9, so in Jabber, a directory search using the user name shows +1NPANXX9Y For the most part, I can build dial rules to work around this, dropping a whole bunch of digits before dialing so that way only the extension is dialed. But searching for extensions is gonna be almost impossible since I can't write a directory lookup rule to include the spaces, etc. I'd like to be able to use the other attributes mentioned here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00 I'm just wondering if I simply use otherTelephone and otherTelephone in the custom LDAP synchronization fields. Will it only take the first one? Anyone else play with this? 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 ___ 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] jabber directory lookup attributes (UDS)
I can’t remember when this was added, it might be in 9, but I know in 10+ you can temporarily convert everyone back to local users and then redo the sync. That would make sure no one got deleted. When and how you can do that depends on how heavily dependent you are on that ldap information. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA Network Engineer Direct Voice: 443.541.1518 Facebookhttps://www.facebook.com/heliontech?ref=hl | Twitterhttps://twitter.com/HelionTech | LinkedInhttps://www.linkedin.com/company/helion-technologies?trk=top_nav_home | G+https://plus.google.com/+Heliontechnologies/posts From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lelio Fulgenzi Sent: Wednesday, August 5, 2015 3:40 PM To: Justin Steinberg jsteinb...@gmail.com Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] jabber directory lookup attributes (UDS) Thanks Justin, I'm gathering options, so that might definitely be a possibility. Not sure how I would handle that though, basically, having to create a new LDAP sync without deleting the existing users. I'm also trying to resolve how Jabber does a search on the UDS contacts with an inbound caller ID (extension). Apparently, that's the only time the directory lookup rules are used? ugh. this was supposed to be easy. :) Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.camailto:le...@uoguelph.ca www.uoguelph.ca/ccshttp://www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 From: Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com To: Lelio Fulgenzi le...@uoguelph.camailto:le...@uoguelph.ca Cc: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net Sent: Wednesday, August 5, 2015 2:29:12 PM Subject: Re: [cisco-voip] jabber directory lookup attributes (UDS) someone correct my if I'm wrong, but I don't think Jabber will search any of the custom LDAP attributes as part of cucm dirsync. I would recommend configuring your directory numbers in AD in the ipPhone field in the format Y. then change your cucm dirsync so that cucm imports the ipPhone field into CUCM as the CUCM telephone number.that why you won't need any dial rules or lookup rules for this setup. On Wed, Aug 5, 2015 at 10:54 AM, Lelio Fulgenzi le...@uoguelph.camailto:le...@uoguelph.ca wrote: Trying to find a way around the way telephone numbers are stored in our Active Directory so Jabber users can search by DN. Right now, we're using UDS so that way the experience is the same on premise and off-premise. CUCM is LDAP integrated with Active Directory. Unfortunately, our telephone numbers are stored as follows: +1-NPA-NXX- xY. (small x is a literal x, big X and Y are 0-9) The dashes and blank are ignored, but the little x is interpreted as a 9, so in Jabber, a directory search using the user name shows +1NPANXX9Y For the most part, I can build dial rules to work around this, dropping a whole bunch of digits before dialing so that way only the extension is dialed. But searching for extensions is gonna be almost impossible since I can't write a directory lookup rule to include the spaces, etc. I'd like to be able to use the other attributes mentioned here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00 I'm just wondering if I simply use otherTelephone and otherTelephone in the custom LDAP synchronization fields. Will it only take the first one? Anyone else play with this? Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354tel:519%E2%80%90824%E2%80%904120%20Ext%2056354 le...@uoguelph.camailto:le...@uoguelph.ca www.uoguelph.ca/ccshttp://www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ___ 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 https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] jabber directory lookup attributes (UDS)
Yes you can just delete the ldap directory authentication and rebuild it with the new telephone number mapping. the users wont disappear (even though it will warn you they will). that should take care of the inbound caller ID extension mapping as well. On Wed, Aug 5, 2015 at 3:46 PM, Matthew Loraditch mloradi...@heliontechnologies.com wrote: I can’t remember when this was added, it might be in 9, but I know in 10+ you can temporarily convert everyone back to local users and then redo the sync. That would make sure no one got deleted. When and how you can do that depends on how heavily dependent you are on that ldap information. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA Network Engineer Direct Voice: 443.541.1518 Facebook https://www.facebook.com/heliontech?ref=hl | Twitter https://twitter.com/HelionTech | LinkedIn https://www.linkedin.com/company/helion-technologies?trk=top_nav_home | G+ https://plus.google.com/+Heliontechnologies/posts *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Lelio Fulgenzi *Sent:* Wednesday, August 5, 2015 3:40 PM *To:* Justin Steinberg jsteinb...@gmail.com *Cc:* cisco-voip@puck.nether.net *Subject:* Re: [cisco-voip] jabber directory lookup attributes (UDS) Thanks Justin, I'm gathering options, so that might definitely be a possibility. Not sure how I would handle that though, basically, having to create a new LDAP sync without deleting the existing users. I'm also trying to resolve how Jabber does a search on the UDS contacts with an inbound caller ID (extension). Apparently, that's the only time the directory lookup rules are used? ugh. this was supposed to be easy. :) 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: *Justin Steinberg jsteinb...@gmail.com *To: *Lelio Fulgenzi le...@uoguelph.ca *Cc: *cisco-voip@puck.nether.net *Sent: *Wednesday, August 5, 2015 2:29:12 PM *Subject: *Re: [cisco-voip] jabber directory lookup attributes (UDS) someone correct my if I'm wrong, but I don't think Jabber will search any of the custom LDAP attributes as part of cucm dirsync. I would recommend configuring your directory numbers in AD in the ipPhone field in the format Y. then change your cucm dirsync so that cucm imports the ipPhone field into CUCM as the CUCM telephone number.that why you won't need any dial rules or lookup rules for this setup. On Wed, Aug 5, 2015 at 10:54 AM, Lelio Fulgenzi le...@uoguelph.ca wrote: Trying to find a way around the way telephone numbers are stored in our Active Directory so Jabber users can search by DN. Right now, we're using UDS so that way the experience is the same on premise and off-premise. CUCM is LDAP integrated with Active Directory. Unfortunately, our telephone numbers are stored as follows: +1-NPA-NXX- xY. (small x is a literal x, big X and Y are 0-9) The dashes and blank are ignored, but the little x is interpreted as a 9, so in Jabber, a directory search using the user name shows +1NPANXX9Y For the most part, I can build dial rules to work around this, dropping a whole bunch of digits before dialing so that way only the extension is dialed. But searching for extensions is gonna be almost impossible since I can't write a directory lookup rule to include the spaces, etc. I'd like to be able to use the other attributes mentioned here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00 I'm just wondering if I simply use otherTelephone and otherTelephone in the custom LDAP synchronization fields. Will it only take the first one? Anyone else play with this? Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 519%E2%80%90824%E2%80%904120%20Ext%2056354 le...@uoguelph.ca www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ___ 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] jabber directory lookup attributes (UDS)
I’d highly recommend you dedicate a VM for lab testing so you can validate things like this in a non-production environment. I’m pretty sure 10 is where the local + ldap users was added and I’m pretty sure they get converted automatically when the ldap agreement is removed. -Ryan On Aug 5, 2015, at 3:49 PM, Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote: Yes you can just delete the ldap directory authentication and rebuild it with the new telephone number mapping. the users wont disappear (even though it will warn you they will). that should take care of the inbound caller ID extension mapping as well. On Wed, Aug 5, 2015 at 3:46 PM, Matthew Loraditch mloradi...@heliontechnologies.commailto:mloradi...@heliontechnologies.com wrote: I can’t remember when this was added, it might be in 9, but I know in 10+ you can temporarily convert everyone back to local users and then redo the sync. That would make sure no one got deleted. When and how you can do that depends on how heavily dependent you are on that ldap information. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA Network Engineer Direct Voice: 443.541.1518tel:443.541.1518 Facebookhttps://www.facebook.com/heliontech?ref=hl | Twitterhttps://twitter.com/HelionTech | LinkedInhttps://www.linkedin.com/company/helion-technologies?trk=top_nav_home | G+https://plus.google.com/+Heliontechnologies/posts From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lelio Fulgenzi Sent: Wednesday, August 5, 2015 3:40 PM To: Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com Cc: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net Subject: Re: [cisco-voip] jabber directory lookup attributes (UDS) Thanks Justin, I'm gathering options, so that might definitely be a possibility. Not sure how I would handle that though, basically, having to create a new LDAP sync without deleting the existing users. I'm also trying to resolve how Jabber does a search on the UDS contacts with an inbound caller ID (extension). Apparently, that's the only time the directory lookup rules are used? ugh. this was supposed to be easy. :) Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.camailto:le...@uoguelph.ca www.uoguelph.ca/ccshttp://www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 From: Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com To: Lelio Fulgenzi le...@uoguelph.camailto:le...@uoguelph.ca Cc: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net Sent: Wednesday, August 5, 2015 2:29:12 PM Subject: Re: [cisco-voip] jabber directory lookup attributes (UDS) someone correct my if I'm wrong, but I don't think Jabber will search any of the custom LDAP attributes as part of cucm dirsync. I would recommend configuring your directory numbers in AD in the ipPhone field in the format Y. then change your cucm dirsync so that cucm imports the ipPhone field into CUCM as the CUCM telephone number.that why you won't need any dial rules or lookup rules for this setup. On Wed, Aug 5, 2015 at 10:54 AM, Lelio Fulgenzi le...@uoguelph.camailto:le...@uoguelph.ca wrote: Trying to find a way around the way telephone numbers are stored in our Active Directory so Jabber users can search by DN. Right now, we're using UDS so that way the experience is the same on premise and off-premise. CUCM is LDAP integrated with Active Directory. Unfortunately, our telephone numbers are stored as follows: +1-NPA-NXX- xY. (small x is a literal x, big X and Y are 0-9) The dashes and blank are ignored, but the little x is interpreted as a 9, so in Jabber, a directory search using the user name shows +1NPANXX9Y For the most part, I can build dial rules to work around this, dropping a whole bunch of digits before dialing so that way only the extension is dialed. But searching for extensions is gonna be almost impossible since I can't write a directory lookup rule to include the spaces, etc. I'd like to be able to use the other attributes mentioned here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00 I'm just wondering if I simply use otherTelephone and otherTelephone in the custom LDAP synchronization fields. Will it only take the first one? Anyone else play with this? Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354tel:519%E2%80%90824%E2%80%904120%20Ext%2056354 le...@uoguelph.camailto:le...@uoguelph.ca www.uoguelph.ca/ccshttp://www.uoguelph.ca/ccs Room 037, Animal
Re: [cisco-voip] clarification on devices of same Jabber type
You can have multiple devices on the same device profile. For example I can have multiple PCs logged in Jabber but only one Jabber can have the phone control. -YX On Wed, Aug 5, 2015 at 6:51 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Correct, you can have multiple devices register the same CSF, BOT, TAB, etc device just don’t have them running at the same time. Nothing good happens when apps fight over the registration. -Ryan On Aug 4, 2015, at 5:02 PM, Lelio Fulgenzi le...@uoguelph.ca wrote: I guess, technically, they can have multiple devices of each type, but only one logged in at a time. Sent from my iPhone On Aug 4, 2015, at 4:29 PM, Matthew Loraditch mloradi...@heliontechnologies.com wrote: Yes you are correct, one CSF, TCT, TAB and BOT per user. The only time this is really a problem is If you have both types of tablets. I believe they are thinking about working on this but not a priority. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA Network Engineer Direct Voice: 443.541.1518 Facebook https://www.facebook.com/heliontech?ref=hl | Twitter https://twitter.com/HelionTech | LinkedIn https://www.linkedin.com/company/helion-technologies?trk=top_nav_home | G+ https://plus.google.com/+Heliontechnologies/posts *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net cisco-voip-boun...@puck.nether.net] *On Behalf Of *Lelio Fulgenzi *Sent:* Tuesday, August 4, 2015 4:21 PM *To:* cisco-voip@puck.nether.net *Subject:* [cisco-voip] clarification on devices of same Jabber type I'm pretty sure that multiple devices of the same Jabber type are not supported, but I did a quick search, and found this information from the v10 deployment guide: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_voice_and_video_communication.html#JABI_RF_T95996B7_00 *Can represent only one device. If a single user has Cisco Jabber on multiple devices (for example, an iPhone and an iPod Touch), configure separate Cisco Dual Mode for iPhone devices for each in Cisco Unified Communications Manager.* It has something similar for BOT devices... *Can represent only one device. If a single user has Cisco Jabber for Android on multiple devices, configure separate Cisco Dual Mode for Android devices for each in Cisco Unified Communications Manager.* But when I try to find the same information in the v11 deployment guide, it doesn't mention this ability at all. Weirder even, when I look at the 10.6 PDF, the paragraphs are gone. So as far as I can tell, a user can have a maximum ONE of each Jabber type installed, so, one TCT (iphone or ipod), one BOT (android phone), one TAB (android tablet or iPad). I understand that people have managed to configure a second android phone as an android tablet, but that reduces the features. Am I on the right track here? 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 ___ 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 mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Unable to switch to Jabber soft-phone
Cisco TAC told my colleague that it’s configured correctly. They are still troubleshooting apparently. Will let you guys know if they get it sorted. From: Charles Goldsmith [mailto:wo...@justfamily.org] Sent: Wednesday, 5 August 2015 12:36 AM To: Tong, Dana dana.t...@team.telstra.com Cc: Cisco VOIP cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Unable to switch to Jabber soft-phone Owner User-ID set correctly on the CSF? Primary Extension set? If they are on 9 or higher, is their service profile set correctly? Have you tried deleting and rebuilding the CSF? HTH On Tue, Aug 4, 2015 at 3:10 AM, Tong, Dana dana.t...@team.telstra.commailto:dana.t...@team.telstra.com wrote: Hi all, A colleague of mine has setup Jabber / CUCM, with IMP etc. Jabber can sign in ok and deskphone control etc is all fine. We can’t however switch to soft-phone mode. Jabber reports the following error: CJ:109:3 The CSF device is created and is a controlled device on the end user. Do you have any advice on what to look for in the PRT to see where the problem might be? I’ve checked everything I can think of and the CSF / and user settings are all ok. Cheers Dana ___ 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 https://puck.nether.net/mailman/listinfo/cisco-voip
