Cisco Bug: CSCup30905 - UDS service discovery fails with Hardphone
Feb 03, 2017
- Cisco Jabber for Windows
Known Affected Releases
Symptom: 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. Conditions: 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.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases