Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
257
Views
1
Helpful
3
Replies

CUBE sending BYE to the provider after mobile phone is answered

goranpilat
Level 3
Level 3

‎09-13-2024 04:34 AM - edited ‎09-13-2024 04:35 AM

Hi

I have setup as simple as it gets: CUCM, CUBE 4331, SIP trunk to the provider through CUBE. 711a all the way through. When I call mobile phone from CUCM, phone rings, but as soon as I answer it it is disconnected. I see on CUBE that immediately after receiving 200OK, CUBE sent BYE to the provider. At the same time CUBE sent 503 service unavailable to the CUCM. This happens every call, and started by itself for no apparent reason couple days ago. Funny thing is, it only happens with two mobile providers. Third mobile provider (which uses same CUBE, trunk, dial-peers etc) works fine, there is no disconnecting. Please can somebody advise me which debugging to use on CUBE to catch the root cause of it sending BYE message

 

Thanks a lot

Labels:
0 Helpful
3 Replies 3

Roger Kallberg
VIP
VIP

‎09-13-2024 04:46 AM

I would suggest that you turn on debug ccsip messages and debug ccsip media, possibly debug voip ccapi inout, but I don’t think it’s needed.



Response Signature


0 Helpful

goranpilat
Level 3
Level 3
In response to Roger Kallberg

‎09-17-2024 12:57 AM - edited ‎09-17-2024 01:06 AM

Hi, please find the traces for both success and unsuccess. for some reason I cannot attach the files

SUCCESFUl

CUBE_DR#
Sep 13 12:14:56: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:0981XXX840@10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105b3207f7ded
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>
Date: Fri, 13 Sep 2024 10:14:55 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM14.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Session-ID: 257e3cf20b594ba78377f03150dceba0;remote=00000000000000000000000000000000
Cisco-Guid: 0074891008-0000065536-0000003271-0202801162
Session-Expires: 3600
P-Asserted-Identity: <sip:+3853XXX7201@10.128.22.12>
Remote-Party-ID: <sip:+3853XXX7201@10.128.22.12>;party=calling;screen=yes;privacy=off
Contact: <sip:+3853XXX7201@10.128.22.12:5060;transport=tcp>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 202

v=0
o=CiscoSystemsCCM-SIP 2240833 1 IN IP4 10.128.22.12
s=SIP Call
c=IN IP4 10.130.8.36
t=0 0
m=audio 37428 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Sep 13 12:14:56: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0981XXX840@192.168.135.63:5060 SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343071385
Remote-Party-ID: <sip:+3853XXX7201@10.228.254.9>;party=calling;screen=yes;privacy=off
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>
Date: Fri, 13 Sep 2024 12:14:56 GMT
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0074891008-0000065536-0000003271-0202801162
User-Agent:Cisco-CUCM_fake
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1726222496
Contact: <sip:+3853XXX7201@10.228.254.9:5060>
Call-Info: <sip:10.228.254.9:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 3600
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 5949 5199 IN IP4 10.228.254.9
s=SIP Call
c=IN IP4 10.228.254.9
t=0 0
m=audio 29560 RTP/AVP 8 101
c=IN IP4 10.228.254.9
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:14:56: //18273293/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105b3207f7ded
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>
Date: Fri, 13 Sep 2024 12:14:56 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Length: 0


Sep 13 12:14:56: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343071385
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222496
Content-Length: 0


CUBE_DR#
Sep 13 12:14:57: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.11:5060;branch=z9hG4bK38252e187733a1
From: <sip:10.128.22.11>;tag=1665086007
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:14:57 GMT
Call-ID: 5a7ec00-1f018fbc-38252f-b16800a@10.128.22.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.128.22.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


CUBE_DR#
Sep 13 12:15:00: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105c544aa75e3
From: <sip:10.128.22.12>;tag=1074872890
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:14:59 GMT
Call-ID: 6d91900-1f018fbc-9fa9-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.128.22.12:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Sep 13 12:15:00: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105c544aa75e3
From: <sip:10.128.22.12>;tag=1074872890
To: <sip:10.228.22.2>;tag=CFFAE223-86B
Date: Fri, 13 Sep 2024 12:15:00 GMT
Call-ID: 6d91900-1f018fbc-9fa9-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 369

