Preview Tool

Cisco Bug: CSCup74253 - Jabber for windows 9.7 UDS service discovery fails with Hardphone

Last Modified

Feb 13, 2018

Products (1)

  • Cisco UC Integration(TM) for Microsoft Lync

Known Affected Releases


Description (partial)

Jabber for Windows not able to login with service discovery and UDS directory connection selected on the service profile selected for the user (no system default profile selected) and ONLY controlling Hardphone for that user.

With the following setup Service discovery fails and user has to manually login in Jabber specifying the IP address of the CUP server
Service Discovery method : _cisco-uds or _cuplogin
Directory connection type : UDS selected on service profile for the jabber user (no XML used)
CUCM and CUP version :  9.1.2
Jabber version:9.7.0 and 9.7.1
End user page in CUCM : under controlled Devices only a Hardphone is selected with owner user id populated on device page of the phone in CUCM.

Related Community Discussions

J4W 10.5 Login only works for users with associated device
Hi all,   I just discovered that using J4W 10.5 and service autodiscovery, the login only works if the user has an Device associated. Means that login is not possible if the user has only a controlled device profile.   We are using 10.5.1 Build 43318 - Is this a known Bug, or is this working with a different version?   Regards, Peter  
Latest activity: Dec 01, 2014
Bug details contain sensitive information and therefore require a 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.