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

[Justin Steinberg]

What document is that?

The reason for changing the system>server 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)" <rratliff at 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 <ewellnitzvoip at 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 <jsteinberg at gmail.com>wrote:
>
>>  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.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>  _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140218/5c2b58a9/attachment.html>