v=0
o=CiscoSystemsSIP-GW-UserAgent 7912 8813 IN IP4 10.228.22.2
s=SIP Call
c=IN IP4 10.228.22.2
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 10.228.22.2
m=image 0 udptl t38
c=IN IP4 10.228.22.2
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Sep 13 12:15:00: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343071385
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>;tag=65055371-1726222500141
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222496
Contact: <sip:192.168.135.63:5060;transport=udp>
P-Asserted-Identity: <sip:0981XXX840@np.ht.hr;user=phone>
P-Charging-Vector: icid-value=b4e0b1b8056e2348aa7b29e2a9323347
P-Early-Media: inactive
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE,SUBSCRIBE
Supported: norefersub,timer
Content-Length: 0


Sep 13 12:15:00: //18273293/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105b3207f7ded
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 12:14:56 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
CSeq: 101 INVITE
Require: 100rel
RSeq: 1001
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:0981XXX840@10.228.22.2>;party=called;screen=no;privacy=off
Contact: <sip:0981XXX840@10.228.22.2:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Length: 0


Sep 13 12:15:00: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:0981XXX840@10.228.22.2:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105c63e9db652
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 10:14:55 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
CSeq: 102 PRACK
RAck: 1001 101 INVITE
Allow-Events: presence
Max-Forwards: 70
Content-Length: 0


Sep 13 12:15:00: //18273293/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:

CUBE_DR#SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105c63e9db652
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 12:15:00 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 PRACK
Content-Length: 0


CUBE_DR#
Sep 13 12:15:04: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343071385
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>;tag=65055371-1726222500141
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222496
Require: timer
Session-Expires: 1800;refresher=uas
Contact: <sip:192.168.135.63:5060;transport=udp>
P-Asserted-Identity: <sip:+385981931840@np.ht.hr;user=phone>
P-Charging-Vector: icid-value=b4e0b1b8056e2348aa7b29e2a9323347
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE,SUBSCRIBE
Accept: application/media_control+xml,application/sdp
Supported: norefersub,timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 241

v=0
o=BroadWorks 1000941565 1 IN IP4 192.168.135.63
s=-
c=IN IP4 192.168.135.63
t=0 0
m=audio 25620 RTP/AVP 8 101
b=AS:80
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=maxptime:30
a=bsoft: 1 image udptl t38
a=ptime:20

Sep 13 12:15:04: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:192.168.135.63:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK834309240A
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>;tag=65055371-1726222500141
Date: Fri, 13 Sep 2024 12:14:56 GMT
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


Sep 13 12:15:04: //18273293/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105b3207f7ded
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 12:15:00 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:0981XXX840@10.228.22.2>;party=called;screen=no;privacy=off
Contact: <sip:0981XXX840@10.228.22.2:5060;transport=tcp>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244

v=0
o=CiscoSystemsSIP-GW-UserAgent 2857 9725 IN IP4 10.228.22.2
s=SIP Call
c=IN IP4 10.228.22.2
t=0 0
m=audio 34124 RTP/AVP 8 101
c=IN IP4 10.228.22.2
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:15:04: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#ACK sip:0981XXX840@10.228.22.2:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105cb2f48dcd9
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 10:14:55 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0


CUBE_DR#
Sep 13 12:15:07: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:0981XXX840@10.228.22.2:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105d36b1a304
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 10:14:55 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
P-Asserted-Identity: <sip:+3853XXX7201@10.128.22.12>
CSeq: 103 BYE
Reason: Q.850;cause=16
Session-ID: 257e3cf20b594ba78377f03150dceba0;remote=16b8d767f6121f9252b873eab2240833
Content-Length: 0


Sep 13 12:15:07: //18273293/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105d36b1a304
From: <sip:+3853XXX7201@10.128.22.12>;tag=2240833~0b80f267-60ed-484a-ab60-588f7c326c8e-42800237
To: <sip:0981XXX840@10.228.22.2>;tag=CFFAE232-C9E
Date: Fri, 13 Sep 2024 12:15:07 GMT
Call-ID: 476bf00-1f018fbc-9fa0-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 103 BYE
Reason: Q.850;cause=16
Content-Length: 0


