Preview Tool

Cisco Bug: CSCup63385 - MGCP mod wrongly drops PriNotify if Alerting/Connect message is delayed

Last Modified

May 05, 2016

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

In working case, we could see the Notify req was sent after we received Alert and hence MGCP layer could process the notify request and sent out PriNotify with the updated display name/number.

In Non working case, MGCP module received Notify request even before getting Alert or Connect, it did not pass PriNotify message and ignores the update.

When doing PSTN to PSTN transfers , Intermittent incorrect caller id is seen on  transfer target .

When the Alerting message from the transfer target is delayed, MGCP component/module does not update or send the Notify message ( with the updated calling number and display) .
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.