Preview Tool

Cisco Bug: CSCuq61286 - MWI Routing loop causes leak

Last Modified

Dec 18, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

Call Flow:

Unity Connection -----> SME Cluster---->Leaf Cluster

A misconfiguration on UCM resulting in a routing loop can create an instance where UCM will forward SIP Notifies for MWI between clusters resulting in an MWI leak.

SME sends a MWI SIP Notify-1 to the Leaf cluster via RL, which constitutes SIP trunk as its member pointing to Leaf cluster. 
Now, Leaf cluster on receiving this MWI SIP Notify-1 from the SME cluster, hits the RL which has 2 RGs,each of which is configured with 2 SIP trunks pointing to SME cluster. 
So, basically the above MWI SIP Notify-1 from SME cluster, triggered 4 SIP Notifys  back to it by the Leaf cluster. 
The MWI DN "XXXX", points to the RL , which constitutes SIP trunk as its member pointing to the Leaf cluster,again for each of these requests there will be  a SIPNotify to the leaf cluster. 
And for each of these SIPNotify, there will again be another 4 SIP Notifys sent back the SME cluster. 
This cumulative behaviour results in the queue depth of SIPHandler getting exhausted and results in core dump.
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.