Sep 13 12:15:07: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:192.168.135.63:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430A1177
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>;tag=65055371-1726222500141
Date: Fri, 13 Sep 2024 12:14:56 GMT
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Max-Forwards: 70
Timestamp: 1726222507
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0


Sep 13 12:15:07: //18273294/0476BF000000/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430A1177
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFAD0AF-14FD
To: <sip:0981XXX840@192.168.135.63>;tag=65055371-1726222500141
Call-ID: DBE027F6-70EF11EF-9520EA00-FD885823@10.228.254.9
Timestamp: 1726222507
CSeq: 102 BYE
Content-Length: 0


Sep 13 12:15:07: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#
CUBE_DR#OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.11:5060;branch=z9hG4bK3825306c38787e
From: <sip:10.128.22.11>;tag=107621154
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:15:07 GMT
Call-ID: b9dcd00-1f018fbc-382531-b16800a@10.128.22.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.128.22.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


CUBE_DR#
CUBE_DR#
CUBE_DR#
CUBE_DR#
Sep 13 12:15:11: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.228.22.11:5060;branch=z9hG4bKcb6d136245dce
From: <sip:10.228.22.11>;tag=1242030606
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:15:11 GMT
Call-ID: e002700-1f018fbc-cb57e-b16e40a@10.228.22.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.228.22.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Sep 13 12:15:11: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.228.22.11:5060;branch=z9hG4bKcb6d136245dce
From: <sip:10.228.22.11>;tag=1242030606
To: <sip:10.228.22.2>;tag=CFFB0ECC-1632
Date: Fri, 13 Sep 2024 12:15:11 GMT
Call-ID: e002700-1f018fbc-cb57e-b16e40a@10.228.22.11
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,re
CUBE_DR#places,sdp-anat
Content-Type: application/sdp
Content-Length: 369

v=0
o=CiscoSystemsSIP-GW-UserAgent 7076 1374 IN IP4 10.228.22.2
s=SIP Call
c=IN IP4 10.228.22.2
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 10.228.22.2
m=image 0 udptl t38
c=IN IP4 10.228.22.2
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

UNSUCCESSFUL

 

UNSUCCESSFUL

 

CUBE_DR#
Sep 13 12:15:14: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:093XXX2211@10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>
Date: Fri, 13 Sep 2024 10:15:13 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM14.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Session-ID: 257e3cf20b594ba78377f03150dceba0;remote=00000000000000000000000000000000
Cisco-Guid: 0254891008-0000065536-0000003276-0202801162
Session-Expires: 3600
P-Asserted-Identity: <sip:+3853XXX7201@10.128.22.12>
Remote-Party-ID: <sip:+3853XXX7201@10.128.22.12>;party=calling;screen=yes;privacy=off
Contact: <sip:+3853XXX7201@10.128.22.12:5060;transport=tcp>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 202

v=0
o=CiscoSystemsCCM-SIP 2241529 1 IN IP4 10.128.22.12
s=SIP Call
c=IN IP4 10.130.8.36
t=0 0
m=audio 38130 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Sep 13 12:15:14: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:093XXX2211@192.168.135.63:5060 SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
Remote-Party-ID: <sip:+3853XXX7201@10.228.254.9>;party=calling;screen=yes;privacy=off
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>
Date: Fri, 13 Sep 2024 12:15:14 GMT
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0254891008-0000065536-0000003276-0202801162
User-Agent:Cisco-CUCM_fake
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1726222514
Contact: <sip:+3853XXX7201@10.228.254.9:5060>
Call-Info: <sip:10.228.254.9:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 3600
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 2344 7261 IN IP4 10.228.254.9
s=SIP Call
c=IN IP4 10.228.254.9
t=0 0
m=audio 32210 RTP/AVP 8 101
c=IN IP4 10.228.254.9
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:15:14: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>
Date: Fri, 13 Sep 2024 12:15:14 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Length: 0


