Guest

Preview Tool

Cisco Bug: CSCvu33113 - Jabber does not stop sending CTI request,with invalid access token to CUCM, causing high CPU on CUCM

Last Modified

Sep 02, 2020

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

12.7(1)

Description (partial)

Symptom:
If the access tokens expire, Jabber does not stop sending CTI request with invalid access token to CUCM. Jabber is not requesting a new token despite of token configuration and on CUCM Side, we see multiple CTI Application failed Messages from these Jabber devices causing high CPU

Sample Snippet below
 
%UC_CTI-3-CtiProviderOpenFailure: %[CTIconnectionId=177616][LoginUserId=][Reason=-1932787616][UNKNOWN_PARAMNAME:IPAddress=X.X.X.X][UNKNOWN_PARAMNAME:IPv6Address=][AppID=Cisco CTIManager][ClusterID=mbwhiteplains-cluster][NodeID=mbwhiteplains-ucmp]: CTI application failed to open provider; application startup failed.

SSO is disabled but oauth is enabled

** SSO is disbaled on CUCM and IMP.
**OAuth is enabled
** We still see some SSO request from IMP.

Conditions:
access tokens expired

SSO is disabled but oauth is enabled

** SSO is disbaled on CUCM and IMP.
**OAuth is enabled
** We still see some SSO request from IMP.
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.