09-05-2023 01:00 AM - last edited on 09-05-2023 02:41 AM by rupeshah
Hi all,
i have a situation where the webex app sends a Cancel in the SIP message before the call to the PSTn completes. Any ideas why this is happening.
Sep 5 07:36:50.087: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+xxx;transport=tls;dtg=ipnx2023_lgu SIP/2.0
Via:SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From:"Info info"<sip:+xxx;user=phone>;tag=1244987949-1693899410023-
To:<sip:+xxx@eun10.bcld.webex.com;user=phone>
Call-ID:xxx
CSeq:100 INVITE
Contact:<sip:170.72.17.196:8934;transport=tls>
P-Asserted-Identity:"Info info"<sip:+xxx@10.247.249.9;user=phone>
Privacy:none
Supported:100rel
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Recv-Info:x-broadworks-client-session-info,x-cisco-mute-status
X-BroadWorks-Correlation-Info:2ea6b843-e089-4859-8939-f0bae7ee3f26
Accept:application/dtmf-relay,application/media_control+xml,application/sdp,multipart/mixed
Max-Forwards:69
Session-ID:xxx;remote=00000000000000000000000000000000
Content-Type:application/sdp
Content-Length:1431
v=0
o=BroadWorks xxx IN IP4 170.72.17.203
s=-
c=IN IP4 170.72.17.203
t=0 0
a=cisco-mari:v1
a=cisco-mari-rate
a=cisco-mari-rtx:v0
a=cisco-mari-hybrid-resilience:v0
m=audio 37852 RTP/SAVP 99 9 8 0 18 102 101 111 112
a=sendrecv
a=rtpmap:99 opus/48000/2
a=rtpmap:9 G722/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:102 iLBC/8000
a=fmtp:102 mode=30
a=rtpmap:101 telephone-event/8000
a=rtpmap:111 x-ulpfecuc/8000
a=fmtp:111 max_esel=1400;max_n=255;m=8;multi_ssrc=1;FEC_ORDER=FEC_SRTP;non_seq=1;feedback=0
a=rtpmap:112 mari-rtx/90000
a=fmtp:112 RTX_ORDER=RTX_SRTP;rtx-time=180
a=extmap:4/sendrecv http://protocols.cisco.com/timestamp#100us
a=extmap:9/sendrecv http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time
a=rtcp-mux
a=rtcp-xr:rcvr-rtt=all voip-metrics
a=ice-ufrag:aC4J
a=ice-pwd:xxx
a=candidate:1 1 UDP 2113935615 172.20.15.69 8596 typ host
a=candidate:1 2 UDP 2113935614 172.20.15.69 8597 typ host
a=candidate:3 1 UDP 1677727999 41.251.55.175 8596 typ srflx raddr 172.20.15.69 rport 8596
a=candidate:3 2 UDP 1677727998 41.251.55.175 8597 typ srflx raddr 172.20.15.69 rport 8597
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
a=candidate:mse 1 UDP 16777215 170.72.17.203 37852 typ relay
a=candidate:mse 2 UDP 16777214 170.72.17.203 37853 typ relay
Timestamp: 3776744210087
UTC Timestamp:3776744210087
Sep 5 07:36:50.094: //191/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From: "Info info"<sip:+xxx;user=phone>;tag=1244987949-1693899410023-
To: <sip:+xxx@eun10.bcld.webex.com;user=phone>
Date: Tue, 05 Sep 2023 07:36:50 GMT
Call-ID: xxx
CSeq: 100 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-17.6.3a
Session-ID: 00000000000000000000000000000000;remote=xxx
Content-Length: 0
Timestamp: 3776744210094
UTC Timestamp:3776744210094
Sep 5 07:36:50.231: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:xxx@sip.ipnxtelecoms.com:5060 SIP/2.0
Via: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK791FA8
Remote-Party-ID: "Info info" <sip:xxx@105.235.207.178>;party=calling;screen=yes;privacy=off
From: "Info info" <sip:xxx@sip.xxx.com:5060>;tag=2FD690-251
To: <sip:012716816@sip.xxx.com>
Date: Tue, 05 Sep 2023 07:36:50 GMT
Call-ID: xxx
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3478372920-1257574894-2156842466-0749259353
User-Agent: Cisco-SIPGateway/IOS-17.6.3a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1693899410
Contact: <sip:xxx@105.235.207.178:5060>
Expires: 180
Allow-Events: kpml, telephone-event
Max-Forwards: 68
Session-ID: xxx;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 326
v=0
o=CiscoSystemsSIP-GW-UserAgent 9261 1671 IN IP4 105.235.207.178
s=SIP Call
c=IN IP4 105.235.207.178
t=0 0
m=audio 8026 RTP/AVP 8 0 18 101
c=IN IP4 105.235.207.178
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Timestamp: 3776744210231
UTC Timestamp:3776744210231
Sep 5 07:36:50.263: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
v: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK791FA8
f: "Info info" <sip:xxx@sipxxx.com:5060>;tag=2FD690-251
t: <sip:012716816@sip.xxx.com>
i: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
CSeq: 101 INVITE
Server: CommuniGatePro/5.4.6 _community_
l: 0
Timestamp: 3776744210263
UTC Timestamp:3776744210263
Sep 5 07:36:52.799: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Authentication required
v: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK791FA8
f: "Info info" <sip:016310967@sip.xxx.com:5060>;tag=2FD690-251
t: <sip:012716816@sip.xxx.com>;tag=5839A2C7
i: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
CSeq: 101 INVITE
WWW-Authenticate: Digest realm="xxx.net",nonce="46ED531B44EF4262C335",opaque="opaq",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.4.6
l: 0
Timestamp: 3776744212799
UTC Timestamp:3776744212799
Sep 5 07:36:52.801: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:012716816@sip.xxx.com:5060 SIP/2.0
Via: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK791FA8
From: "Info info" <sip:016310967@sip.xxx.com>;tag=2FD690-251
To: <sip:012716816@sip.xxx.com>;tag=5839A2C7
Date: Tue, 05 Sep 2023 07:36:50 GMT
Call-ID: xxx
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: kpml, telephone-event
Session-ID: xxx;remote=00000000000000000000000000000000
Content-Length: 0
Timestamp: 3776744212801
UTC Timestamp:3776744212801
Sep 5 07:36:52.801: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:012716816@sip.xxx.com:5060 SIP/2.0
Via: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
Remote-Party-ID: "Info info" <sip:xxx@105.235.207.178>;party=calling;screen=yes;privacy=off
From: "Info info" <sip:016310967@sip.xxx.com:5060>;tag=2FD690-251
To: <sip:012716816@sip.xxx.com>
Date: Tue, 05 Sep 2023 07:36:52 GMT
Call-ID: xxx
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3478372920-1257574894-2156842466-0749259353
User-Agent: Cisco-SIPGateway/IOS-17.6.3a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1693899412
Contact: <sip:016310967@105.235.207.178:5060>
Expires: 180
Allow-Events: kpml, telephone-event
Authorization: Digest username="016310967",realm="xxx.net",uri="sip:012716816@sip.xxx.com:5060",response="3baf517a35dac02b5135f62ee379e7e6",nonce="46ED531B44EF4262C335",opaque="opaq",cnonce="CE922FDF",qop=auth,algorithm=MD5,nc=00000001
Max-Forwards: 68
Session-ID: xxx;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 326
v=0
o=CiscoSystemsSIP-GW-UserAgent 9261 1671 IN IP4 105.235.207.178
s=SIP Call
c=IN IP4 105.235.207.178
t=0 0
m=audio 8026 RTP/AVP 8 0 18 101
c=IN IP4 105.235.207.178
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Timestamp: 3776744212801
UTC Timestamp:3776744212801
Sep 5 07:36:52.826: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
v: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
f: "Info info" <sip:016310967@sip.xxx.com:5060>;tag=2FD690-251
t: <sip:012716816@sip.xxx.com>
i: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
CSeq: 102 INVITE
Server: CommuniGatePro/5.4.6 _community_
l: 0
Timestamp: 3776744212826
UTC Timestamp:3776744212826
Sep 5 07:37:02.080: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:+23412716816@105.235.207.178:5061;transport=tls;dtg=ipnx2023_lgu SIP/2.0
Via:SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From:"Info info"<sip:+23416310967@170.72.17.196;user=phone>;tag=1244987949-1693899410023-
To:<sip:+23xx@eun10.bcld.webex.com;user=phone>
Call-ID:xxx
CSeq:100 CANCEL
X-BroadWorks-Correlation-Info:2ea6b843-e089-4859-8939-f0bae7ee3f26
Max-Forwards:69
Session-ID:xxx;remote=00000000000000000000000000000000
Content-Length:0
Timestamp: 3776744222080
UTC Timestamp:3776744222080
Sep 5 07:37:02.083: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:012716816@sip.xxx.com:5060 SIP/2.0
Via: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
From: "Info info" <sip:016310967@sip.xxx.com>;tag=2FD690-251
To: <sip:012716816@sip.xxx.com>
Date: Tue, 05 Sep 2023 07:36:52 GMT
Call-ID: xxx
CSeq: 102 CANCEL
Max-Forwards: 70
Timestamp: 1693899422
Content-Length: 0
Timestamp: 3776744222083
UTC Timestamp:3776744222083
Sep 5 07:37:02.084: //191/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From: "Info info"<sip:+23416310967@170.72.17.196;user=phone>;tag=1244987949-1693899410023-
To: <sip:+23412716816@eun10.bcld.webex.com;user=phone>
Date: Tue, 05 Sep 2023 07:37:02 GMT
Call-ID: xxx
CSeq: 100 CANCEL
Session-ID: 00000000000000000000000000000000;remote=3xxx
Content-Length: 0
Timestamp: 3776744222084
UTC Timestamp:3776744222084
Sep 5 07:37:02.084: //191/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From: "Info info"<sip:+23416310967@170.72.17.196;user=phone>;tag=1244987949-1693899410023-
To: <sip:+23412716816@eun10.bcld.webex.com;user=phone>;tag=3004DC-C8D
Date: Tue, 05 Sep 2023 07:37:02 GMT
Call-ID: xxx
CSeq: 100 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-17.6.3a
Reason: Q.850;cause=16
Session-ID: xxx;remote=00000000000000000000000000000000
Content-Length: 0
Timestamp: 3776744222084
UTC Timestamp:3776744222084
Sep 5 07:37:02.097: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 487 Request cancelled
v: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
f: "Info info" <sip:016310967@sipxxx.com:5060>;tag=2FD690-251
t: <sip:012716816@sip.xxx.com>;tag=6BC4FDFA
i: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
CSeq: 102 INVITE
Server: CommuniGatePro/5.4.6 _community_
l: 0
Timestamp: 3776744222097
UTC Timestamp:3776744222097
Sep 5 07:37:02.098: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
v: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
f: "Info info" <sip:016310967@sip.xxx.com>;tag=2FD690-251
t: <sip:012716816@sip.xxx.com>;tag=6BC4FDFA
i: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
CSeq: 102 CANCEL
Server: CommuniGatePro/5.4.6 _community_
l: 0
Timestamp: 3776744222098
UTC Timestamp:3776744222098
Sep 5 07:37:02.099: //192/CF53C238808E/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:012716816@sip.xxx.com:5060 SIP/2.0
Via: SIP/2.0/UDP 105.235.207.178:5060;branch=z9hG4bK7A13E0
From: "Info info" <sip:016310967@sip.xxs.com>;tag=2FD690-251
To: <sip:012716816@sip.xxs.com>;tag=6BC4FDFA
Date: Tue, 05 Sep 2023 07:36:52 GMT
Call-ID: CF55489C-4AF511EE-8094CDE2-2CA8CA59@105.235.207.178
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: kpml, telephone-event
Session-ID: xxx;remote=00000000000000000000000000000000
Content-Length: 0
Timestamp: 3776744222099
UTC Timestamp:3776744222099
Sep 5 07:37:02.218: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+23412716816@105.235.207.178:5061;transport=tls;dtg=ipnx2023_lgu SIP/2.0
Via:SIP/2.0/TLS 170.72.17.196:8934;branch=z9hG4bKBroadworksSSE.-105.235.207.178V23126-0-100-1244987949-1693899410023-
From:"Info info"<sip:+23416310967@170.72.17.196;user=phone>;tag=1244987949-1693899410023-
To:<sip:+23412716816@eun10.bcld.webex.com;user=phone>;tag=3004DC-C8D
Call-ID:xxx
CSeq:100 ACK
Session-ID:00000000000000000000000000000000;remote=3xxx
Max-Forwards:10
Content-Length:0
Timestamp: 3776744222218
UTC Timestamp:3776744222218
--Paul
12-18-2023 04:08 PM
Were you able to solve your problem? I have the same scenario and I see that the cacel is sent by WxC since it does not receive SIP messages for 12 seconds
09-12-2023 10:03 AM
What does you setuo look like? Do you have a LGW for you Webex Calling users? Is the LGW also connected to a UCM?
In your SIP trace, which ip address is what (device, LGW, UCM, itsp..)?
In case you've the setup itsp<->LGW<->WxC<->device, have you configured the LGW according to the guide?
09-12-2023 01:16 PM - edited 09-12-2023 01:17 PM
Many thanks for responding.
What does you setuo look like? Do you have a LGW for you Webex Calling users? Is the LGW also connected to a UCM?
Yes LGW is setup. I connected it to UCM to test calling using the same ITSP and the call is successful
In your SIP trace, which ip address is what (device, LGW, UCM, itsp..)?
device - 170.72.17.196,
LGW - 105.235.207.178,
UCM - This is not in the trace and UCM is not in the call path. This call is from the Webex App,
itsp - sip.ipnxtelecoms.com..
In case you've the setup itsp<->LGW<->WxC<->device, have you configured the LGW according to the guide?
The LGW is setup exactly according to the guide and works fine for incoming call.
09-08-2023 03:27 PM
I set up a phone on CUCM to route calls to the same CUBE without changing the CUBE configuration and the calls completed successfully but when i make the same call using Webex, the call fails.
Can anyone help?
--Paul
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