Introduction
This document describes how to troubleshoot call failure from the Cisco TelePresence System (CTS) to the multipoint control unit (MCU)/endpoint registered to the Video Communication Server (VCS) on CallManager Release 8.6.2 due to Cisco bug ID CSCty07061.
Problem
Calls from the CTS on the Cisco Unified Communications Manager (CUCM) fail to the endpoints/MCU on the VCS. This issue happens specifically with CUCM Release 8.6.2.
CTS----CUCM----VCS----MCU
This is caused by:
- Logs from CUCM
- Communication between CUCM and the VCS
- INVITE sent from CUCM to the 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
Incoming 100 Tries from the VCS
[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
Incoming 180 Rings from the VCS
[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
Since the contact header in the 180 Ringing is a number@domain and since the Domain Name Server (DNS) on the CUCM cannot resolve the domain, the call fails and CUCM sends CANCEL with the cause "No route to destination". CUCM tries to resolve the domain in the contact header and fails to resolve it.
DNS Resolution on CUCM Fails
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^*^*
Hence, CallManager sends a CANCEL with the cause "No route to destination".
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
Solution
CallManager should attempt to respond to the INVITE with the the record route in the 180 Ringing instead of the contact header when both are present. However, it uses the contact header. Cisco bug ID CSCty07061 is open on the CUCM side for the same issue.
The best fix is to upgrade CallManager to a fixed-in version of the bug. You can also include the domain in the contact header in order to resolve to the IP address of the VCS. However, this is only a workaround.
You can also enable Rel1XX on the Session Initiation Protocol (SIP) Profile of the SIP Trunk. This might or might not work.
Feedback