Guest

Preview Tool

Cisco Bug: CSCur89604 - Jabber for Windows not using UDS Batch API

Last Modified

Jul 26, 2015

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

10.5(1) 9.7(5)

Description (partial)

Symptom:
Jabber for Windows is not using UDS Batch API for searching.

End result is that Jabber is not able to resolve all contacts because CUCM will be closing off the connections after it receives 40 individual UDS queries from a single client.

This is with CUCM 9 w/ cmterm-uds COP file, so CUCM does support bulk API. With CUCM 10, Jabber does use bulk API

Comparing working vs. non-working scenarios, in non-working Jabber logs:
2014-11-10 06:21:48,429 INFO [0x000002ec] [main\person-uds\UdsServerHelper.cpp(222)] [csf.person.uds] [person::uds::UdsServerHelper::onProcessBatchApiRequestComplete] - Batch API may be supported.

In working Jabber logs:
2014-11-10 06:17:28,054 INFO [0x00000e4c] [main\person-uds\UdsServerHelper.cpp(245)] [csf.person.uds] [person::uds::UdsServerHelper::onProcessBatchApiRequestComplete] - Batch API supported.

Conditions:
Jabber for Windows 9.7
Jabber for Windows 10.5
CUCM 9.1.2
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.