Guest

Preview Tool

Cisco Bug: CSCuo35952 - 180 Ringing is not forwarded by cucm in certain cases

Last Modified

Oct 27, 2017

Products (7)

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

Known Affected Releases

9.1(2)

Description (partial)

Symptom:
If CUCM recieves 183 session progress and responds with PRACK and establishes early media. If it's followed by an UPDATE/200 OK which sets media to a=inactive. Effectively both Parties involved in the call have stopped sending/recieving RTP stream.

Then a 180 Ringing is recieved. CUCM still thinks that the EARLY MEDIA session is active and does not forward it to the LEAF cluster in SME environment.

Conditions:
Early media cut through followed by UPDATE which sets media to inactive.
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.