Guest

Preview Tool

Cisco Bug: CSCur34180 - Jabber support for globalization/localization

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

10.5(0)

Description (partial)

Symptom:
Scenario:
++ PSTN incoming call to jabber windows; In voice gateway, the number is being globalized to + E.164 number. There is a calling party transformation applied on jabber device pool so  that the globalized number is localized by removing the +<countrycode>
++ SIP invite received on Jabber looks like this:
 Remote-Party-ID: <sip:93250074@172.24.8.13;x-cisco-callback-number=+6593250074>;party=calling;screen=yes;privacy=off

Jabber will only show up the number as 93250074 in the missed call history as per the SIP URI field in the remote-party-ID header. In-order for jabber to show up the +E.164 number, it should support x-cisco-callback-number field as well, like the normal sip ip hard phones. 

The only work around is to apply dial rules to get around this situation. This needs to be documented that, in order for jabber to support globalization/localization, dial rules need to be applied so that the full E164 number will appear in call history/call toast.

Conditions:
Scenario:
++ PSTN incoming call to jabber windows; In voice gateway, the number is being globalized to + E.164 number. There is a calling party transformation applied on jabber device pool so  that the globalized number is localized by removing the +<countrycode>
++ SIP invite received on Jabber looks like this:
 Remote-Party-ID: <sip:93250074@172.24.8.13;x-cisco-callback-number=+6593250074>;party=calling;screen=yes;privacy=off

Jabber will only show up the number as 93250074 in the missed call history as per the SIP URI field in the remote-party-ID header. In-order for jabber to show up the +E.164 number, it should support x-cisco-callback-number field as well, like the normal sip ip hard phones. 

The only work around is to apply dial rules to get around this situation. This needs to be documented that, in order for jabber to support globalization/localization, dial rules need to be applied so that the full E164 number will appear in call history/call toast.
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.