Guest

Preview Tool

Cisco Bug: CSCut47840 - J4W 10.6 - Protocol for directory UC service in Service Profile is used

Last Modified

Jul 23, 2015

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

10.6(0) 10.6(1)

Description (partial)

Symptom:
With Jabber 10.5, the service profile has priority over jabber-config.xml but the protocol in the directory profile is ignored. If no protocol is defined in the jabber-config.xml file, then the default protocol is TCP.

With Jabber 10.6, the behavior is the same except that the protocol setting in the service profile is being used.

Conditions:
If the Serverport and BDIServerport in Jabber-config.xml are 636 (TLS) and default protocol is TCP in Directory UC Service in service profile, then the directory integration will not work as expected. So, the protocol setting in Directory UC service profile should be set to "TLS"

(i) In Jabber 10.5 - the protocol setting for the directory UC service in Service profile is ignored 
(ii) In Jabber 10.6.x - protocol setting for the directory UC service in Service profile is used
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.