[cisco-voip] 2 different jabber TCT devices for one CUWL Standard User
Hi all, what would be the effect of creating 2 different TCT devices, assigning the same owner and associating this end user with both devices? Assume that ELM has a CUWL standard license available and the platforms are Cisco IM P 9.1 and CUCM 9.1. The idea is to have 2 different jabber numbers: one for an iphone for US one for an iphone for Europe. Cheers, Anthony ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] Changing CUCM SystemServer from IP to FQDN
Is anyone using CUCM deployments where they set the SystemServer value to the FQDN of the CUCM nodes ? I'm in the process of deploying Jabber for Windows 9.6+ with Collaboration Edge, and there are requirements around certificate validation that seem to require the CUCM SystemServer value set to a FQDN. I'm concerned around making this change and curious if others are using FQDN. ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Changing CUCM SystemServer from IP to FQDN
Using FQDN in System-Server on UCM is specifically not supported in the Collab Edge deployment guide I'm looking at. It's ok to use a hostname there but it must be resolvable by the Expressway-C (and the phones of course). -Ryan On Feb 18, 2014, at 11:36 AM, Erick Wellnitz ewellnitzv...@gmail.commailto:ewellnitzv...@gmail.com wrote: We were but it interferes with EMCC. The phone only does DNS lookups for the domain it is assigned so we switched back to IP addreses. On Tue, Feb 18, 2014 at 8:39 AM, Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote: Is anyone using CUCM deployments where they set the SystemServer value to the FQDN of the CUCM nodes ? I'm in the process of deploying Jabber for Windows 9.6+ with Collaboration Edge, and there are requirements around certificate validation that seem to require the CUCM SystemServer value set to a FQDN. I'm concerned around making this change and curious if others are using FQDN. ___ 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 https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] 2 different jabber TCT devices for one CUWL Standard User
It wouldn't do what I think you're trying to do. Is it possible to put both dn's on the same dual mode profile? Sent from my iPad On Feb 17, 2014, at 1:53 PM, Anthony Kouloglou ak...@dataways.gr wrote: Hi all, what would be the effect of creating 2 different TCT devices, assigning the same owner and associating this end user with both devices? Assume that ELM has a CUWL standard license available and the platforms are Cisco IM P 9.1 and CUCM 9.1. The idea is to have 2 different jabber numbers: one for an iphone for US one for an iphone for Europe. Cheers, Anthony ___ 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] Changing CUCM SystemServer from IP to FQDN
What document is that? The reason for changing the systemserver to fqdn is more because of the Jabber for Windows certificate validation process than for CE. That being said, if Jabber wants FQDN and Collab Edge doesn't, we will have a problem. On Feb 18, 2014 2:45 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Using FQDN in System-Server on UCM is specifically not supported in the Collab Edge deployment guide I'm looking at. It's ok to use a hostname there but it must be resolvable by the Expressway-C (and the phones of course). -Ryan On Feb 18, 2014, at 11:36 AM, Erick Wellnitz ewellnitzv...@gmail.com wrote: We were but it interferes with EMCC. The phone only does DNS lookups for the domain it is assigned so we switched back to IP addreses. On Tue, Feb 18, 2014 at 8:39 AM, Justin Steinberg jsteinb...@gmail.comwrote: Is anyone using CUCM deployments where they set the SystemServer value to the FQDN of the CUCM nodes ? I'm in the process of deploying Jabber for Windows 9.6+ with Collaboration Edge, and there are requirements around certificate validation that seem to require the CUCM SystemServer value set to a FQDN. I'm concerned around making this change and curious if others are using FQDN. ___ 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] Changing CUCM SystemServer from IP to FQDN
The doc I have is a draft version so may be subject to change. What is directing you to use the FQDN for helping jabber validate certs? I don't see anything perusing the server setup guide or install guide for 9.6. Sent from my iPhone On Feb 18, 2014, at 8:35 PM, Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote: What document is that? The reason for changing the systemserver to fqdn is more because of the Jabber for Windows certificate validation process than for CE. That being said, if Jabber wants FQDN and Collab Edge doesn't, we will have a problem. On Feb 18, 2014 2:45 PM, Ryan Ratliff (rratliff) rratl...@cisco.commailto:rratl...@cisco.com wrote: Using FQDN in System-Server on UCM is specifically not supported in the Collab Edge deployment guide I'm looking at. It's ok to use a hostname there but it must be resolvable by the Expressway-C (and the phones of course). -Ryan On Feb 18, 2014, at 11:36 AM, Erick Wellnitz ewellnitzv...@gmail.commailto:ewellnitzv...@gmail.com wrote: We were but it interferes with EMCC. The phone only does DNS lookups for the domain it is assigned so we switched back to IP addreses. On Tue, Feb 18, 2014 at 8:39 AM, Justin Steinberg jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote: Is anyone using CUCM deployments where they set the SystemServer value to the FQDN of the CUCM nodes ? I'm in the process of deploying Jabber for Windows 9.6+ with Collaboration Edge, and there are requirements around certificate validation that seem to require the CUCM SystemServer value set to a FQDN. I'm concerned around making this change and curious if others are using FQDN. ___ 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 https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Voip solution for Home Health Care Organization
UC540 would probably do it. but it might be end of sale. or the 18xx router cme/cue. But seriously, they only have 1 POTS line? On Mon, Feb 17, 2014 at 2:33 PM, Grace Maximuangu grace.maximua...@blackbox.com wrote: This is for a small Home Health care practice with just 1 main line and about ten employees, scalable to 20. Can you recommend a Cisco Voip solution for a budget of about $4,500 excluding the IP phones. They are big about auto attendant, Queuing features, basic phone functionality etc..and maybe looking at interconnecting 3 other offices They need to purchase their equipment as soon as possible Tks :-:gm Grace Maximuangu Voice Solutions Engineer *Black Box Network Services* Cell: 213.268.6342 grace.maximua...@blackbox.com www.blackbox.com [image: bbox logo.JPG] -- This email and any files transmitted with it are confidential and are intended for the sole use of the individual to whom they are addressed. Black Box Corporation reserves the right to scan all e-mail traffic for restricted content and to monitor all e-mail in general. If you are not the intended recipient or you have received this email in error, any use, dissemination or forwarding of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email. ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip inline: image001.jpg___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] 2 different jabber TCT devices for one CUWL Standard User
Hi Ryan, I have tried to assign 2 dns for the same dual mode device allthough cisco says thst these devices are single line (for the record, these devices have 6 lines by default!). The result was that these 2 dns would ring on jabber, thus accepting calls, but for the outbound calls it was kind of unpredictable; I couldn't figure out how to choose the line from which I want to call. BR Anthony On February 19, 2014 2:36:34 AM EET, Ryan Huff rthconsulta...@gmail.com wrote: It wouldn't do what I think you're trying to do. Is it possible to put both dn's on the same dual mode profile? Sent from my iPad On Feb 17, 2014, at 1:53 PM, Anthony Kouloglou ak...@dataways.gr wrote: Hi all, what would be the effect of creating 2 different TCT devices, assigning the same owner and associating this end user with both devices? Assume that ELM has a CUWL standard license available and the platforms are Cisco IM P 9.1 and CUCM 9.1. The idea is to have 2 different jabber numbers: one for an iphone for US one for an iphone for Europe. Cheers, Anthony ___ 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
