Guest

Preview Tool

Cisco Bug: CSCul53784 - JTAPI Ignores Privacy Settings When Creating Unknown Connection

Last Modified

Nov 14, 2015

Products (8)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Business Edition 5000 Version 8.6
  • Cisco Intercompany Media Engine
  • Cisco Business Edition 3000 Version 8.6
  • Cisco Business Edition 6000 Version 8.6
  • Cisco Unified Communications Manager Version 8.6
  • Cisco Unity Connection Version 8.6
  • Cisco Unified Communications Manager Session Management Edition

Known Affected Releases

8.6(2)

Description (partial)

Symptom:
Some calls have CurrentCallingPI set to true and others have CurrentCallingPI set to false for the same call flow.  This can cause issues with applications using the getCurrentCallingAddressPI API where the application is not prepared to handle both true and false results. Depending on timing, the same call flow could inconsistently return true or false for the same API.

Conditions:
A call is received from a SIP gateway that has user information in the FROM header but has a Remote-Party ID that has no user information and privacy=full.  This call is sent to an application monitored CTI device and the application monitoring the device is using the getCurrentCallingAddressPI API.
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.