[cisco-voip] Callmanager TomCat

[Jason Aarons (AM)]

Tomcat was signed by Enterprise Root that clients have.  The Jabber 10.5 with cisco_uds you must be FQDN under CCMAdmin > System > Server for everything, all.

From: Chris Ward (chrward) [mailto:chrward at cisco.com] CCM
Sent: Wednesday, October 29, 2014 2:40 PM
To: Jason Aarons (AM); cisco-voip (cisco-voip at puck.nether.net)
Subject: RE: Callmanager TomCat

IP/Hostname isn't the issue. It's the self-signed certificate that CUCM/IMP is using.

The fix is either to get a cert signed by a publicly trusted cert authority like GoDaddy or Verisign OR you need a CA on the local network (AD) that the Windows system trusts (has the root cert loaded) and use that to generate a new cert for CUCM.

The latter is free except for time and allows a little more flexibility.

+Chris
TME - MediaSense and Unity Connection

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Wednesday, October 29, 2014 1:47 PM
To: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] Callmanager TomCat

Customer is asking if they can leave CallManager > CCMAdmin > Server >  IP address and change the Tomcat Certificate to IP Address for Jabber for Windows client to be happy and not prompt an error first time opening?  Can you even do that in CUCM? So keep the ip address as the Subject Alternate Name?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141029/72f44238/attachment.html>