Preview Tool

Cisco Bug: CSCtc43612 - Message Delivery delayed when message left on Secondary

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unity Connection

Known Affected Releases


Description (partial)

When Secondary Unity Connection answers call and takes message delay may be seen in message being delivered. As soon as message is delivered MWI will turn on.

The delay can be on the order of 15 seconds. 

To detect the issue the following traces can be enabled:

Traces for MWI Problem (Will allow us to see when the MWI turned on)
Conversation Traces (Gives idea when message is left and call is disconnected)

CuFileSync 1-3 (shows message being copied to Primary)
MTA 10-29 (shows message delivery process)

Traces may look similar to the following:

The message completed coping to the primary at:
10/06/2009 16:39:40.405 |15727,,,CuFileSync,1,/var/opt/cisco/connection/spool/drop/fa3eaf36-195a-4eba-9d57-cd4753e7a394.eml exists (CuFSTransporter.cpp:716)|
The MTA timer kicked off here:
10/06/2009 16:39:39.283 |17899,,,MTA,15,Thread=mtaTimerTasks;;Every 15 secs task running. Time=Tue Oct 06 20:39:39 GMT 2009|
10/06/2009 16:39:39.283 |17895,,,MTA,15,Thread=mtaDropMailHandler;;MTA Drop Messages Monitor: No new messages found !!|
Notice the timestamp. The message had not completed coping to the primary at this time.
Here the MTA timer kicked off again in 15 seconds:
10/06/2009 16:39:54.284 |17899,,,MTA,15,Thread=mtaTimerTasks;;Every 15 secs task running. Time=Tue Oct 06 20:39:54 GMT 2009|
10/06/2009 16:39:54.284 |17895,,,MTA,15,Thread=mtaDropMailHandler;;MTA Drop Messages Monitor: Number of messages found =1|
The message was found and the delivery and MWI turned on in same second:
10/06/2009 16:39:54.390 |17889,,,MTA,14,Thread=MtaMailDelivery-1;;Message Delivered to Recipient. SMTP mailbox Id=fe80e0ae-9764-4bd8-beda-6e7780057311|
10/06/2009 16:39:54.857 |17907,,,Notifier,12,Test: MWI (ON) completed successfully for mwi extension =32378|

This occurs in Cisco Unity Connection 7.1.2 with an active/active cluster.
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.