MWI Does Not Work through PIMG Integration with Serial MCI

Introduction

This document describes Message Waiting Indicator (MWI) issues, which are a common problem reported when you configure a PBX IP Media Gateway (PIMG) or T1 Media Gateway (TIMG). This configuration can be tricky because it is not completed as often as CallManager integrations.

Problem

After you complete Setting Up a Serial (SMDI, MCI, or MD-110) PIMG Integration with Cisco Unity Connection via the PIMG Integration Guide, it possible that you might have an issue with the MWI.

Cisco suggests that you complete these steps in order to enable this trace on the PIMG/TIMG and troubleshoot the issue:

1. On the PIMG/TIMG, go to the Administration interface and choose Diagnostics > Trace/Logging.
2. Beside Trace, click Configure.Cisco recommends that you turn on these traces:
   • Tel - check the Event check box.
   • Voip - check the Prot check box.
   • SI - check the ALL check box.
3. Click Submit.

Complete these steps in order to start and gather traces on PIMG/TIMG:

1. On the PIMG/TIMG, go to the Administration interface and choose Diagnostics > Trace/Logging.
2. Beside Trace, click Start. It will be easier to troubleshoot this if you mark all messages read or deleted in the mailbox first.
3. Click Stop.
4. Click Download in order to obtain the trace file.

The traces from PIMG might indicate:

973:46.128 [VoIP   ] Prot   ---->NOTIFY sip:99666@14.48.48.82 SIP/2.0
973:46.128 [VoIP   ] Prot   From: sip:10.103.200.80:5060;
tag=0a81d948f05c42978c24cfce1c5c8fdc
973:46.128 [VoIP   ] Prot   To: sip:66666@10.103.200.82
973:46.128 [VoIP   ] Prot   Via: SIP/2.0/UDP 10.103.200.80:5060;
branch=z9hG4bKeab1185eb5064167af7c04e8dbbd7560
973:46.128 [VoIP   ] Prot   Max-Forwards: 70
973:46.128 [VoIP   ] Prot   Contact: sip:14.48.48.80:5060
973:46.128 [VoIP   ] Prot   Call-ID: c8331fa69d03489998c2550993385e6f@10.103.200.82
973:46.128 [VoIP   ] Prot   CSeq: 300 NOTIFY
973:46.128 [VoIP   ] Prot   Event: message-summary
973:46.128 [VoIP   ] Prot   Content-Length: 23
973:46.128 [VoIP   ] Prot   Content-Type: application/simple-message-summary
973:46.128 [VoIP   ] Prot   
973:46.128 [VoIP   ] Prot   Messages-Waiting: yes
973:46.128 [VoIP   ] Prot   
973:46.128 [VoIP   ] Prot   <----SIP/2.0 100 Trying
973:46.128 [VoIP   ] Prot   From:sip:10.103.200.80:5060;
tag=0a81d948f05c42978c24cfce1c5c8fdc

973:46.128 [VoIP   ] Prot   To:sip:99666@14.48.48.82
973:46.128 [VoIP   ] Prot   Call-ID:c8331fa69d03489998c2550993385e6f@14.48.48.82
973:46.128 [VoIP   ] Prot   CSeq:300 NOTIFY
973:46.128 [VoIP   ] Prot   Server:PBX-IP Media Gateway/2.1
973:46.128 [VoIP   ] Prot   Via:SIP/2.0/UDP 10.103.200.80:5060;
branch=z9hG4bKeab1185eb5064167af7c04e8dbbd7560
973:46.128 [VoIP   ] Prot   Content-Length:0
973:46.128 [VoIP   ] Prot   
973:46.128 [Gw     ] Error  rtGetOutboundRoute() failed (manip only) 3
973:46.128 [VoIP   ] Prot   
973:46.128 [VoIP   ] Prot   <----SIP/2.0 503 Service Unavailable
973:46.128 [VoIP   ] Prot   From:sip:10.103.200.80:5060;
tag=0a81d948f05c42978c24cfce1c5c8fdc
973:46.128 [VoIP   ] Prot   To:sip:66666@10.103.200.82;tag=4F823246313536410009495D
973:46.128 [VoIP   ] Prot   Call-ID:c8331fa69d03489998c2550993385e6f@10.103.200.82
973:46.128 [VoIP   ] Prot   CSeq:300 NOTIFY
973:46.128 [VoIP   ] Prot   Server:PBX-IP Media Gateway/2.1
973:46.128 [VoIP   ] Prot   Via:SIP/2.0/UDP 10.103.200.80:5060;
branch=z9hG4bKeab1185eb5064167af7c04e8dbbd7560
973:46.128 [VoIP   ] Prot   Content-Length:0
973:46.128 [VoIP   ] Prot

Notice 503 Service Unavailable in this trace. This is an indication that PIMG/TIMG receives the request, but does not have the resources to deal with it. The rtGetOutboundRout() is an indication that it cannot find a route to the Time-Division Multiplexing (TDM).

If you do not see any '---->NOTIFY' messages in the PIMG/TIMG traces that you gather, this might be an indication of a configuration problem on the Unity Connection. The best method to troubleshoot is to verify the configuration on Unity Connection. Then, enable the Notifier Macro traces on Unity Connection and verify with the Connection Conversation Manager and Connection Notifier traces that MWI processes and requests are sent to PIMG/TIMG.

Solution

In order to fix this issue, complete these steps:

1. Go to the Routing Table and choose Voip Rule > Inbound VoIP Rules.
2. In the Routing Table, find Outbound Routes.
3. Find Outbound Destination and set to TDM.
4. Find Trunk Group and set to TdmAll or the name you created.

Note: This is documented in the Release 10.x guide, but is sometimes overlooked.