Sep 13 12:15:14: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222514
Content-Length: 0


CUBE_DR#
Sep 13 12:15:16: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=759856528-1726222516416
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222514
Supported: timer
Contact: <sip:192.168.135.63:5060;transport=udp>
Session: Media
P-Asserted-Identity: <sip:093XXX2211@xx.xx.xx;user=phone>
P-Charging-Vector: icid-value=dc7bff81dc91bfea69c9b1e6104c723c
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE,SUBSCRIBE
User-Agent: I-SBC
Content-Type: application/sdp
Content-Length: 271

v=0
o=BroadWorks 1000943668 1 IN IP4 192.168.135.63
s=-
c=IN IP4 192.168.135.63
t=0 0
a=sendrecv
m=audio 26272 RTP/AVP 8 101
c=IN IP4 192.168.135.63
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=bsoft: 1 image udptl t38
a=ptime:20

Sep 13 12:15:16: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 12:15:14 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
CSeq: 101 INVITE
Require: 100rel
RSeq: 1367
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:093XXX2211@10.228.22.2>;party=called;screen=yes;privacy=off
Contact: <sip:093XXX2211@10.228.22.2:5060;transport=tcp>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244

v=0
o=CiscoSystemsSIP-GW-UserAgent 9122 2069 IN IP4 10.228.22.2
s=SIP Call
c=IN IP4 10.228.22.2
t=0 0
m=audio 33290 RTP/AVP 8 101
c=IN IP4 10.228.22.2
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:15:16: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:093XXX2211@10.228.22.2:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105f2380f2733
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 10:15:13 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
CSeq: 102 PRACK
RAck: 1367 101 INVITE
Allow-Events: presence
Max-Forwards: 70
Content-Length: 0


Sep 13 12:15:16: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105f2380f2733
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 12:15:16 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 PRACK
Content-Length: 0


Sep 13 12:15:16: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=404570692-1726222516453
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222514
Supported: timer
Contact: <sip:192.168.135.63:5060;transport=udp>
P-Asserted-Identity: <sip:093XXX2211@xx.xx.xx;user=phone>
P-Early-Media: sendonly
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE,SUBSCRIBE
Content-Type: application/sdp
Content-Length: 231
P-Charging-Vector: icid-value=dc7bff81dc91bfea69c9b1e6104c723c

v=0
o=BroadWorks 1000943668 2 IN IP4 192.168.135.63
s=-
c=IN IP4 192.168.135.63
t=0 0
m=audio 26272 RTP/AVP 8 101
c=IN IP4 192.168.135.63
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:15:16: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 12:15:16 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
CSeq: 101 INVITE
Require: 100rel
RSeq: 1368
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:093XXX2211@10.228.22.2>;party=called;screen=yes;privacy=off
Contact: <sip:093XXX2211@10.228.22.2:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Length: 0


Sep 13 12:15:16: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:093XXX2211@10.228.22.2:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105f34e4d8ff
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 10:15:13 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
CSeq: 103 PRACK
RAck: 1368 101 INVITE
Allow-Events: presence
Max-Forwards: 70
Content-Length: 0


Sep 13 12:15:16: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:

CUBE_DR#SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105f34e4d8ff
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 12:15:16 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 103 PRACK
Content-Length: 0


Sep 13 12:15:16: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=759856528-1726222516416
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222514
Supported: timer
Contact: <sip:192.168.135.63:5060;transport=udp>
P-Asserted-Identity: <sip:093XXX2211@xx.xx.xx;user=phone>
P-Charging-Vector: icid-value=dc7bff81dc91bfea69c9b1e6104c723c
P-Early-Media: inactive
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE
User-Agent: I-SBC
Content-Length: 0


