Guest

Preview Tool

Cisco Bug: CSCur75757 - FQDN in place of hostname in CUCM

Last Modified

Feb 12, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

9.1(2.12900.11)

Description (partial)

Symptom:
On using applications such as Jabber in an external domain which uses the host name as a method to identify the CUCM the Jabber client is unable to identify the domain of the CUCM as the CUCM sends only its host-name in the UDS response.

Changing the CUCM host name to its FQDN in the System > Servers page resolves the issue considering we have proper forward and reverse DNS lookup.

Conditions:
Using an external application like Jabber that requires the hostname/ FQDN resolution rather than the IP address.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.