Guest

Preview Tool

Cisco Bug: CSCuo36371 - Jabber Windows Administration Guide - mention of DNS requirements needed

Last Modified

Jan 14, 2015

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

9.7(0)

Description (partial)

Symptom:
Incomplete statement about the configuration of directory integration under the CUCM Service Profile for Jabber Windows

Conditions:
If the client machine is not part of the domain and unable to resolve the hostname or FQDN of Jabber servers, Jabber will fail service discovery.

An example from a PC that is able to successfully perform a SRV lookup to CUCM, but is unable to resolve the hostname would look like this:

2014-04-15 17:45:50,541 INFO  [0x000020fc] [cies\ucm9-config\src\DnsProvider.cpp(45)] [csf.config] [ucm90::DnsProvider::initialise] - Initial DNS information:
*------------------------------------*
| ucm-config Library DNS Information
|              DNS Domain: domain.com
|              DNS Record: cucm1.domain.com:8443 [weight: 0, priority: 0]
*------------------------------------*
.
.
.
2014-04-15 17:46:13,011 INFO  [0x000020fc] [netutils\src\http\CurlHttpUtils.cpp(265)] [csf.httpclient] [http::CurlHttpUtils::curlCodeToResult] - curlCode=[6] error message=[Could not resolve host: CUCM1] result=[UNRESOLVED_HOST_ERROR]
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.