Cisco Bug: CSCul50916 - Improve UDS scalability
May 04, 2016
- Cisco Jabber for Windows
Known Affected Releases
Symptom: If a Jabber user does a search for a contact, it's possible that the search will come back with no results. This can be intermittent. So, for example 3 out of 50 searches might come back empty. It is possible that the cache will not refresh because the UDS requests to refresh the cache could be ignored. If this happens, it is possible that a phone number could become out of sync. For example, I change my cell phone number in AD. Someone tries to call me and doesn't have my updated number because their cache did not get my new phone number yet. Conditions: UDS will start to throttle requests form devices when it has too many to handle. UDS has a buffer so that it throttles requests long before Call Control would be affected to ensure that Call Control is always up. Cisco recommends no more than 200 Jabber clients to connect to CUCM using UDS at any given time. More than 200 active Jabber clients could result in UDS requests not being processed.
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