03-08-2017 05:39 AM - edited 03-17-2019 09:44 AM
Hi All,
My Setup:
Cucm endpoint -------CUCM--------------TLS/SRTP---------SBC
Problem:
Initial call coming from SBC to CUCM works fine. TLS and Cipher suit negotiation worked fine. When I'm trying to put call on Hold from CUCM,
CUCM sends Re-INVITE without SDP, in response to that, SBC responds with 200 OK with SDP and in a = RTP/SAVP.
CUCM responding with ACK with SDP and a = RTP/AVP
Which results in call Failure.
Kindly suggest.
Thanks and Regards,
Ankit
Sample Log:
172.16.104.178--- CUCM IP
203 03082017 185220.724256:1.01.00.11524.Info .SIPCM: *Receive Msg From: 172.16.104.178/55047, len: 1179, sigPort: 1, socket: 161, INVITE sip:7778883001@GMC.testnetwork.com:5061;transport=tls SIP/2.0
1256 03082017 185220.724332:1.01.00.11525.Info .SIPCM: SipFeSocketRecvMsg - msg = INVITE sip:7778883001@GMC.testnetwork.com:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 172.16.104.178:5061;branch=z9hG4bK9daa1bc9e677
From: <sip:6666;phone-context=private@172.16.104.178;user=phone>;tag=50523~b99e7ce0-17e0-435d-b2af-6b4f3d777340-31085640
To: "User1" <sip:7778883001;phone-context=private@172.16.101.116;user=phone>;tag=gK0c00056a
Date: Wed, 08 Mar 2017 13:22:21 GMT
Call-ID: 786434_117374449@172.16.101.116
Supported: timer,resource-priority,replaces
User-Agent: Cisco-CUCM11.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Session-ID: b121eb45885d543ad7a9754f7aa50524;remote=90487b14e315a67d1597e047fab50523
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uac
Min-SE: 1800
P-Asserted-Identity: <sip:6666@172.16.104.178>
Remote-Party-ID: <sip:6666@172.16.104.178>;party=calling;screen=yes;privacy=off
Contact: <sip:72e3376b-f443-8229-299c-18bbe26693ac@172.16.104.178:5061;transport=tls>
Content-Length: 0
SBC response:
139 03082017 185220.727159:1.01.00.11583.Info .SIPCM: *Send Msg to: 172.16.104.178/55047, len: 381, sigPort: 1, socket: 161, 100 Trying
169 03082017 185220.727179:1.01.03.11584.Info .SIPSG: sipsgUtils.c (-1897) 4218. crypto->sdp:sdp strm index:0 ccb audIndex:0 nsd medIndex:0 nsdstream:0x7f002400cc84
473 03082017 185220.727202:1.01.00.11585.Info .SIPCM: SipFeSocketSendMsg - msg = SIP/2.0 100 Trying
Via: SIP/2.0/TLS 172.16.104.178:5061;branch=z9hG4bK9daa1bc9e677
From: <sip:6666;phone-context=private@172.16.104.178;user=phone>;tag=50523~b99e7ce0-17e0-435d-b2af-6b4f3d777340-31085640
To: "User1" <sip:7778883001;phone-context=private@172.16.101.116;user=phone>;tag=gK0c00056a
Call-ID: 786434_117374449@172.16.101.116
CSeq: 101 INVITE
Content-Length: 0
136 03082017 185220.731884:1.01.00.11694.Info .SIPCM: *Send Msg to: 172.16.104.178/55047, len: 1170, sigPort: 1, socket: 161, 200 OK
918 03082017 185220.731932:1.01.00.11695.Info .SIPCM: SipFeSocketSendMsg - msg = SIP/2.0 200 OK
Via: SIP/2.0/TLS 172.16.104.178:5061;branch=z9hG4bK9daa1bc9e677
From: <sip:6666;phone-context=private@172.16.104.178;user=phone>;tag=50523~b99e7ce0-17e0-435d-b2af-6b4f3d777340-31085640
To: "User1" <sip:7778883001;phone-context=private@172.16.101.116;user=phone>;tag=gK0c00056a
Call-ID: 786434_117374449@172.16.101.116
CSeq: 101 INVITE
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "User1" <sip:7778883001@GMC.testnetwork.com:5061;transport=tls>
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE,NOTIFY,PRACK,UPDATE,OPTIONS,MESSAGE,PUBLISH
Require: timer
Supported: timer,precondition,replaces
Session-Expires: 1800;refresher=uac
Content-Length: 336
Content-Disposition: session; handling=required
Content-Type: application/sdp
, msgLen = 818.
423 03082017 185220.731980:1.01.00.11696.Info .SIPCM: SipFeSocketSendMsg - msg = v=0
o=XXXX_UAC 777216 903047 IN IP4 172.16.101.116
s=SIP Media Capabilities
c=IN IP4 172.16.101.116
t=0 0
m=audio 1042 RTP/SAVP 0 101
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AY7+LxsKnQ4IF/rdGnU+Y8XYuX4QwWNoqJeUiYta
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20
a=rtcp:1043
, msgLen = 323.
199 03082017 185220.742497:1.01.00.11697.Info .SIPCM: *Receive Msg From: 172.16.104.178/55047, len: 845, sigPort: 1, socket: 161, ACK sip:7778883001@GMC.testnetwork.com:5061;transport=tls SIP/2.0
737 03082017 185220.742548:1.01.00.11698.Info .SIPCM: SipFeSocketRecvMsg - msg = ACK sip:7778883001@GMC.testnetwork.com:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 172.16.104.178:5061;branch=z9hG4bK9dac333cd61d
From: <sip:6666;phone-context=private@172.16.104.178;user=phone>;tag=50523~b99e7ce0-17e0-435d-b2af-6b4f3d777340-31085640
To: "User1" <sip:7778883001;phone-context=private@172.16.101.116;user=phone>;tag=gK0c00056a
Date: Wed, 08 Mar 2017 13:22:21 GMT
Call-ID: 786434_117374449@172.16.101.116
User-Agent: Cisco-CUCM11.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Session-ID: b121eb45885d543ad7a9754f7aa50524;remote=90487b14e315a67d1597e047fab50523
Content-Type: application/sdp
Content-Length: 194
, msgLen = 637.
284 03082017 185220.742591:1.01.00.11699.Info .SIPCM: SipFeSocketRecvMsg - msg = v=0
o=CiscoSystemsCCM-SIP 50523 2 IN IP4 172.16.104.178
s=SIP Call
c=IN IP4 172.16.104.178
t=0 0
m=audio 4000 RTP/AVP 0
a=X-cisco-media:umoh
a=ptime:20
a=rtpmap:0 PCMU/8000
a=sendonly
, msgLen = 184.
03-08-2017 06:43 AM
Hi Ankit,
Can you post a set of CCM trace for the issue?
Mention calling, called number and timestamp of the issue.
Kindly check if you are affected by something similar to this bug:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq84875/?reffering_site=dumpcr
Regards,
Hitesh
03-08-2017 07:07 AM
05-13-2019 02:24 PM
I am running into this same problem. Did you ever resolve this?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide