Guest

Preview Tool

Cisco Bug: CSCvu00496 - Jabber Mac does not clear the Active Call count causing the CUCM to reject further calls with 486

Last Modified

Apr 27, 2020

Products (1)

  • Cisco Jabber for Mac

Known Affected Releases

12.8(1)

Description (partial)

Symptom:
Cisco Jabber iOS does not clear the active call count with the CUCM because of which any further calls that the Jabber tries to place is rejected by the CUCM with '486 Busy Here' message. 

In this scenario, the symptom is:
At the beginning of the first call jabber reports that there are active calls "numCalls = 1" in the logs, however there are not active calls, when the user attempts to transfer, Jabber sets the counter to 3 active calls, whereas TCT devices support only 2 active calls, hence CUCM sends a fast busy, this happens randomly.

Conditions:
Intermittent issue
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.