MWI不通过与序列MCI的PIMG集成工作

Download Options

PDF (138.5 KB)
View with Adobe Reader on a variety of devices
ePub (66.5 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (63.9 KB)
View on Kindle device or Kindle app on multiple devices

Updated: 2014 年 11 月 24 日

Document ID:118641

About Translation

About This Translation

Cisco has translated this document using a combination of machine and human technologies to offer our users around the world Support content in their own language.Please note that even the best machine translation will not be as accurate as that provided by a professional translator.Cisco Systems, Inc. assumes no liability for the accuracy of these translations and recommends that the original English document (link provided) is always consulted.

简介

本文描述消息等待指示符(MWI)问题，是报告的常见问题，当您配置PBX IP媒体网关(PIMG)时或T1媒体网关(TIMG)。因为一样经常没有完成象Callmanager集成，此配置可以是不易处理的。

问题

在您完成设置与Cisco Unity Connection的序列(SMDI、MCI或者MD-110)后PIMG集成通过PIMG集成指南，它可能您也许有与MWI的一个问题。

思科建议您完成这些步骤为了启用在PIMG/TIMG的此trace和排除故障问题：

在PIMG/TIMG，请去管理界面并且选择诊断> Trace/记录日志。
在Trace旁边，请点击Configure.Cisco建议您打开这些跟踪：
- Tel -请检查事件复选框。
- Voip -请检查Prot复选框。
- SI -请检查All复选框。
单击 submit。

完成这些步骤为了开始和搜集在PIMG/TIMG的跟踪：

在PIMG/TIMG，请去管理界面并且选择诊断> Trace/记录日志。
在Trace旁边，请点击开始。如果标记在邮箱首先，读取或删除的所有消息排除故障此将是更加容易的。
单击“停止”。
点击下载为了得到跟踪文件。

从PIMG的跟踪也许指示：

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

公告503服务不可用在此trace。这是征兆PIMG/TIMG收到请求，但是没有资源涉及它。rtGetOutboundRout()是征兆找不到路由到Time Division Multiplexing (TDM)。

如果看不到其中任一‘----在您搜集的PIMG/TIMG跟踪的>NOTIFY’消息，这也许是配置问题的征兆在Unity Connection的。排除故障的佳方法是验证在Unity Connection的配置。然后，请启用在Unity Connection的通告人宏观跟踪并且验证与连接会话管理器，并且连接MWI处理的通告人跟踪和请求发送对PIMG/TIMG。