本文档介绍与消息等待指示器(MWI)状态相关的Unity Connection到PBX设备集成问题。PBX IP媒体网关(PIMG)是允许Unity Connection与PBX设备集成的设备。有时,这些设备通过串行电缆传达呼叫信息和MWI状态。此通信可以由SMDI、MCI或MD-110进行。
在这种情况下,SMDI Centrex集成中设置了多个PIMG。有时,MWI不起作用。
PIMG在主/从配置中设置,如Cisco Unity Connection版本9.x的PIMG集成指南的“为串行集成设置模拟PIMG单元”部分所示。
为了从PIMG获取更多数据,您需要在所有PIMG上启用这些跟踪。
在PIMG/TIMG上,转到Administration(管理)界面,然后选择Diagnostics(诊断)> Trace/Logging(跟踪/记录)。
在“跟踪”旁,单击配置。思科建议您打开以下跟踪:
单击“Submit”。
要在PIMG上启动和收集跟踪,请完成以下步骤:
在PIMG/TIMG上,转到Administration(管理)界面,然后选择Diagnostics(诊断)> Trace/Logging(跟踪/记录)。
在“跟踪”旁,单击开始,在经过足够的时间后进行测试呼叫,以便您预期该呼叫应滚动到语音邮件。
重现MWI不起作用的实例。
单击“停止”。
单击Download以获取跟踪文件。
收到Unity Connection的MWI请求的PIMG可能会在出现问题时显示以下内容:
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
您可能会注意到以下问题:
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 OK
但是,MWI未打开。
完成这些步骤以解决问题:
这仅使主PIMG端口能够完成这些功能。现在,MWI应按预期运行。
版本 | 发布日期 | 备注 |
---|---|---|
1.0 |
20-Aug-2014 |
初始版本 |