Preview Tool

Cisco Bug: CSCtd02385 - Call not cleared when MWI comes in via SIP notify/StationMwiNotification

Last Modified

Feb 01, 2017

Products (3)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Unity Connection Version 7.1
  • Cisco Unified Communications Manager Version 7.1

Known Affected Releases


Description (partial)

(**Note: please see CSCtd60961 for the entire fix to this issue**)

Call not cleared when MWI comes in via SIP notify. 
This problem exists when Unity integration is SIP or the new SCCP StationMwiNotificationMessage.


MWI comes in via SIP notify, which goes across an ICT. Call across ICT is not torn down after MWI operation is completed.

When CUCM 7.1.2 is integrated with Unity Connection 7.1.2 by Skinny, MWI is notified by a StationMwiNotificationMessage message. A call triggered by the message won't tear down.
If either version is older than 7.1.2, OffhookWithCpgn is used for MWI notification. As a result, this problem won't occur.

Upon receiving SsInfoReq, MessageWaitingManager creates a new MessageWaiting instance with message interface type set to ON_NET_CMI. In this case, the MWI Activate APDU sent earlier is received. As a result, CallManager invokes clearCall to send SsClearCallReq to Cc. MessageWaiting rejects sending the SsClearCallReq if the message interface type set to ON_NET_CMI.
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.