CUBE_DR#
Sep 13 12:15:18: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.11:5060;branch=z9hG4bK382532769c5f1d
From: <sip:10.128.22.11>;tag=1954714441
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:15:17 GMT
Call-ID: 1193ae00-1f018fbc-382533-b16800a@10.128.22.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.128.22.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Sep 13 12:15:18: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430E193E
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=500667883-1726222519109
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
CSeq: 101 INVITE
Timestamp: 1726222514
Require: timer
Session-Expires: 1800;refresher=uas
Supported: timer
Contact: <sip:192.168.135.63:5060;transport=udp>
P-Asserted-Identity: <sip:093XXX2211@xx.xx.xx;user=phone>
P-Charging-Vector: icid-value=dc7bff81dc91bfea69c9b1e6104c723c
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE,SUBSCRIBE
Accept: application/media_control+xml,application/sdp
User-Agent: I-SBC
Content-Type: application/sdp
Content-Length: 271

v=0
o=BroadWorks 1000943668 3 IN IP4 192.168.135.63
s=-
c=IN IP4 192.168.135.63
t=0 0
a=sendrecv
m=audio 26272 RTP/AVP 8 101
c=IN IP4 192.168.135.63
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=bsoft: 1 image udptl t38
a=ptime:20

Sep 13 12:15:19: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
UPDATE sip:+3853XXX7201@10.128.22.12:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.228.22.2:5060;branch=z9hG4bK834310DE6
From: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
To: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
Date: Fri, 13 Sep 2024 12:15:16 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Max-Forwards: 70
Supported: timer,resource-priority,replaces,sdp-anat
Timestamp: 1726222519
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 UPDATE
Contact: <sip:093XXX2211@10.228.22.2:5060;transport=tcp>
Min-SE: 1800
Remote-Party-ID: <sip:093XXX2211@10.228.22.2>;party=called;screen=yes;privacy=off
Content-Type: application/sdp
Content-Length: 244

v=0
o=CiscoSystemsSIP-GW-UserAgent 9122 2069 IN IP4 10.228.22.2
s=SIP Call
c=IN IP4 10.228.22.2
t=0 0
m=audio 33290 RTP/AVP 8 101
c=IN IP4 10.228.22.2
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sep 13 12:15:19: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:192.168.135.63:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK83430FB5F
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=500667883-1726222519109
Date: Fri, 13 Sep 2024 12:15:14 GMT
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


Sep 13 12:15:19: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 12:15:16 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Reason: Q.850;cause=47
Content-Length: 0


Sep 13 12:15:19: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:192.168.135.63:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343111AC
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=500667883-1726222519109
Date: Fri, 13 Sep 2024 12:15:14 GMT
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Max-Forwards: 70
Timestamp: 1726222519
CSeq: 102 BYE
Reason: Q.850;cause=47
Content-Length: 0


Sep 13 12:15:19: //18273301/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.228.22.2:5060;branch=z9hG4bK834310DE6
From: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
To: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
Date: Fri, 13 Sep 2024 10:15:18 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
Server: Cisco-CUCM14.0
CSeq: 101 UPDATE
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: 257e3cf20b594ba78377f03150dceba0;remote=16b8d767f6121f9252b873eab2241529
P-Asserted-Identity: <sip:+3853XXX7201@10.128.22.12>
Remote-Party-ID: <sip:+3853XXX7201@10.128.22.12>;party=called;screen=yes;privacy=off
Contact: <sip:093XXX2211@10.128.22.12:5060;transport=tcp>
Content-Type: application/sdp
Content-Length: 246

v=0
o=CiscoSystemsCCM-SIP 2241529 2 IN IP4 10.128.22.12
s=SIP Call
c=IN IP4 10.130.8.36
b=TIAS:64000
b=CT:64
b=AS:80
t=0 0
m=audio 38130 RTP/AVP 8 101
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Sep 13 12:15:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:093XXX2211@10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK105e7409ea0d3
From: <sip:+3853XXX7201@10.128.22.12>;tag=2241529~0b80f267-60ed-484a-ab60-588f7c326c8e-42800291
To: <sip:093XXX2211@10.228.22.2>;tag=CFFB1FF0-24AA
Date: Fri, 13 Sep 2024 10:15:18 GMT
Call-ID: f315400-1f018fbc-9fb6-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0


Sep 13 12:15:19: //18273302/0F3154000000/SIP/Msg/ccsipDisplayMsg:
Received:

