简介
本文档介绍如何排除因Cisco Bug ID CSCty07061而从Cisco TelePresence System(CTS)到多点控制单元(MCU)/终端的呼叫故障,该多点控制单元(MCU)/终端注册到CallManager版本8.6.2上的视频通信服务器(VCS)。。
问题
从Cisco Unified Communications Manager(CUCM)上的CTS发出的呼叫无法到达VCS上的终端/MCU。此问题在CUCM版本8.6.2中特别发生。
CTS - CUCM - VCS - MCU
这是由以下原因造成的:
- 来自CUCM的日志
- CUCM与VCS之间的通信
- 从CUCM发送到VCS的邀请
[77348,NET]
INVITE sip:75005@172.16.198.29:5060 SIP/2.0
Date: Fri, 27 Apr 2012 08:39:00 GMT
Call-Info:
<sip:172.16.17.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
SUBSCRIBE, NOTIFY
From:
<sip:7001@172.16.17.11>;tag=26846~41fac465-b852-4a36-b3e8-f08e73aef877-21357
319
Allow-Events: presence, kpml
P-Asserted-Identity: <sip:7001@172.16.17.11>
Supported:
timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation
Min-SE: 1800
Cisco-Guid: 1849552768-0000065536-0000000093-0185667756
Remote-Party-ID:
<sip:7001@172.16.17.11>;party=calling;screen=yes;privacy=off
Content-Length: 0
User-Agent: Cisco-CUCM8.6
To: <sip:75005@172.16.198.29>
Contact:
<sip:7001@172.16.17.11:5060;transport=tcp>;video;audio;x-cisco-tip;x-cisco-m
ultiple-screen=3
Expires: 180
Call-ID: 6e3def80-f9a15b24-380-b1110ac@172.16.17.11
Via: SIP/2.0/TCP 172.16.17.11:5060;branch=z9hG4bK7371e5c6b50
CSeq: 101 INVITE
Session-Expires: 1800
Max-Forwards: 69
从VCS传入100次尝试
[77349,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP
172.16.17.11:5060;branch=z9hG4bK7371e5c6b50;received=172.16.17.11;ingress-zo
ne=CUCMAKBANK
Call-ID: 6e3def80-f9a15b24-380-b1110ac@172.16.17.11
CSeq: 101 INVITE
From:
<sip:7001@172.16.17.11>;tag=26846~41fac465-b852-4a36-b3e8-f08e73aef877-21357
319
To: <sip:75005@172.16.198.29>
Server: TANDBERG/4102 (X7.0.2)
Content-Length: 0
从VCS传入的180响铃
[77352,NET]
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP
172.16.17.11:5060;branch=z9hG4bK7371e5c6b50;received=172.16.17.11;ingress-zo
ne=CUCMAKBANK
Call-ID: 6e3def80-f9a15b24-380-b1110ac@172.16.17.11
CSeq: 101 INVITE
Contact:
<sip:01189175005@vcsc.cisco.com;gr=urn:uuid:d3cd717d-3870-5f90-aa64-be57a7db
fb2f>;isfocus
From:
<sip:7001@172.16.17.11>;tag=26846~41fac465-b852-4a36-b3e8-f08e73aef877-21357
319
To: <sip:75005@172.16.198.29>;tag=1644632DC02A0000
Record-Route:
<sip:proxy-call-id=6fb77ef2-9044-11e1-aeb4-0010f31e2904@172.16.198.29:5061;t
ransport=tls;lr>
Record-Route:
<sip:proxy-call-id=6fb77ef2-9044-11e1-aeb4-0010f31e2904@172.16.198.29:5060;t
ransport=tcp;lr>
User-Agent: Codian MCU 4505 v4.2 (1.50)
Content-Length: 0
由于180振铃中的联系人报头是number@domain,并且由于CUCM上的域名服务器(DNS)无法解析域,因此呼叫失败,CUCM发送CANCEL,原因是“没有到目的地的路由”。CUCM尝试解析联系人信头中的域,但无法解析。
CUCM上的DNS解析失败
11:39:01.095 |//SIP/SIPDns(1,72,1)/wait_SdlDnsSrvRecordRsp: (DNS A or AAAA query called
as SRV query Fail):hostname=vcsc.cisco.com,ReqType=1,serversused=0|0,0,0,0.0^*^*
11:39:01.095 |LineCdpc(175): -dispatchToAllDevices-, sigName=CcAlertReq,
device=SEP001DA2394CE2|1,100,63,1.28663^172.16.198.29^*
11:39:01.095 |LineCdpc(175): -dispatchToAllDevices-, sigName=CcAlertReq,
device=SEPE80462EB1661|1,100,63,1.28663^172.16.198.29^*
11:39:01.095 |//SIP/SIPDns(1,72,1)/wait_SdlDnsSrvRecordRsp: ReceivedSdlDnsSrvRecordRsp
ReqCode is -1|0,0,0,0.0^*^*
11:39:01.095 |//SIP/SIPDns(1,72,1)/copySdlDnsSrvRecordRspToSpi: ReqType is
1|0,0,0,0.0^*^*
11:39:01.095 |//SIP/SIPDns(1,72,1)/wait_SdlDnsSrvRecordRsp: (DNS A QueryFail)
|0,0,0,0.0^*^*
11:39:01.095 |//SIP/Stack/Info/0x0/ccsip_spi_get_msg_type returned: 2 for
event 44|0,0,0,0.0^*^*
因此,CallManager发送CANCEL,其原因是“没有到目的地的路由”。
CANCEL sip:75005@172.16.198.29:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.17.11:5060;branch=z9hG4bK7371e5c6b50
From:
<sip:7001@172.16.17.11>;tag=26846~41fac465-b852-4a36-b3e8-f08e73aef877-21357
319
To: <sip:75005@172.16.198.29>
Date: Fri, 27 Apr 2012 08:39:00 GMT
Call-ID: 6e3def80-f9a15b24-380-b1110ac@172.16.17.11
CSeq: 101 CANCEL
Max-Forwards: 70
Reason: Q.850;cause=3
Content-Length: 0
解决方案
CallManager应尝试使用180振铃中的记录路由(而不是联系人报头)响应INVITE(当两者都存在时)。但是,它使用联系人信头。CUCM端上针对同一问题打开了Cisco Bug ID CSCty07061。
最佳解决方法是将CallManager升级到Bug的固定版本。您还可以在联系人报头中包含域,以便解析为VCS的IP地址。但是,这只是一种解决方法。
您还可以在SIP中继的会话发起协议(SIP)配置文件上启用Rel1XX。这可能有效,也可能无效。