Guest

Preview Tool

Cisco Bug: CSCut53747 - Name resolution doesnt work for E.164 numbers- Jabber over UDS

Last Modified

May 05, 2015

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

10.6(0)

Description (partial)

Symptom:
Jabber is unable to resolve the name for incoming calls with calling party number which are E.164 numbers ( with a plus sign). This is for the scenario where customer uses UDS as the contact source for directory look ups.

when Jabber gets an incoming call, it will send a UDS query to call manager like below:

https://10.106.83.196:8443/cucm-uds/users?max=4&start=0&number=+9111223344

However, call manager is unable to process the same as it cannot process a special character like '+'. 


Jabber is able to resolve any other numbers correctly. The issue is always reproducible with latest version of Jabber and CUCM versions 9.x / 10.x.

Conditions:
Jabber is unable to resolve the name for incoming calls with calling party number which are E.164 numbers ( with a plus sign). This is for the scenario where customer uses UDS as the contact source for directory look ups.
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.