Preview Tool

Cisco Bug: CSCvs96056 - Bulk /Indvidual Reset Option for Jabber devices to prevent outages for collab solution

Last Modified

Mar 03, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

11.5(1.17900.49) 12.5(1.12900.115)

Description (partial)

1> System under high CPU or carsh observed for tomcat
2> TCP/IP Client reconnects and heavy bursts leading to Kernel Flood
3> High Request rate as jabber misbehavior and lead to 503 or server not available 
4> HA gets disturbed for products like unity where only 2 clusters can be supported

1> Jabber sending old tokens / password for authentication to all Collab servers like CUCM ,CUC and IM&P
2> Jabber misbehaves and start expired or corrupt token from cache which is not updated 
3> Jabber still do not refresh itself due to known bugs or solution complexity with serve side fix or change
4> Jabber requires to be RESET by Customer as part of some distribution/changes done to Service Profile 
5> Jabber in Fast logins sometimes fails to fetch token from Web Ex cloud and sends old token 
6> Customer want to RESET Jabber on upgrade for cache issues FIX FROM JABBER 
7> CLI runs for token and keys on CUCM misbehave and jabber enters into loop .post fix Jabber may need RESET 
8> JABBER defect has workaround to REST client and customer do not want to upgrade all clients and want to implement workaround
Bug details contain sensitive information and therefore require a 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.