Cisco Expressway Troubleshooting
SIP/2.0 503 Service Unavailable
Observed in Expressway-C trace
SIP/2.0 503
Service Unavailable
Via: SIP/2.0/TCP 1.1.1.241_EXPC:5060;egress-zone=CEtcp192168994;branch=z9hG4bK3eca9d5dc4e26de65b1b83f501cea485458555;proxy-call-id=51ce23fa-d8d1-4c22-9579-ade0f631d257;rport,SIP/2.0/TLS 1.1.1.241_EXPC:5073;branch=z9hG4bK1e991e55187479dada6391ef5adf084024563;x-cisco-local-service=nettle;received=1.1.1.241_EXPC;rport=30979;ingress-zone=DefaultZone,SIP/2.0/TLS 1.1.1.241_EXPC:5061;egress-zone=DefaultZone;branch=z9hG4bKb340db4a70e04cc037ea7de16e55df58458554.3d8de2b0006ebe59e4c4ae2fde61ae57;proxy-call-id=1ceee43f-3413-4f0f-bfcb-aed8a3b2ad03;received=1.1.1.241_EXPC;rport=29605,SIP/2.0/TLS 1.1.1.246_EXPE:7001;egress-zone=UCtoEXPC2;branch=z9hG4bKf0e07263c19c7bfd6133775994af916998831.7b4bb0bfbe6838be4f4507d0ce70df61;proxy-call-id=bc3fdcb9-f10b-4f23-a0d1-1e59e49de578;received=1.1.1.246_EXPE;rport=7001;ingress-zone=UCtoEXPE2,SIP/2.0/TLS 0.0.0.0_USER:43932;branch=z9hG4bK00004aa4;received=2.2.2.2_EXPEPUB;rport=43932;ingress-zone=CollaborationEdgeZone
Call-ID: aefdce71-0af2001c-00004664-00007833@0.0.0.0_USER
CSeq: 101 INVITE
From: “Jason Neurohr” <sip:30822@1.1.1.1_CUCM>;tag=aefdce710af2021f0000027c-00000f51
To: <sip:12345@domain.com.au>;tag=698699~2004fc79-b651-49b6-be90-35de0e0192d1-48112662
Server: Cisco-CUCM10.5
Date: Wed, 28 Dec 2016 02:37:57 GMT
Allow-Events: presence
Reason: Q.850 ;cause=41
Observed on CUCM trunk
Status Reason local=2
Discussion
This issue occurred on an Expressway pair where both MRA and B2B were configured. The zone towards CUCM was configured to use a non-standard port and this configuration was reciprocated on the CUCM trunk and security profile. The problem was the Expressway was not listening on the non-standard SIP TCP port so the trunk from the CUCM perspective was out of service. To resolve the Configuration > Protocols > SIP > TCP port was altered to be the non-stanard one.
Content Sharing Issue when call passes through a CUCM Trunk with Expressway-C
A content sharing problem was raised with me on a customer environment, specifically for the scenario of a Lync client attempting to share content with a Cisco VC device. Below are two of the SIP exchanges followed by a discussion or the what caused the problem.
This is the 200 OK from the VC endpoint back towards the Expressway-C. Here you can see the media line for the UDP/BFCP channel.
SIPMSG:
|SIP/2.0 200 OK
Via: SIP/2.0/TLS 1.1.1.1:5061;egress-zone=SydneyC;branch=z9hG4bKb22340aaa28b7e3008f895757df71f47179697.1bc5134a3bbf3b08cc9c62bcd51b9ae5;proxy-call-id=7f638648-a465-4f0f-a9ff-23a4e37c1af1;received=1.1.1.1;rport=28744,SIP/2.0/TLS 1.1.1.2:5061;branch=z9hG4bK1c24f5540b0c7f;received=1.1.1.2;ingress-zone=CUCMNeighborZone
Call-ID: c7cd1180-8c7174f8-1641e6-76cd400a@1.1.1.2
CSeq: 101 INVITE
Contact: <sip:1000@domain.com.au;gr=urn:uuid:a07c707d-d19d-5dd3-84a8-8bec2f44ec3d>
From: “Lync User” <sip:lync_user@domain.com.au>;tag=26486455~9d74399c-45ec-4e38-8133-ad0e4a5cbed3-19847807
To: “VC EP " <sip:1000@1.1.1.1>;tag=fdf9b0d5cdd30776
Record-Route: <sip:proxy-call-id=7f638648-a465-4f0f-a9ff-23a4e37c1af1@1.1.1.1:5061;transport=tls;lr>
Record-Route: <sip:proxy-call-id=7f638648-a465-4f0f-a9ff-23a4e37c1af1@1.1.1.1:5061;transport=tls;lr>
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
Server: TANDBERG/528 (TC7.3.6.ea51021) Cisco-C20
Supported: replaces,100rel,timer,gruu,path,outbound
Require: timer
Session-Expires: 1800;refresher=uas
Min-SE: 500
Content-Type: application/sdp
Content-Length: 3926v=0
o=tandberg 271 1 IN IP4 2.2.2.2
s=-
c=IN IP4 2.2.2.2
b=AS:6000
t=0 0
m=audio 2388 RTP/AVP 108 109 110 104 105 9 18 8 0 101
b=TIAS:64000
a=rtpmap:108 MP4A-LATM/90000
a=fmtp:108 profile-level-id=24;object=23;bitrate=64000
a=rtpmap:109 MP4A-LATM/90000
a=fmtp:109 profile-level-id=24;object=23;bitrate=56000
a=rtpmap:110 MP4A-LATM/90000
a=fmtp:110 profile-level-id=24;object=23;bitrate=48000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=sendrecv
m=video 2390 RTP/AVP 97 126 96 34 31
b=TIAS:6000000
a=rtpmap:97 H264/90000
a=fmtp:97 packetization-mode=0;profile-level-id=420016;max-br=5000;max-mbps=108000;max-fs=3600;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1382400;sar-supported=16
a=rtpmap:126 H264/90000
a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3600;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1382400;sar-supported=16
a=rtpmap:96 H263-1998/90000
a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
a=rtpmap:34 H263/90000
a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
a=rtpmap:31 H261/90000
a=fmtp:31 cif=1;qcif=1;maxbr=20000
a=label:11
a=answer:full
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=content:main
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=rtcp-fb:* ccm tmmbr
a=sendrecv
m=application 2444 UDP/BFCP ***
a=setup:actpass
a=confid:1
a=userid:271
a=floorid:2 mstrm:12
a=floorctrl:c-s
a=connection:new
m=video 2392 RTP/AVP 97 126 96 34 31
b=TIAS:6000000
a=rtpmap:97 H264/90000
a=fmtp:97 packetization-mode=0;profile-level-id=420016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560;sar-supported=16
a=rtpmap:126 H264/90000
a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560;sar-supported=16
a=rtpmap:96 H263-1998/90000
a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,2;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
a=rtpmap:34 H263/90000
a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
a=rtpmap:31 H261/90000
a=fmtp:31 cif=1;qcif=1;maxbr=20000
a=label:12
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=content:slides
a=rtcp-fb: nack pli
a=rtcp-fb: ccm fir
a=rtcp-fb:* ccm tmmbr
a=sendrecv
m=application 2394 RTP/AVP 100
a=rtpmap:100 H224/4800
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=sendrecv
m=application 2454 UDP/UDT/IX *
a=ixmap:0 ping
a=ixmap:2 xccp
This next message is the SIP 200 OK being sent from the Expressway-C to CUCM. The BFCP media line is again present but it was been changed to TCP/BFCP.
SIPMSG:
|SIP/2.0 200 OK
Via: SIP/2.0/TLS 1.1.1.2:5061;branch=z9hG4bK1c24f5540b0c7f;received=1.1.1.2;ingress-zone=CUCMNeighborZone
Call-ID: c7cd1180-8c7174f8-1641e6-76cd400a@1.1.1.2
CSeq: 101 INVITE
Contact: <sip:1000@domain.com.au;gr=urn:uuid:a07c707d-d19d-5dd3-84a8-8bec2f44ec3d>
From: “Lync User <sip:lync_user@domain.com.au>;tag=26486455~9d74399c-45ec-4e38-8133-ad0e4a5cbed3-19847807
To: “VC EP” <sip:1000@1.1.1.1>;tag=fdf9b0d5cdd30776
Record-Route: <sip:proxy-call-id=7f638648-a465-4f0f-a9ff-23a4e37c1af1@1.1.1.1:5061;transport=tls;lr>
Record-Route: <sip:proxy-call-id=7f638648-a465-4f0f-a9ff-23a4e37c1af1@1.1.1.1:5061;transport=tls;lr>
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
Server: TANDBERG/528 (TC7.3.6.ea51021) Cisco-C20
Supported: replaces,100rel,timer,gruu,path,outbound
Require: timer
Session-Expires: 1800;refresher=uas
Min-SE: 500
Content-Type: application/sdp
Content-Length: 3885v=0
o=tandberg 271 1 IN IP4 2.2.2.2
s=-
c=IN IP4 2.2.2.2
b=AS:1536
t=0 0
m=audio 2388 RTP/AVP 108 109 110 104 105 9 18 8 0 101
b=TIAS:64000
a=rtpmap:108 MP4A-LATM/90000
a=fmtp:108 profile-level-id=24;object=23;bitrate=64000
a=rtpmap:109 MP4A-LATM/90000
a=fmtp:109 profile-level-id=24;object=23;bitrate=56000
a=rtpmap:110 MP4A-LATM/90000
a=fmtp:110 profile-level-id=24;object=23;bitrate=48000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=sendrecv
m=video 2390 RTP/AVP 97 126 96 34 31
b=TIAS:6000000
a=rtpmap:97 H264/90000
a=fmtp:97 packetization-mode=0;profile-level-id=420016;max-br=5000;max-mbps=108000;max-fs=3600;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1382400;sar-supported=16
a=rtpmap:126 H264/90000
a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3600;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1382400;sar-supported=16
a=rtpmap:96 H263-1998/90000
a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
a=rtpmap:34 H263/90000
a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
a=rtpmap:31 H261/90000
a=fmtp:31 cif=1;qcif=1;maxbr=20000
a=label:11
a=answer:full
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=content:main
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=rtcp-fb:* ccm tmmbr
a=sendrecv
m=application 0 TCP/BFCP ***
a=setup:actpass
a=confid:1
a=userid:271
a=floorid:2 mstrm:12
a=floorctrl:c-s
a=connection:new
m=video 2392 RTP/AVP 97 126 96 34 31
b=TIAS:6000000
a=rtpmap:97 H264/90000
a=fmtp:97 packetization-mode=0;profile-level-id=420016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560;sar-supported=16
a=rtpmap:126 H264/90000
a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560;sar-supported=16
a=rtpmap:96 H263-1998/90000
a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,2;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
a=rtpmap:34 H263/90000
a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
a=rtpmap:31 H261/90000
a=fmtp:31 cif=1;qcif=1;maxbr=20000
a=label:12
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=content:slides
a=rtcp-fb: nack pli
a=rtcp-fb: ccm fir
a=rtcp-fb:* ccm tmmbr
a=sendrecv
m=application 2394 RTP/AVP 100
a=rtpmap:100 H224/4800
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:………………………………………
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:……………………………………… UNENCRYPTED_SRTCP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:………………………………………
a=sendrecv
m=application 0 RTP/AVP 0</>
Discussion
This occured because of the Zone Profile used on the Expressway-C Zone corresponding with the CUCM node. In this case it was set to Cisco Unified Communications Manager which is intended for version prior to 8.6.1. When this profile is configured the property SIP UDP/BFCP filter mode is set to On. This causes the behaviour shown above in the traces. Instead in this instance with CUCM version 10.5, the Zone Profile should be set to Custom with the only change to defaults being Call Signaling routed mode set to Always.