CUBE_DR#SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.228.254.9:5060;branch=z9hG4bK8343111AC
From: <sip:+3853XXX7201@10.228.254.9>;tag=CFFB1779-1035
To: <sip:093XXX2211@192.168.135.63>;tag=500667883-1726222519109
Call-ID: E6AD8171-70EF11EF-952CEA00-FD885823@10.228.254.9
Timestamp: 1726222519
CSeq: 102 BYE
Content-Length: 0


CUBE_DR#
Sep 13 12:15:20: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: cdna] [Source: 10.228.255.147] [localport: 22] at 12:15:20 MET-DST Fri Sep 13 2024
Sep 13 12:15:21: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.228.22.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK1060686d4e7d
From: <sip:10.128.22.12>;tag=958999334
To: <sip:10.228.22.2>
Date: Fri, 13 Sep 2024 10:15:20 GMT
Call-ID: 135d7180-1f018fbc-9fc3-c16800a@10.128.22.12
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:10.128.22.12:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Sep 13 12:15:21: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.128.22.12:5060;branch=z9hG4bK1060686d4e7d
From: <sip:10.128.22.12>;tag=958999334
To: <sip:10.228.22.2>;tag=CFFB338D-187D
Date: Fri, 13 Sep 2024 12:15:21 GMT
Call-ID: 135d7180-1f018fbc-9fc3-c16800a@10.128.22.12
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,repl

DIAL PEERS:

dial-peer voice 10 voip
description From CUCM to CUBE
session protocol sipv2
session transport tcp
incoming called-number .
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
no vad
!
dial-peer voice 20 voip
description ***From CUBE to CUCM***
destination-pattern +385........
session protocol sipv2
session target ipv4:10.XXX.22.12
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 20 down-interval 10 retry 3
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
!
dial-peer voice 21 voip
description From ***CUBE to CUCM***
preference 5
destination-pattern +385........
session protocol sipv2
session target ipv4:10.XXX.22.13
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 20 down-interval 10 retry 3
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
!
dial-peer voice 22 voip
description From ***CUBE to CUCM***
preference 7
destination-pattern +385........
session protocol sipv2
session target ipv4:10.XXX.22.11
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 20 down-interval 10 retry 3
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
!
dial-peer voice 30 voip
description ***From HT to CUBE***
call-block translation-profile incoming BLOCK_INCOMING
call-block disconnect-cause incoming unassigned-number
session protocol sipv2
incoming called-number +385........
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0/1
voice-class sip bind media source-interface GigabitEthernet0/0/1
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
!
dial-peer voice 40 voip
description ***From CUBE to SBC***
destination-pattern [0-9]T
session protocol sipv2
session target ipv4:192.168.135.62
voice-class codec 1
no voice-class sip asserted-id
voice-class sip early-offer forced
voice-class sip profiles 10
voice-class sip bind control source-interface GigabitEthernet0/0/1
voice-class sip bind media source-interface GigabitEthernet0/0/1
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
no vad
!
dial-peer voice 50 voip
description ***From CUBE to SBC***
preference 5
destination-pattern [0-9]T
session protocol sipv2
session target ipv4:192.168.135.162
voice-class codec 1
voice-class sip early-offer forced
voice-class sip profiles 10
voice-class sip bind control source-interface GigabitEthernet0/0/1
voice-class sip bind media source-interface GigabitEthernet0/0/1
dtmf-relay rtp-nte sip-notify
fax-relay sg3-to-g3
fax rate 9600
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
no vad
!
!

 

0 Helpful

Shalid Kurunnan Chalil
Spotlight
Spotlight

‎09-13-2024 08:19 AM

Hi there, 

Please provide the debug ccsip messages logs as suggested by @Roger Kallberg . 

Off the top of my head, it seems there may be changes in the DSP attributes within the 200 OK SIP message for calls to this specific provider, which the CUBE may not be handling well under the current configuration.

It would be helpful to compare the logs of both successful and failed calls to see if there are any differences that could point to the issue.  If you can share the debug ccsip message logs here, we may able to assist you further. 

Regards

Shalid 

Customers Also Viewed These Support Documents