[cisco-voip] Changing CUCM System>Server from IP to FQDN

[Heim, Dennis]

I have usually just put the hostname, but if you have ip domain name configured, when it generates the certificate signed request (CSR), it will set the subject name to the FQDN. I always make sure that the CA add the following Subject Alternative Names(1) DNS:<hostname> (2) DNS:<IP-Address>.

Dennis Heim | Solution Architect (Collaboration)
World Wide Technology, Inc. | 314-212-1814

PS Engineering:  Innovate & Ignite.


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Tuesday, February 18, 2014 10:18 AM
To: Justin Steinberg; Cisco VOIP
Subject: Re: [cisco-voip] Changing CUCM System>Server from IP to FQDN

I would think it would be easier to import CallManagers certs into AD’s trust list.  I assume these computers are part of the domain.  This won’t work for Jabber for Mac, etc that are not part of the domain.

About to go down this road for a customer.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Justin Steinberg
Sent: Tuesday, February 18, 2014 9:39 AM
To: Cisco VOIP
Subject: [cisco-voip] Changing CUCM System>Server from IP to FQDN


Is anyone using CUCM deployments where they set the System>Server 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 System>Server value set to a FQDN.

I'm concerned around making this change and curious if others are using FQDN.


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140218/0839eafd/attachment.html>