MWI Does Not Work on PIMG SMDI Integration
Available Languages
Introduction
This document describes a Unity Connection to PBX device integration issue related to the Message Waiting Indicator (MWI) status. PBX IP Media Gateways (PIMGs) are devices that allow Unity Connection to be integrated with PBX devices. At times these devices communicate call information and MWI status via a serial cable. This communication can be by SMDI, MCI, or MD-110.
Problem
In this situation there are multiple PIMGs set up to a SMDI Centrex integration. At times, MWI does not work.
The PIMGs are set up in a Master/Slave configuration as indicated in the Setting Up the Analog PIMG Units for a Serial Integration section of the PIMG Integration Guide for Cisco Unity Connection Release 9.x.
In order to get more data from PIMGs, you need to enable these traces on all PIMGs.
On the PIMG/TIMG, go to the Administration interface and choose Diagnostics > Trace/Logging.
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 all of the check boxes.
- SiIP - check all of the check boxes.
Click Submit.
Complete these steps in order to start and gather traces on the PIMG:
On the PIMG/TIMG, go to the Administration interface and choose Diagnostics > Trace/Logging.
Beside Trace, click Start and make a test call after enough time has passed that you expect the call should have rolled to voicemail.
Reproduce an instance of where MWI does not work.
Click Stop.
Click Download in order to obtain the trace file.
The PIMG that received the MWI request from Unity Connection might show this when the problem occurred:
856:46.974 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:46.974 [VoIP ] Prot From: sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:46.974 [VoIP ] Prot To: sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:46.974 [VoIP ] Prot Via: SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:46.974 [VoIP ] Prot Max-Forwards: 70
856:46.974 [VoIP ] Prot Contact: sip:14.48.48.58:5060
856:46.974 [VoIP ] Prot Call-ID: 0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:46.974 [VoIP ] Prot CSeq: 300 NOTIFY
856:46.974 [VoIP ] Prot Event: message-summary
856:46.974 [VoIP ] Prot Content-Length: 23
856:46.974 [VoIP ] Prot Content-Type: application/simple-message-summary
856:46.974 [VoIP ] Prot
856:46.974 [VoIP ] Prot Messages-Waiting: yes
856:46.988 [VoIP ] Prot <----SIP/2.0 100 Trying
856:46.988 [VoIP ] Prot From:sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:46.988 [VoIP ] Prot To:sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:46.988 [VoIP ] Prot Call-ID:0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:46.988 [VoIP ] Prot CSeq:300 NOTIFY
856:46.988 [VoIP ] Prot Server:PBX-IP Media Gateway/2.1
856:46.988 [VoIP ] Prot Via:SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:46.988 [VoIP ] Prot Content-Length:0
856:50.998 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:50.998 [VoIP ] Prot From: sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:50.998 [VoIP ] Prot To: sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:50.998 [VoIP ] Prot Via: SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:50.998 [VoIP ] Prot Max-Forwards: 70
856:50.998 [VoIP ] Prot Contact: sip:14.48.48.58:5060
856:50.998 [VoIP ] Prot Call-ID: 0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:50.998 [VoIP ] Prot CSeq: 300 NOTIFY
856:50.998 [VoIP ] Prot Event: message-summary
856:50.998 [VoIP ] Prot Content-Length: 23
856:50.998 [VoIP ] Prot Content-Type: application/simple-message-summary
856:50.998 [VoIP ] Prot
856:50.998 [VoIP ] Prot Messages-Waiting: yes
856:51.008 [VoIP ] Prot <----SIP/2.0 100 Trying
856:51.008 [VoIP ] Prot From:sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:51.008 [VoIP ] Prot To:sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:51.008 [VoIP ] Prot Call-ID:0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:51.008 [VoIP ] Prot CSeq:300 NOTIFY
856:51.008 [VoIP ] Prot Server:PBX-IP Media Gateway/2.1
856:51.008 [VoIP ] Prot Via:SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:51.008 [VoIP ] Prot Content-Length:0
856:51.008 [VoIP ] Prot
856:55.016 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:55.018 [VoIP ] Prot From: sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:55.018 [VoIP ] Prot To: sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:55.018 [VoIP ] Prot Via: SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:55.018 [VoIP ] Prot Max-Forwards: 70
856:55.018 [VoIP ] Prot Contact: sip:14.48.48.58:5060
856:55.018 [VoIP ] Prot Call-ID: 0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:55.018 [VoIP ] Prot CSeq: 300 NOTIFY
856:55.018 [VoIP ] Prot Event: message-summary
856:55.018 [VoIP ] Prot Content-Length: 23
856:55.018 [VoIP ] Prot Content-Type: application/simple-message-summary
856:55.018 [VoIP ] Prot
856:55.018 [VoIP ] Prot Messages-Waiting: yes
856:55.024 [VoIP ] Prot <----SIP/2.0 100 Trying
856:55.024 [VoIP ] Prot From:sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:55.024 [VoIP ] Prot To:sip:9193334778@14.48.48.122;vnd.pimg.port=8
856:55.024 [VoIP ] Prot Call-ID:0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:55.024 [VoIP ] Prot CSeq:300 NOTIFY
856:55.024 [VoIP ] Prot Server:PBX-IP Media Gateway/2.1
856:55.024 [VoIP ] Prot Via:SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:55.478 [VoIP ] Prot <----SIP/2.0 200 OK
856:55.478 [VoIP ] Prot From:sip:14.48.48.58:5060;
tag=95d24e2779b54fcf933c9b5623e37d23
856:55.478 [VoIP ] Prot To:sip:9193334778@14.48.48.122;vnd.pimg.port=8;
tag=7578324631353641038E657E
856:55.478 [VoIP ] Prot Call-ID:0d404c0a3a094ef4a1a729b2d8845e3c@14.48.48.122
856:55.478 [VoIP ] Prot CSeq:300 NOTIFY
856:55.478 [VoIP ] Prot Server:PBX-IP Media Gateway/2.1
856:55.478 [VoIP ] Prot Via:SIP/2.0/UDP 14.48.48.58:5060;
branch=z9hG4bKb761e35b9cf34fa1a8a1511343b11271
856:55.478 [VoIP ] Prot Content-Length:0
856:55.478 [VoIP ] Prot
856:56.910 [Tel-8 ] Event ringback Off
It is possible you will notice these issues:
- You might see this sequence in the trace. You see the notification tried three times and finally concluded with a 200 OK message to stop the process.
856:46.974 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:46.988 [VoIP ] Prot <----SIP/2.0 100 Trying
856:50.998 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:51.008 [VoIP ] Prot <----SIP/2.0 100 Trying
856:55.016 [VoIP ] Prot ---->NOTIFY sip:9193334778@14.48.48.122 SIP/2.0
856:55.024 [VoIP ] Prot <----SIP/2.0 100 Trying
856:55.478 [VoIP ] Prot <----SIP/2.0 200 OKHowever, the MWI is not turned on.
- You might also notice that the PIMG that shows this information is not the Master PIMG.
Solution
Complete these steps in order to resolve the issue:
- Go to the Unity Connection Administration web page.
- Go to Telephony Integrations.
- Click Ports (or Port Groups, if you want to disable the entire port group).
- Choose the Phone System Display name and enter the PIMG integration.
- Go into the ports for the Slave PIMGs and uncheck the Perform Message Notification and Send MWI Requests check box.
- Save for each port.
This only leaves the Master PIMG ports able to complete these functions. Now the MWI should function as expected.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)