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
1377
Views
13
Helpful
17
Replies

SIP outgoing calls are not working

Go to solution
Bothra Group
Level 1
Level 1

‎08-05-2024 11:18 PM

Hi,

Outgoing calls are dropping as soon as answer the call. External incoming calls and internal numbers  are working fine.

below is my debug ccsip messages output.

 


BOTHRA_KOLKATA#debug ccsip messages
SIP Call messages tracing is enabled
BOTHRA_KOLKATA#term mon
BOTHRA_KOLKATA#
Aug 6 05:42:00.219: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:08978180483@172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
Supported: 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, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.17.27.59:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
Session-Expires: 1800
P-Asserted-Identity: "PIYALI Madam" <sip:+913349506906@172.17.27.59>
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;party=calling;screen=yes;privacy=off
Contact: <sip:+913349506906@172.17.27.59:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP3891B747EFEB"
Max-Forwards: 69
Content-Length: 0


Aug 6 05:42:00.224: //18307/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: 00000000000000000000000000000000;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


Aug 6 05:42:00.228: //18308/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08978180483@172.17.27.59:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@172.17.27.89>;party=calling;screen=yes;privacy=off
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1722922920
Contact: <sip:+913349506906@172.17.27.89:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Session-Expires: 1800
Content-Length: 0


Aug 6 05:42:00.229: //18308/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


Aug 6 05:42:00.237: //18308/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>;tag=148155~c961babc-d78c-40c7-9169-6d3071fa2c18-27156443
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
CSeq: 101 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Server: Cisco-CUCM14.0
Session-ID: 00000000000000000000000000000000;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


Aug 6 05:42:00.247: //18308/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:08978180483@172.17.27.59:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>;tag=148155~c961babc-d78c-40c7-9169-6d3071fa2c18-27156443
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Content-Length: 0


Aug 6 05:42:00.247: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08978180483@ims.airtel.in:5060 SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@10.239.164.110>;party=calling;screen=yes;privacy=off
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1722922920
Contact: <sip:+913349506906@10.239.164.110:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 324

v=0
o=CiscoSystemsSIP-GW-UserAgent 9152 5547 IN IP4 10.239.164.110
s=SIP Call
c=IN IP4 10.239.164.110
t=0 0
m=audio 8144 RTP/AVP 0 8 18 101
c=IN IP4 10.239.164.110
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Aug 6 05:42:00.252: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>
CSeq: 101 INVITE
Content-Length: 0


Aug 6 05:42:00.749: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:+913349506906@ims.airtel.in SIP/2.0
Via: SIP/2.0/UDP 10.232.135.130:5060;branch=z9hG4bKpwyzulgulqgglqmpvqzzp0woz;Role=3;Hpt=8fb2_36;X-HwDim=4
Call-ID: asbc87pqkl188b1pkgg7cgg6ble8dfcakgp8@10.232.207.226
From: <sip:+913349506906@ims.airtel.in>;tag=gpclpfaa
To: <sip:+913349506906@ims.airtel.in>
CSeq: 1 NOTIFY
Contact: <sip:10.232.135.130:5060;Dsp=eb4a-200;Hpt=8fb2_16;CxtId=4;TRC=ffffffff-ffffffff>
Max-Forwards: 67
Supported: 100rel
Event: ua-profile
Subscription-State: active
P-Asserted-Identity: <sip:+913349506906@ims.airtel.in>
P-Charging-Vector: icid-value=ATS9900-202408061112000143546;term-ioi=SIP_12105716_BOTHRA_3349506959
Content-Length: 158
Content-Type: application/simservs+xml

<?xml version="1.0"?>
<simservs>
<dial-tone-management>
<dial-tone-pattern>standard-dial-tone</dial-tone-pattern>
</dial-tone-management>
</simservs>

Aug 6 05:42:04.988: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff>
P-Charging-Vector: icid-value="bcf2.22.ea5c3628.29116878";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.242
P-Early-Media: sendrecv,gated
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 235340243 235340243 IN IP4 10.232.135.133
s=SBC call
c=IN IP4 10.232.135.133
t=0 0
m=audio 19102 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

Aug 6 05:42:04.992: //18307/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


Aug 6 05:42:06.808: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:+913349506906@ims.airtel.in SIP/2.0
Via: SIP/2.0/UDP 10.232.135.130:5060;branch=z9hG4bKw5yww095gymmzg9w9o5gxmlxy;Role=3;Hpt=8fb2_36;X-HwDim=4
Call-ID: asbc87pqkl188b1pkgg7cgg6ble8dfcakgp8@10.232.207.226
From: <sip:+913349506906@ims.airtel.in>;tag=gpclpfaa
To: <sip:+913349506906@ims.airtel.in>
CSeq: 2 NOTIFY
Contact: <sip:10.232.135.130:5060;Dsp=eb4a-200;Hpt=8fb2_16;CxtId=4;TRC=ffffffff-ffffffff>
Max-Forwards: 66
Supported: 100rel
Event: ua-profile
Subscription-State: active
P-Asserted-Identity: <sip:+913349506906@ims.airtel.in>
P-Charging-Vector: icid-value=ATS9900-202408061112000143546;term-ioi=SIP_12105716_BOTHRA_3349506959
Content-Length: 158
Content-Type: application/simservs+xml

<?xml version="1.0"?>
<simservs>
<dial-tone-management>
<dial-tone-pattern>standard-dial-tone</dial-tone-pattern>
</dial-tone-management>
</simservs>

Aug 6 05:42:07.984: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff>
Require: timer
Session-Expires: 1800;refresher=uac
P-Charging-Vector: icid-value="bcf2.22.ea5c3628.29116878";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.242
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 235340243 235340243 IN IP4 10.232.135.133
s=SBC call
c=IN IP4 10.232.135.133
t=0 0
m=audio 19102 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

Aug 6 05:42:07.988: //18307/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Supported: replaces
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Session-Expires: 1800;refresher=uac
Require: timer
Supported: timer
Content-Length: 0


Aug 6 05:42:07.989: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AE89B
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 7d35397e00105000a0003891b747efeb;remote=e9475dc359e252eabed205359dcaf382
Content-Length: 0


Aug 6 05:42:07.990: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e91db941f3
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Session-ID: 7d35397e00105000a0003891b747efeb;remote=e9475dc359e252eabed205359dcaf382
Content-Length: 0


Aug 6 05:42:07.992: //18307/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:+913349506906@172.17.27.59:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK23AFE56
From: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
To: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
Date: Tue, 06 Aug 2024 05:42:07 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Max-Forwards: 70
Timestamp: 1722922927
CSeq: 101 BYE
Reason: Q.850;cause=86
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


Aug 6 05:42:07.993: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88ea1701970a
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
P-Asserted-Identity: "PIYALI Madam" <sip:+913349506906@172.17.27.59>
CSeq: 102 BYE
Reason: Q.850;cause=65
Content-Length: 0


Aug 6 05:42:07.996: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23B02380
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Max-Forwards: 70
Timestamp: 1722922927
CSeq: 102 BYE
Reason: Q.850;cause=96
Session-ID: 7d35397e00105000a0003891b747efeb;remote=e9475dc359e252eabed205359dcaf382
Content-Length: 0


Aug 6 05:42:07.997: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88ea1701970a
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:07 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
Server: Cisco-SIPGateway/IOS-17.6.1a
CSeq: 102 BYE
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


Aug 6 05:42:07.998: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK23AFE56
From: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
To: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
Date: Tue, 06 Aug 2024 05:42:07 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
Server: Cisco-CUCM14.0
CSeq: 101 BYE
Content-Length: 0


Aug 6 05:42:08.081: //18309/988189800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23B02380
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
CSeq: 102 BYE
P-Charging-Vector: icid-value="bcf2.22.ea5c3628.29116878";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.242
Content-Length: 0


6194: Aug 6 05:42:08.348: //18307/988189800000/
------------------ Cover Buffer ---------------
Search-key = +913349506906:08978180483:18307
Timestamp = Aug 6 05:42:00.219
CallID = 18307
Peer-CallID = 18309
Correlator = NA
Called-Number = 08978180483
Calling-Number = +913349506906
SIP CallID = 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
SIP SessionID = e9475dc359e252eabed205359dcaf382
GUID = 988189800000
-----------------------------------------------
6020: Aug 6 05:42:00.218: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:34158 to 172.17.27.89:5060
INVITE sip:08978180483@172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
Supported: 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, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.17.27.59:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
Session-Expires: 1800
P-Asserted-Identity: "PIYALI Madam" <sip:+913349506906@172.17.27.59>
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;party=calling;screen=yes;privacy=off
Contact: <sip:+913349506906@172.17.27.59:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP3891B747EFEB"
Max-Forwards: 69
Content-Length: 0


6023: Aug 6 05:42:00.219: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_NONE, Next State = STATE_IDLE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6024: Aug 6 05:42:00.221: //18307/988189800000/CUBE_VT/SIP/MISC/Matched Dialpeer: Dir:Inbound, Peer-Tag: 9
6025: Aug 6 05:42:00.221: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_sig_ip_address_to_bind: Dialpeer bind configured, interface addr failure
6026: Aug 6 05:42:00.221: //18307/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6027: Aug 6 05:42:00.222: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
6028: Aug 6 05:42:00.222: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
6029: Aug 6 05:42:00.222: //18307/988189800000/CUBE_VT/SIP/API: cc_api_call_setup_ind_with_callID (0)
6030: Aug 6 05:42:00.221: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_RECD_INVITE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6031: Aug 6 05:42:00.223: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:34158
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: 00000000000000000000000000000000;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


6038: Aug 6 05:42:00.226: //18307/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_SET_MODE, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6039: Aug 6 05:42:00.226: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_PROCEEDING, Current State = STATE_RECD_INVITE
6067: Aug 6 05:42:00.239: //18307/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_SET_MODE, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6101: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_CAPS, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6102: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/API: cc_api_caps_ack (0)
6103: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/API: cc_api_caps_ack (0)
6109: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_MULTIMEDIA_CHANNEL_IND, Current State = S_SIP_IWF_SDP_IDLE, Next State = CNFSM_NO_STATE_CHANGE
6110: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
6111: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
6112: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
6113: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
6114: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/MISC/Media Stream Parameters: Stream Type = voice-only, Stream State = STREAM_ADDING Negotiated Codec = No Codec , Negotiated DTMF Type = inband-voice, Stream Index = 1
6115: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
6116: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Idb not found for GigabitEthernet0/0/0 interface
6117: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
6118: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/FSM/Media-State: Event = E_IPIP_MEDIA_SERV_EV_PEER_CHNL_IND, Current State = S_IPIP_MEDIA_SERV_STATE_IDLE, Next State = S_IPIP_MEDIA_SERV_STATE_INIT_XCODER_RESERVED
6119: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Software-Error: Type: Error in Transcoder Reservation, Code-location:0x36005A2
6120: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/API: ccsip_xcoder_reserve (-1)
6121: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_sig_ip_address_to_bind: Dialpeer bind configured, interface addr failure
6122: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
6123: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
6124: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/API: voip_rtp_allocate_port (0)
6125: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/API: cc_api_bridge_done (0)
6126: Aug 6 05:42:04.988: //18307/988189800000/CUBE_VT/SIP/API: ccsip_bridge (0)
6132: Aug 6 05:42:04.989: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_PROGRESS, Current State = STATE_RECD_INVITE
6133: Aug 6 05:42:04.990: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:34158
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


6145: Aug 6 05:42:07.985: //18307/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_CALL_CONNECT, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6146: Aug 6 05:42:07.986: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_CONNECT, Current State = STATE_RECD_INVITE
6147: Aug 6 05:42:07.986: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_RECD_INVITE, Next State = STATE_SENT_SUCCESS, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6148: Aug 6 05:42:07.986: //18307/988189800000/CUBE_VT/SIP/API: voip_rtp_allocate_port (0)
6149: Aug 6 05:42:07.987: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:34158
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e8442d4904
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Supported: replaces
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Session-Expires: 1800;refresher=uac
Require: timer
Supported: timer
Content-Length: 0


6153: Aug 6 05:42:07.990: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:34158 to 172.17.27.89:5060
ACK sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88e91db941f3
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Session-ID: 7d35397e00105000a0003891b747efeb;remote=e9475dc359e252eabed205359dcaf382
Content-Length: 0


6155: Aug 6 05:42:07.990: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_SENT_SUCCESS
6156: Aug 6 05:42:07.990: //18307/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x17037C5, Originated at:0x41044CF, Cause Code = 96
6157: Aug 6 05:42:07.989: //18307/988189800000/CUBE_VT/SIP/API: cc_api_call_disconnected (0)
6158: Aug 6 05:42:07.989: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_SENT_SUCCESS, Next State = STATE_DISCONNECTING, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6159: Aug 6 05:42:07.989: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_DISCONNECTING, Next State = STATE_DISCONNECTING, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6160: Aug 6 05:42:07.990: //18307/988189800000/CUBE_VT/SIP/FSM/Media-State: Event = E_IPIP_MEDIA_SERV_EV_XCODER_RESET_STREAM, Current State = CNFSM_CONTAINER_STATE, Next State = S_IPIP_MEDIA_SERV_STATE_IDLE
6161: Aug 6 05:42:07.991: //18307/988189800000/CUBE_VT/SIP/API: cc_api_bridge_drop_done (0)
6165: Aug 6 05:42:07.992: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:5060
BYE sip:+913349506906@172.17.27.59:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK23AFE56
From: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
To: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
Date: Tue, 06 Aug 2024 05:42:07 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Max-Forwards: 70
Timestamp: 1722922927
CSeq: 101 BYE
Reason: Q.850;cause=86
Session-ID: e9475dc359e252eabed205359dcaf382;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


6167: Aug 6 05:42:07.992: //18307/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x260070A, Originated at:0x260070B, Cause Code = 96
6169: Aug 6 05:42:07.993: //18307/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:34158 to 172.17.27.89:5060
BYE sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK88ea1701970a
From: "PIYALI Madam" <sip:+913349506906@172.17.27.59>;tag=148154~c961babc-d78c-40c7-9169-6d3071fa2c18-27156442
To: <sip:08978180483@172.17.27.89>;tag=226D6C86-1616
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 98818980-1f0171b9-843d-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
P-Asserted-Identity: "PIYALI Madam" <sip:+913349506906@172.17.27.59>
CSeq: 102 BYE
Reason: Q.850;cause=65
Content-Length: 0


6171: Aug 6 05:42:07.993: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_DISCONNECTING
6172: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6173: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_DISCONNECT, Current State = STATE_DISCONNECTING
6174: Aug 6 05:42:07.993: //18307/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x1702FDC, Originated at:0x41044CF, Cause Code = 86
6175: Aug 6 05:42:07.993: //18307/988189800000/CUBE_VT/SIP/API: voip_rtp_release_port (0)
6176: Aug 6 05:42:07.993: //18307/988189800000/CUBE_VT/SIP/API: cc_api_call_disconnect_done (0)
6177: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_DISCONNECTING, Next State = STATE_DEAD, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6178: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/MISC/Error: sipSPIFlushDeferredQueue: Invalid deferredQueue
6179: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/MISC/Error: ws_call_fork_cleanup: ws_info is NULL
6180: Aug 6 05:42:07.994: //18307/988189800000/CUBE_VT/SIP/API: voip_rtp_release_port (0)
6195: Aug 6 05:42:08.354: //18309/988189800000/
------------------ Cover Buffer ---------------
Search-key = +913349506906:08978180483:18309
Timestamp = Aug 6 05:42:00.238
CallID = 18309
Peer-CallID = 18307
Correlator = NA
Called-Number = 08978180483
Calling-Number = +913349506906
SIP CallID = 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
SIP SessionID = 7d35397e00105000a0003891b747efeb
GUID = 988189800000
-----------------------------------------------
6062: Aug 6 05:42:00.238: //18309/988189800000/CUBE_VT/SIP/MISC/Matched Dialpeer: Dir:Outbound, Peer-Tag: 101
6063: Aug 6 05:42:00.238: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_NONE, Next State = STATE_IDLE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6064: Aug 6 05:42:00.237: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_SET_MODE, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6065: Aug 6 05:42:00.237: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_DO, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6066: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PRE_SETUP, Current State = S_SIP_IWF_SDP_IDLE, Next State = CNFSM_NO_STATE_CHANGE
6068: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_INIT_CALL_SETUP, Current State = S_SIP_IWF_SDP_IDLE, Next State = CNFSM_NO_STATE_CHANGE
6069: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6070: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_SETUP, Current State = STATE_IDLE
6071: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_IDLE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_IDLE
6072: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_IDLE, Current Sub-State = STATE_IDLE, Next Sub-State = STATE_IDLE
6073: Aug 6 05:42:00.239: //18309/988189800000/CUBE_VT/SIP/API: cc_api_call_proceeding (0)
6074: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_DNS_RESOLVED, Current State = STATE_IDLE
6075: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_IDLE, Current Sub-State = STATE_IDLE, Next Sub-State = STATE_NONE
6076: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_allocate_port (8144)
6077: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/FSM/Offer-Answer: Event = E_SIP_INVITE_SDP_SENT, Current State = S_SIP_EARLY_DIALOG_IDLE, Next State = S_SIP_EARLY_DIALOG_OFFER_SENT
6078: Aug 6 05:42:00.244: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_SENT_SDP, Current State = S_SIP_IWF_SDP_IDLE, Next State = S_SIP_IWF_SDP_SENT_AWAIT_SDP
6079: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_SENT_INVITE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6080: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_create_session (0)
6081: Aug 6 05:42:00.245: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_set_non_rtp_call (0)
6082: Aug 6 05:42:00.246: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
6085: Aug 6 05:42:00.247: //18309/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 10.239.164.110:5060 to 10.232.135.130:5060
INVITE sip:08978180483@ims.airtel.in:5060 SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@10.239.164.110>;party=calling;screen=yes;privacy=off
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1722922920
Contact: <sip:+913349506906@10.239.164.110:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 324

v=0
o=CiscoSystemsSIP-GW-UserAgent 9152 5547 IN IP4 10.239.164.110
s=SIP Call
c=IN IP4 10.239.164.110
t=0 0
m=audio 8144 RTP/AVP 0 8 18 101
c=IN IP4 10.239.164.110
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

6088: Aug 6 05:42:00.253: //18309/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>
CSeq: 101 INVITE
Content-Length: 0


6089: Aug 6 05:42:00.253: //18309/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_SENT_INVITE
6090: Aug 6 05:42:00.253: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_SENT_INVITE, Next State = STATE_RECD_PROCEEDING, Current Sub-State = STATE_NONE, Next Sub-State = STATE_SETUP_BUFFERED
6091: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff>
P-Charging-Vector: icid-value="bcf2.22.ea5c3628.29116878";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.242
P-Early-Media: sendrecv,gated
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 235340243 235340243 IN IP4 10.232.135.133
s=SBC call
c=IN IP4 10.232.135.133
t=0 0
m=audio 19102 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

6093: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_RECD_PROCEEDING
6094: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/FSM/Offer-Answer: Event = E_SIP_INVITE_RESP_SDP_RCVD, Current State = S_SIP_EARLY_DIALOG_OFFER_SENT, Next State = S_SIP_EARLY_DIALOG_OFFER_ANSWER_COMPLETE
6095: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_RCVD_SDP, Current State = S_SIP_IWF_SDP_SENT_AWAIT_SDP, Next State = S_SIP_IWF_SDP_DONE
6096: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/MISC/Error: sipSPI_ipip_upd_2833_dtmf_params: Unable to find proper instance for FMTP
6097: Aug 6 05:42:04.987: //18309/988189800000/CUBE_VT/SIP/MISC/Error: sipSPI_ipip_upd_2833_dtmf_params: Unable to acquire event mask for rfc2833
6098: Aug 6 05:42:04.988: //18309/988189800000/CUBE_VT/SIP/MISC/Media Stream Parameters: Stream Type = voice+dtmf, Stream State = STREAM_ADDING Negotiated Codec = g711ulaw, Negotiated DTMF Type = rtp-nte, Stream Index = 1
6099: Aug 6 05:42:04.988: //18309/988189800000/CUBE_VT/SIP/API: cc_api_call_mode_update_ind (0)
6100: Aug 6 05:42:04.988: //18309/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6104: Aug 6 05:42:04.988: //18309/988189800000/CUBE_VT/SIP/API: cc_api_caps_ind (0)
6105: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/API: cc_api_call_alert (0)
6106: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_RECD_PROCEEDING, Next State = STATE_RECD_PROCEEDING, Current Sub-State = STATE_SETUP_BUFFERED, Next Sub-State = STATE_SETUP_BUFFERED
6107: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_CAPS_ACK,, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6108: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_CAPS_ACK,, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6127: Aug 6 05:42:04.990: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
6128: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_set_non_rtp_call (0)
6129: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
6130: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/API: cc_api_bridge_done (0)
6131: Aug 6 05:42:04.989: //18309/988189800000/CUBE_VT/SIP/API: ccsip_bridge (0)
6135: Aug 6 05:42:07.983: //18309/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK23AD2420
Call-ID: 6F743B64-52ED11EF-874F993F-BF708816@10.239.164.110
From: "PIYALI Madam"<sip:+913349506906@ims.airtel.in>;tag=226D59FD-269C
To: <sip:08978180483@ims.airtel.in>;tag=7ad86cbb
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7758-400;Hpt=8fb2_16;CxtId=3;TRC=ffffffff-ffffffff>
Require: timer
Session-Expires: 1800;refresher=uac
P-Charging-Vector: icid-value="bcf2.22.ea5c3628.29116878";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.242
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 235340243 235340243 IN IP4 10.232.135.133
s=SBC call
c=IN IP4 10.232.135.133
t=0 0
m=audio 19102 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

6137: Aug 6 05:42:07.984: //18309/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_RECD_PROCEEDING
6138: Aug 6 05:42:07.984: //18309/988189800000/CUBE_VT/SIP/FSM/Offer-Answer: Event = E_SIP_INVITE_RESP_SDP_RCVD, Current State = S_SIP_EARLY_DIALOG_OFFER_ANSWER_COMPLETE, Next State = CNFSM_NO_STATE_CHANGE
6139: Aug 6 05:42:07.984: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_RECD_PROCEEDING, Next State = STATE_RECD_PROCEEDING, Current Sub-State = STATE_SETUP_BUFFERED, Next Sub-State = STATE_NONE
6140: Aug 6 05:42:07.984: //18309/988189800000/CUBE_VT/SIP/API: cc_api_call_connected (0)
6141: Aug 6 05:42:07.984: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_RECD_PROCEEDING, Next State = SIP_STATE_RECD_SUCCESS, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6142: Aug 6 05:42:07.985: //18309/988189800000/CUBE_VT/SIP/FSM/Offer-Answer: Event = E_SIP_DIALOG_ESTD, Current State = S_SIP_EARLY_DIALOG_OFFER_ANSWER_COMPLETE, Next State = S_SIP_MID_DIALOG_IDLE
6143: Aug 6 05:42:07.985: //18309/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_CALL_ACTIVE, Current State = S_SIP_IWF_SDP_DONE, Next State = CNFSM_NO_STATE_CHANGE
6144: Aug 6 05:42:07.985: //18309/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = SIP_STATE_RECD_SUCCESS, Next State = STATE_ACTIVE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6192: Aug 6 05:42:08.082: //18309/988189800000/CUBE_VT/SIP/MISC/Error: ws_call_fork_cleanup: ws_info is NULL
6193: Aug 6 05:42:08.082: //18309/988189800000/CUBE_VT/SIP/API: voip_rtp_release_port (8144)
BOTHRA_KOLKATA#
BOTHRA_KOLKATA#
BOTHRA_KOLKATA#u all
All possible debugging has been turned off
BOTHRA_KOLKATA#
6199: Aug 6 05:42:32.354: //18308/988189800000/
------------------ Cover Buffer ---------------
Search-key = +913349506906:08978180483:18308
Timestamp = Aug 6 05:42:00.226
CallID = 18308
Peer-CallID = 18307
Correlator = NA
Called-Number = 08978180483
Calling-Number = +913349506906
SIP CallID = 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
SIP SessionID =
GUID = 988189800000
-----------------------------------------------
6033: Aug 6 05:42:00.225: //18308/988189800000/CUBE_VT/SIP/MISC/Matched Dialpeer: Dir:Outbound, Peer-Tag: 100
6034: Aug 6 05:42:00.226: //18308/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_NONE, Next State = STATE_IDLE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6035: Aug 6 05:42:00.226: //18308/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_SET_MODE, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6036: Aug 6 05:42:00.226: //18308/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PEER_DO, Current State = CNFSM_CONTAINER_STATE, Next State = CNFSM_NO_STATE_CHANGE
6037: Aug 6 05:42:00.226: //18308/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_PRE_SETUP, Current State = S_SIP_IWF_SDP_IDLE, Next State = CNFSM_NO_STATE_CHANGE
6040: Aug 6 05:42:00.226: //18308/988189800000/CUBE_VT/SIP/FSM/IWF: Event = E_SIP_IWF_EV_INIT_CALL_SETUP, Current State = S_SIP_IWF_SDP_IDLE, Next State = CNFSM_NO_STATE_CHANGE
6041: Aug 6 05:42:00.225: //18308/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6042: Aug 6 05:42:00.225: //18308/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_SETUP, Current State = STATE_IDLE
6043: Aug 6 05:42:00.227: //18308/988189800000/CUBE_VT/SIP/API: cc_api_call_proceeding (0)
6044: Aug 6 05:42:00.227: //18308/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_IDLE, Next State = STATE_SENT_INVITE, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6045: Aug 6 05:42:00.228: //18308/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 172.17.27.89:5060 to 172.17.27.59:5060
INVITE sip:08978180483@172.17.27.59:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
Remote-Party-ID: "PIYALI Madam" <sip:+913349506906@172.17.27.89>;party=calling;screen=yes;privacy=off
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2558626176-0000065536-0000000189-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1722922920
Contact: <sip:+913349506906@172.17.27.89:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Session-Expires: 1800
Content-Length: 0


6047: Aug 6 05:42:00.229: //18308/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 172.17.27.59:5060 to 172.17.27.89:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


6048: Aug 6 05:42:00.230: //18308/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_SENT_INVITE
6049: Aug 6 05:42:00.230: //18308/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_SENT_INVITE, Next State = STATE_RECD_PROCEEDING, Current Sub-State = STATE_NONE, Next Sub-State = STATE_SETUP_BUFFERED
6050: Aug 6 05:42:00.237: //18308/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 172.17.27.59:5060 to 172.17.27.89:5060
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>;tag=148155~c961babc-d78c-40c7-9169-6d3071fa2c18-27156443
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
CSeq: 101 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Server: Cisco-CUCM14.0
Session-ID: 00000000000000000000000000000000;remote=7d35397e00105000a0003891b747efeb
Content-Length: 0


6052: Aug 6 05:42:00.237: //18308/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_NEW_MESSAGE, Current State = STATE_RECD_PROCEEDING
6053: Aug 6 05:42:00.236: //18308/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x1701CCC, Originated at:0x5A07E89, Cause Code = 1
6054: Aug 6 05:42:00.236: //18308/988189800000/CUBE_VT/SIP/API: cc_api_call_disconnected (0)
6055: Aug 6 05:42:00.237: //18308/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_RECD_PROCEEDING, Next State = STATE_DISCONNECTING, Current Sub-State = STATE_SETUP_BUFFERED, Next Sub-State = STATE_NONE
6056: Aug 6 05:42:00.238: //18308/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x260070A, Originated at:0x260070B, Cause Code = 1
6057: Aug 6 05:42:00.238: //18308/988189800000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
6058: Aug 6 05:42:00.238: //18308/988189800000/CUBE_VT/SIP/FSM/Event-Action: Event = SIPSPI_EV_CC_CALL_DISCONNECT, Current State = STATE_DISCONNECTING
6059: Aug 6 05:42:00.238: //18308/988189800000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x1702FDC, Originated at:0x5A07E89, Cause Code = 1
6060: Aug 6 05:42:00.238: //18308/988189800000/CUBE_VT/SIP/API: cc_api_call_disconnect_done (0)
6061: Aug 6 05:42:00.237: //18308/988189800000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State = STATE_DISCONNECTING, Next State = STATE_DEAD, Current Sub-State = STATE_NONE, Next Sub-State = STATE_NONE
6083: Aug 6 05:42:00.247: //18308/988189800000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 172.17.27.89:5060 to 172.17.27.59:5060
ACK sip:08978180483@172.17.27.59:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.27.89:5060;branch=z9hG4bK23AC221E
From: "PIYALI Madam" <sip:+913349506906@ims.airtel.in>;tag=226D59EA-1460
To: <sip:08978180483@172.17.27.59>;tag=148155~c961babc-d78c-40c7-9169-6d3071fa2c18-27156443
Date: Tue, 06 Aug 2024 05:42:00 GMT
Call-ID: 6F723F96-52ED11EF-874D993F-BF708816@172.17.27.89
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 7d35397e00105000a0003891b747efeb;remote=00000000000000000000000000000000
Content-Length: 0


6196: Aug 6 05:42:32.239: //18308/988189800000/CUBE_VT/SIP/FSM/Timer-Action: Event = SIP_TIMER_REMOVE_TRANSACTION, Current State = STATE_DEAD
6197: Aug 6 05:42:32.239: //18308/988189800000/CUBE_VT/SIP/MISC/Error: sipSPIFlushDeferredQueue: Invalid deferredQueue
6198: Aug 6 05:42:32.238: //18308/988189800000/CUBE_VT/SIP/MISC/Error: ws_call_fork_cleanup: ws_info is NULL
BOTHRA_KOLKATA#

0 Helpful
2 Accepted Solutions

Accepted Solutions

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 04:28 AM - edited ‎08-27-2024 08:44 AM

Do these changes on your dial peers and try again with all the suggested debugs running at the same time.

 

dial-peer voice 210 voip
 no translation-profile incoming ITSP_CUCM !Not needed on outbound dial peer
 no incoming uri via CUCM !Not needed on outbound dial peer
 voice-class sip bind control source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 voice-class sip bind media source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
!
voice class uri PSTN sip !Create a class uri to be used for inbound dial peer match from PSTN/ITSP
 host ipv4:<IP address as seen in VIA header for inbound calls from PSTN>
!
dial-peer voice 211 voip
 no incoming called-number +913349506... ! Remove match for called number to use the below match instead
 incoming uri via PSTN !Use info in VIA header to match inbound calls from PSTN/ITSP
!
dial-peer voice 212 voip
 translation-profile incoming ITSP_CUCM !Moved from DP 210 as it looks to be used by the inbound dial peer for calls comming from CM
 no incoming called-number . !Not needed on inbound dial peer as you use VIA header info with command incoming uri via CUCM
 voice-class sip bind control source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 voice-class sip bind media source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 no voice-class sip options-keepalive up-interval 30 down-interval 10 retry 2 !Not needed on inbound dial peer

 

Collect the debug output if there is still problem and post it in one file please.

Edit: I added a few things to the suggested changes as I missed the inbound translation used on DP 210. It is now removed from that DP and added to DP 212 as that with my suggested changes should be the only viable inbound DP matched for calls coming from CM.



Response Signature


View solution in original post

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-29-2024 04:00 AM - edited ‎08-30-2024 07:20 AM

From what I can tell you're sending the call back to the service provider instead of sending it to CM. This is what the debugs shows.

image.pngimage.pngimage.pngimage.pngimage.png
As you can see the calls is matched inbound on dial peer 211 and this is based on your configuration what you expect it to do, but then instead of matching dial peer 210 to send the call to CM it matches dial peer 213 that sends the call back to your service provider. This happens since you translate the called number on ingress from the SP to the last three digits, then it doesn't match DP 210 as that is matching in +E.164 format, it will instead match DP 213 that has destination-pattern .T as that matches basically anything.

Using this type of broad match is a quite bad and dangerous thing to do as it opens up for call loops or at least hair-pinning as in your case here. I would suggest that you change the destination pattern on DP 213 to something that only matches outbound calls, what that would be depends on how you make outbound calls. For example it might be destination-pattern 0T if you use a zero (0) to make outbound calls.

Since you route to CM in +E.164 format on DP 210 and the SP is sending the called number to you in +E.164 format you don't need to do any translation of the called number, that is if you have the directory numbers in CM in +E.164 format. If you don't and have it in for example last three digit format you'd need to do a translation, but that is better done on egress when the call leaves the outbound dial peer towards CM. To do that you should do these changes.

 

voice translation-rule 210
 rule 1 /^\+913349506\(...\)$/ /\1/
!
voice translation-profile TO_CUCM_OUT
 translate called 210
!
dial-peer voice 210 voip
 translation-profile outgoing TO_CUCM_OUT

 

 

To be clear the above is only needed if you do not have the directory numbers in CM in +E.164 format.

To clean up your configuration and have it as what I've previously suggested please do these changes.

 

service timestamps log datetime msec
service password-encryption
service sequence-numbers
!
voice service voip
 mode border-element
  no allow-connections h323 to h323
  no allow-connections h323 to sip
  no allow-connections sip to h323
!
voice class uri PSTN sip
 host ipv4:10.232.135.130
!
no voice translation-rule 18
no voice translation-rule 100
no voice translation-rule 110
no voice translation-rule 150
!
no voice translation-profile E164_FORMAT
no voice translation-profile ITSP_CUCM
!
dial-peer voice 210 voip
 no translation-profile incoming ITSP_CUCM
 no incoming uri via CUCM
!
dial-peer voice 211 voip
 no translation-profile incoming ITSP_CUCM
 no incoming called-number .%
 incoming uri via PSTN
!
no ntp server 10.232.135.130
no ntp server 172.17.27.59

 

 

This will remove the translation that you currently have on ingress from the SP so that DP 210 is matched on egress and sends the call to CM, it will as well remove some incorrect and/or unneeded configuration that I urge you do please follow as suggested.



Response Signature


View solution in original post

17 Replies 17

Go to solution
Bothra Group
Level 1
Level 1

‎08-23-2024 04:42 AM

Dear Team,

SIP outgoing calls disconnect after the call is answered.


BOTHRA_KOLKATA#debug ccsip messages
SIP Call messages tracing is enabled
BOTHRA_KOLKATA#sh log
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

 

No Inactive Message Discriminator.


Console logging: level debugging, 24250 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 24250 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 274 message lines logged
Logging Source-Interface: VRF Name:
TLS Profiles:

Log Buffer (102400 bytes):

Aug 23 10:34:43.112: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a012e0558e9
From: <sip:172.17.27.59>;tag=605557132
To: <sip:172.17.27.89>
Date: Fri, 23 Aug 2024 10:34:43 GMT
Call-ID: 4de46900-1f017f3e-ff15-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.17.27.59:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Aug 23 10:34:43.114: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a012e0558e9
From: <sip:172.17.27.59>;tag=605557132

To: <sip:172.17.27.89>;tag=ED9F5FA-7C
Date: Fri, 23 Aug 2024 10:34:43 GMT
Call-ID: 4de46900-1f017f3e-ff15-3b1b11ac@172.17.27.59
Server: Cisco-SIPGateway/IOS-17.9.5a
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Accept: application/sdp
Supported: timer,resource-priority,replaces
Content-Length: 0


Aug 23 10:34:59.753: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:08978180483@172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59

Supported: 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, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.17.27.59:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 0000617f00105000a0002800afb78bd9;remote=00000000000000000000000000000000
Cisco-Guid: 1466814720-0000065536-0000000478-0991629740
Session-Expires: 18000
P-Asserted-Identity: <sip:+913349506956@172.17.27.59>
Privacy: none
Remote-Party-ID: <sip:+913349506956@172.17.27.59>;party=calling;screen=yes;privacy=off
Contact: <sip:+913349506956@172.17.27.59:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="CSFhari";bfcp

Max-Forwards: 69
Content-Length: 0


Aug 23 10:34:59.764: //19524/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow-Events: kpml, telephone-event
Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: 00000000000000000000000000000000;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


Aug 23 10:34:59.912: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08978180483@ims.airtel.in:5060 SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Remote-Party-ID: <sip:+913349506956@10.239.164.110>;party=calling;screen=yes;privacy=off
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
Supported: timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1466814720-0000065536-0000000478-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1724409299
Contact: <sip:+913349506956@10.239.164.110:5060>
Call-Info: <sip:10.239.164.110:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 60
Allow-Events: kpml, telephone-event
Max-Forwards: 68

Session-ID: 0000617f00105000a0002800afb78bd9;remote=00000000000000000000000000000000
Session-Expires: 18000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 252

v=0
o=CiscoSystemsSIP-GW-UserAgent 7162 8197 IN IP4 10.239.164.110
s=SIP Call
c=IN IP4 10.239.164.110
t=0 0
m=audio 8170 RTP/AVP 0 101
c=IN IP4 10.239.164.110
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Aug 23 10:34:59.917: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>
CSeq: 101 INVITE
Content-Length: 0


Aug 23 10:35:04.221: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff>
P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
P-Early-Media: sendrecv,gated

Content-Length: 194
Content-Type: application/sdp

v=0
o=- 233480777 233480777 IN IP4 10.232.135.132
s=SBC call
c=IN IP4 10.232.135.132
t=0 0
m=audio 57466 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

Aug 23 10:35:04.223: //19524/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59

CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Call-Info: <sip:172.17.27.89:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


Aug 23 10:35:08.193: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l

CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff>
Require: timer
Session-Expires: 1800;refresher=uac
P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 233480777 233480777 IN IP4 10.232.135.132
s=SBC call
c=IN IP4 10.232.135.132
t=0 0
m=audio 57466 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

Aug 23 10:35:08.196: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188320D6
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: kpml, telephone-event
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


Aug 23 10:35:08.199: //19524/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC

Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Supported: replaces
Call-Info: <sip:172.17.27.89:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Session-Expires: 1800;refresher=uac
Require: timer
Supported: timer
Content-Length: 0


Aug 23 10:35:08.201: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a056b1c5fc1
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


Aug 23 10:35:08.204: //19524/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:+913349506956@172.17.27.59:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK1884712
From: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC

To: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
Date: Fri, 23 Aug 2024 10:35:08 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Max-Forwards: 70
Timestamp: 1724409308
CSeq: 101 BYE
Reason: Q.850;cause=86
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


Aug 23 10:35:08.206: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK18851FB0
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
Date: Fri, 23 Aug 2024 10:34:59 GMT

Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Max-Forwards: 70
Timestamp: 1724409308
CSeq: 102 BYE
Reason: Q.850;cause=96
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


Aug 23 10:35:08.207: //19524/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK1884712
From: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
To: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
Date: Fri, 23 Aug 2024 10:35:08 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
Server: Cisco-CUCM14.0
CSeq: 101 BYE

Content-Length: 0


Aug 23 10:35:08.335: //19525/576DD1000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK18851FB0
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
CSeq: 102 BYE
P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
Content-Length: 0


Aug 23 10:35:08.402: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a06fe07068
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257

To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
Privacy: none
P-Asserted-Identity: <sip:+913349506956@172.17.27.59>
CSeq: 102 BYE
Reason: Q.850;cause=65
Content-Length: 0


Aug 23 10:35:08.403: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a06fe07068
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 102 BYE
Content-Length: 0

 

14287: Aug 23 10:35:08.510: //19524/576DD1000000/
------------------ Cover Buffer ---------------
Search-key = +913349506956:08978180483:19524
Timestamp = Aug 23 10:34:59.752
CallID = 19524
Peer-CallID = 19525
Correlator = NA
Called-Number = 08978180483
Calling-Number = +913349506956
SIP CallID = 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
SIP SessionID = ec30a7d2290053f8bfaf72ad326615e5
GUID = 576DD1000000
Tenant = 0
-----------------------------------------------
14147: Aug 23 10:34:59.752: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:43836 to 172.17.27.89:5060
INVITE sip:08978180483@172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257

To: <sip:08978180483@172.17.27.89>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
Supported: 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, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.17.27.59:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 0000617f00105000a0002800afb78bd9;remote=00000000000000000000000000000000
Cisco-Guid: 1466814720-0000065536-0000000478-0991629740
Session-Expires: 18000
P-Asserted-Identity: <sip:+913349506956@172.17.27.59>
Privacy: none
Remote-Party-ID: <sip:+913349506956@172.17.27.59>;party=calling;screen=yes;privacy=off

Contact: <sip:+913349506956@172.17.27.59:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="CSFhari";bfcp
Max-Forwards: 69
Content-Length: 0


14150: Aug 23 10:34:59.753: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_NONE, Next State: STATE_IDLE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14151: Aug 23 10:34:59.755: //19524/576DD1000000/CUBE_VT/SIP/MISC/Matched Dialpeer: Dir: Inbound, Peer-Tag: 210
14152: Aug 23 10:34:59.755: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_sig_ip_address_to_bind: Dialpeer bind configured, interface addr failure
14153: Aug 23 10:34:59.755: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
14154: Aug 23 10:34:59.755: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14155: Aug 23 10:34:59.755: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14156: Aug 23 10:34:59.756: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_call_setup_ind_with_callID (0)
14157: Aug 23 10:34:59.756: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_IDLE, Next State: STATE_RECD_INVITE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14163: Aug 23 10:34:59.758: //19524/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_SET_MODE, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14164: Aug 23 10:34:59.757: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_PROCEEDING, Current State: STATE_RECD_INVITE
14171: Aug 23 10:34:59.762: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:43836
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow-Events: kpml, telephone-event
Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: 00000000000000000000000000000000;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


14193: Aug 23 10:35:04.221: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_ALERTING, Current State: STATE_RECD_INVITE
14194: Aug 23 10:35:04.222: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_RECD_INVITE, Next State: STATE_SENT_ALERTING, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14195: Aug 23 10:35:04.222: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:43836
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Call-Info: <sip:172.17.27.89:5060>;method="NOTIFY;Event=telephone-event;Duration=500"

Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


14207: Aug 23 10:35:08.194: //19524/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PEER_CAPS, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14208: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_caps_ack (0)
14209: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_caps_ack (0)
14219: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PEER_MULTIMEDIA_CHANNEL_IND, Current State: S_SIP_IWF_SDP_IDLE, Next State: CNFSM_NO_STATE_CHANGE
14220: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14221: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14222: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14223: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14224: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Media Stream Parameters: Stream Type: voice-only, Stream State: STREAM_ADDING, Negotiated Codec: No Codec , Negotiated DTMF Type: inband-voice, Stream Index: 1
14225: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14226: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14227: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/FSM/Media-State: Event: E_IPIP_MEDIA_SERV_EV_PEER_CHNL_IND, Current State: S_IPIP_MEDIA_SERV_STATE_IDLE, Next State: S_IPIP_MEDIA_SERV_STATE_INIT_XCODER_RESERVED
14228: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/API: ccsip_xcoder_reserve (-1)
14229: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_sig_ip_address_to_bind: Dialpeer bind configured, interface addr failure
14230: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14231: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14232: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/API: voip_rtp_allocate_port (0)
14235: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_bridge_done (0)
14236: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/API: ccsip_bridge (0)
14242: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_CALL_CONNECT, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14243: Aug 23 10:35:08.197: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_CONNECT, Current State: STATE_SENT_ALERTING
14244: Aug 23 10:35:08.198: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_SENT_ALERTING, Next State: STATE_SENT_SUCCESS, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14245: Aug 23 10:35:08.198: //19524/576DD1000000/CUBE_VT/SIP/API: voip_rtp_allocate_port (0)
14246: Aug 23 10:35:08.198: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:43836
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a0460edf888
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
CSeq: 101 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Remote-Party-ID: <sip:08978180483@172.17.27.89>;party=called;screen=no;privacy=off
Contact: <sip:08978180483@172.17.27.89:5060;transport=tcp>
Supported: replaces
Call-Info: <sip:172.17.27.89:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Server: Cisco-SIPGateway/IOS-17.9.5a
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Session-Expires: 1800;refresher=uac
Require: timer
Supported: timer
Content-Length: 0


14248: Aug 23 10:35:08.202: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:43836 to 172.17.27.89:5060
ACK sip:08978180483@172.17.27.89:5060;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK10a056b1c5fc1
From: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
To: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


14250: Aug 23 10:35:08.202: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_SENT_SUCCESS
14251: Aug 23 10:35:08.203: //19524/576DD1000000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x17037E3, Originated at: 0x41044FC, Cause Code: 96
14252: Aug 23 10:35:08.203: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_call_disconnected (0)
14253: Aug 23 10:35:08.203: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_SENT_SUCCESS, Next State: STATE_DISCONNECTING, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14254: Aug 23 10:35:08.203: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_DISCONNECTING, Next State: STATE_DISCONNECTING, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14255: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/FSM/Media-State: Event: E_IPIP_MEDIA_SERV_EV_XCODER_RESET_STREAM, Current State: CNFSM_CONTAINER_STATE, Next State: S_IPIP_MEDIA_SERV_STATE_IDLE
14256: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_bridge_drop_done (0)
14260: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP TCP message from 172.17.27.89:5060 to 172.17.27.59:5060
BYE sip:+913349506956@172.17.27.59:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK1884712
From: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
To: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257
Date: Fri, 23 Aug 2024 10:35:08 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Max-Forwards: 70

Timestamp: 1724409308
CSeq: 101 BYE
Reason: Q.850;cause=86
Session-ID: ec30a7d2290053f8bfaf72ad326615e5;remote=0000617f00105000a0002800afb78bd9
Content-Length: 0


14262: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x260070A, Originated at: 0x260070B, Cause Code: 96
14264: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
14265: Aug 23 10:35:08.204: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_DISCONNECT, Current State: STATE_DISCONNECTING
14271: Aug 23 10:35:08.206: //19524/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP TCP message from 172.17.27.59:43836 to 172.17.27.89:5060
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.27.89:5060;branch=z9hG4bK1884712
From: <sip:08978180483@172.17.27.89>;tag=EDA486F-8BC
To: <sip:+913349506956@172.17.27.59>;tag=298190~c961babc-d78c-40c7-9169-6d3071fa2c18-30651257

Date: Fri, 23 Aug 2024 10:35:08 GMT
Call-ID: 576dd100-1f017f3e-ff17-3b1b11ac@172.17.27.59
Server: Cisco-CUCM14.0
CSeq: 101 BYE
Content-Length: 0


14272: Aug 23 10:35:08.206: //19524/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_DISCONNECTING
14273: Aug 23 10:35:08.206: //19524/576DD1000000/CUBE_VT/SIP/API: voip_rtp_release_port (0)
14274: Aug 23 10:35:08.207: //19524/576DD1000000/CUBE_VT/SIP/API: cc_api_call_disconnect_done (0)
14275: Aug 23 10:35:08.207: //19524/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_DISCONNECTING, Next State: STATE_DEAD, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14276: Aug 23 10:35:08.208: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: sipSPIFlushDeferredQueue: Invalid deferredQueue
14277: Aug 23 10:35:08.208: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: ws_call_fork_cleanup: ws_info is NULL
14278: Aug 23 10:35:08.208: //19524/576DD1000000/CUBE_VT/SIP/API: voip_rtp_release_port (0)
14288: Aug 23 10:35:08.514: //19525/576DD1000000/
------------------ Cover Buffer ---------------
Search-key = +913349506956:08978180483:19525
Timestamp = Aug 23 10:34:59.757
CallID = 19525
Peer-CallID = 19524
Correlator = NA
Called-Number = 08978180483
Calling-Number = +913349506956
SIP CallID = 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
SIP SessionID = 0000617f00105000a0002800afb78bd9
GUID = 576DD1000000
Tenant = 0
-----------------------------------------------
14158: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/MISC/Matched Dialpeer: Dir: Outbound, Peer-Tag: 213
14159: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_NONE, Next State: STATE_IDLE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14160: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_SET_MODE, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14161: Aug 23 10:34:59.758: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PEER_DO, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14162: Aug 23 10:34:59.758: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PRE_SETUP, Current State: S_SIP_IWF_SDP_IDLE, Next State: CNFSM_NO_STATE_CHANGE
14165: Aug 23 10:34:59.758: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_INIT_CALL_SETUP, Current State: S_SIP_IWF_SDP_IDLE, Next State: CNFSM_NO_STATE_CHANGE
14166: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
14167: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_SETUP, Current State: STATE_IDLE
14168: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_IDLE, Next State: STATE_IDLE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_IDLE
14169: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_IDLE, Next State: STATE_IDLE, Current Sub-State: STATE_IDLE, Next Sub-State: STATE_IDLE
14170: Aug 23 10:34:59.757: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_call_proceeding (0)
14173: Aug 23 10:34:59.908: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_DNS_RESOLVED, Current State: STATE_IDLE
14174: Aug 23 10:34:59.908: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_IDLE, Next State: STATE_IDLE, Current Sub-State: STATE_IDLE, Next Sub-State: STATE_NONE
14175: Aug 23 10:34:59.908: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_allocate_port (8170)
14176: Aug 23 10:34:59.909: //19525/576DD1000000/CUBE_VT/SIP/FSM/Offer-Answer: Event: E_SIP_INVITE_SDP_SENT, Current State: S_SIP_EARLY_DIALOG_IDLE, Next State: S_SIP_EARLY_DIALOG_OFFER_SENT
14177: Aug 23 10:34:59.910: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_SENT_SDP, Current State: S_SIP_IWF_SDP_IDLE, Next State: S_SIP_IWF_SDP_SENT_AWAIT_SDP
14178: Aug 23 10:34:59.911: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_IDLE, Next State: STATE_SENT_INVITE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14179: Aug 23 10:34:59.911: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_create_session (0)
14180: Aug 23 10:34:59.911: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_set_non_rtp_call (0)
14181: Aug 23 10:34:59.911: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
14182: Aug 23 10:34:59.911: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 10.239.164.110:5060 to 10.232.135.130:5060
INVITE sip:08978180483@ims.airtel.in:5060 SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Remote-Party-ID: <sip:+913349506956@10.239.164.110>;party=calling;screen=yes;privacy=off

From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
Supported: timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1466814720-0000065536-0000000478-0991629740
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1724409299
Contact: <sip:+913349506956@10.239.164.110:5060>
Call-Info: <sip:10.239.164.110:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 60
Allow-Events: kpml, telephone-event
Max-Forwards: 68
Session-ID: 0000617f00105000a0002800afb78bd9;remote=00000000000000000000000000000000
Session-Expires: 18000
Content-Type: application/sdp

Content-Disposition: session;handling=required
Content-Length: 252

v=0
o=CiscoSystemsSIP-GW-UserAgent 7162 8197 IN IP4 10.239.164.110
s=SIP Call
c=IN IP4 10.239.164.110
t=0 0
m=audio 8170 RTP/AVP 0 101
c=IN IP4 10.239.164.110
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

14185: Aug 23 10:34:59.917: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1

To: <sip:08978180483@ims.airtel.in>
CSeq: 101 INVITE
Content-Length: 0


14186: Aug 23 10:34:59.917: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_SENT_INVITE
14187: Aug 23 10:34:59.917: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_SENT_INVITE, Next State: STATE_RECD_PROCEEDING, Current Sub-State: STATE_NONE, Next Sub-State: STATE_SETUP_BUFFERED
14188: Aug 23 10:35:04.221: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff>

P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
P-Early-Media: sendrecv,gated
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 233480777 233480777 IN IP4 10.232.135.132
s=SBC call
c=IN IP4 10.232.135.132
t=0 0
m=audio 57466 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

14190: Aug 23 10:35:04.220: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_RECD_PROCEEDING
14191: Aug 23 10:35:04.221: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_call_alert (0)
14192: Aug 23 10:35:04.221: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_RECD_PROCEEDING, Next State: STATE_RECD_PROCEEDING, Current Sub-State: STATE_SETUP_BUFFERED, Next Sub-State: STATE_SETUP_BUFFERED
14197: Aug 23 10:35:08.193: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188182A
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
CSeq: 101 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Contact: <sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff>
Require: timer
Session-Expires: 1800;refresher=uac
P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
Content-Length: 194
Content-Type: application/sdp

v=0
o=- 233480777 233480777 IN IP4 10.232.135.132
s=SBC call
c=IN IP4 10.232.135.132

t=0 0
m=audio 57466 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20

14199: Aug 23 10:35:08.193: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_RECD_PROCEEDING
14200: Aug 23 10:35:08.193: //19525/576DD1000000/CUBE_VT/SIP/FSM/Offer-Answer: Event: E_SIP_INVITE_RESP_SDP_RCVD, Current State: S_SIP_EARLY_DIALOG_OFFER_SENT, Next State: S_SIP_EARLY_DIALOG_OFFER_ANSWER_COMPLETE
14201: Aug 23 10:35:08.194: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_RCVD_SDP, Current State: S_SIP_IWF_SDP_SENT_AWAIT_SDP, Next State: S_SIP_IWF_SDP_DONE
14202: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/MISC/Error: sipSPI_ipip_upd_2833_dtmf_params: Unable to find proper instance for FMTP
14203: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/MISC/Error: sipSPI_ipip_upd_2833_dtmf_params: Unable to acquire event mask for rfc2833
14204: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/MISC/Media Stream Parameters: Stream Type: voice+dtmf, Stream State: STREAM_ADDING, Negotiated Codec: g711ulaw, Negotiated DTMF Type: rtp-nte, Stream Index: 1
14205: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_call_mode_update_ind (0)
14206: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
14210: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_caps_ind (0)
14211: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_RECD_PROCEEDING, Next State: STATE_RECD_PROCEEDING, Current Sub-State: STATE_SETUP_BUFFERED, Next Sub-State: STATE_NONE
14212: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_call_connected (0)
14213: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_RECD_PROCEEDING, Next State: SIP_STATE_RECD_SUCCESS, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14214: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/FSM/Offer-Answer: Event: E_SIP_DIALOG_ESTD, Current State: S_SIP_EARLY_DIALOG_OFFER_ANSWER_COMPLETE, Next State: S_SIP_MID_DIALOG_IDLE
14215: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_CALL_ACTIVE, Current State: S_SIP_IWF_SDP_DONE, Next State: CNFSM_NO_STATE_CHANGE
14216: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: SIP_STATE_RECD_SUCCESS, Next State: STATE_ACTIVE, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14217: Aug 23 10:35:08.194: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PEER_CAPS_ACK,, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14218: Aug 23 10:35:08.194: //19525/576DD1000000/CUBE_VT/SIP/FSM/IWF: Event: E_SIP_IWF_EV_PEER_CAPS_ACK,, Current State: CNFSM_CONTAINER_STATE, Next State: CNFSM_NO_STATE_CHANGE
14233: Aug 23 10:35:08.195: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 10.239.164.110:5060 to 10.232.135.130:5060
ACK sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK188320D6
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: kpml, telephone-event
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


14237: Aug 23 10:35:08.196: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
14238: Aug 23 10:35:08.196: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_set_non_rtp_call (0)
14239: Aug 23 10:35:08.196: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
14240: Aug 23 10:35:08.196: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_bridge_done (0)
14241: Aug 23 10:35:08.196: //19525/576DD1000000/CUBE_VT/SIP/API: ccsip_bridge (0)
14257: Aug 23 10:35:08.204: //19525/576DD1000000/CUBE_VT/SIP/FSM/Media-State: Event: E_IPIP_MEDIA_SERV_EV_XCODER_RESET_STREAM, Current State: CNFSM_CONTAINER_STATE, Next State: S_IPIP_MEDIA_SERV_STATE_IDLE
14258: Aug 23 10:35:08.204: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_update_callinfo (0)
14259: Aug 23 10:35:08.204: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_bridge_drop_done (0)
14263: Aug 23 10:35:08.205: //19525/576DD1000000/CUBE_VT/SIP/MISC/Call Disconnect: Initiated at: 0x260070A, Originated at: 0x260070B, Cause Code: 96
14266: Aug 23 10:35:08.205: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_update_interface_cac_resource (0)
14267: Aug 23 10:35:08.205: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_CC_CALL_DISCONNECT, Current State: STATE_ACTIVE
14268: Aug 23 10:35:08.206: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_ACTIVE, Next State: STATE_DISCONNECTING, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14269: Aug 23 10:35:08.206: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Sent: SIP UDP message from 10.239.164.110:5060 to 10.232.135.130:5060
BYE sip:10.232.135.130:5060;Dpt=7738-400;Hpt=8e72_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK18851FB0
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
Date: Fri, 23 Aug 2024 10:34:59 GMT
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
User-Agent: Cisco-SIPGateway/IOS-17.9.5a
Max-Forwards: 70
Timestamp: 1724409308
CSeq: 102 BYE
Reason: Q.850;cause=96
Session-ID: 0000617f00105000a0002800afb78bd9;remote=ec30a7d2290053f8bfaf72ad326615e5
Content-Length: 0


14279: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/Msg/ccsipDisplayMsg:
Received: SIP UDP message from 10.232.135.130:5060 to 10.239.164.110:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.239.164.110:5060;branch=z9hG4bK18851FB0
Call-ID: 2EAFD9E9-607211EF-8CE4F69E-FAE10052@10.239.164.110
From: <sip:+913349506956@ims.airtel.in>;tag=EDA3798-7A1
To: <sip:08978180483@ims.airtel.in>;tag=18l1ll5l
CSeq: 102 BYE
P-Charging-Vector: icid-value="bcf2.20.ea72e453.2943a6f9";orig-ioi=SIP_12105716_BOTHRA_3349506959;term-ioi=10.232.128.220
Content-Length: 0


14280: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/FSM/Event-Action: Event: SIPSPI_EV_NEW_MESSAGE, Current State: STATE_DISCONNECTING
14281: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_delete_dp_session (0)
14282: Aug 23 10:35:08.336: //19525/576DD1000000/CUBE_VT/SIP/API: cc_api_call_disconnect_done (0)
14283: Aug 23 10:35:08.336: //19525/576DD1000000/CUBE_VT/SIP/FSM/SPI-State-Change: Current State: STATE_DISCONNECTING, Next State: STATE_DEAD, Current Sub-State: STATE_NONE, Next Sub-State: STATE_NONE
14284: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/MISC/Error: sipSPIFlushDeferredQueue: Invalid deferredQueue
14285: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/MISC/Error: ws_call_fork_cleanup: ws_info is NULL
14286: Aug 23 10:35:08.335: //19525/576DD1000000/CUBE_VT/SIP/API: voip_rtp_release_port (8170)
BOTHRA_KOLKATA#
BOTHRA_KOLKATA#

 

 

0 Helpful

Go to solution
Vaijanath Sonvane
VIP Alumni
VIP Alumni
In response to Bothra Group

‎08-23-2024 07:13 AM

Hi @Bothra Group,

From the logs, it looks like CUBE is sending BYE signal to CUCM first with Cause Code =86 and then to the service provider with Cause Code = 96:

VaijanathSonvane_0-1724421401705.png

 

The cause code = 86 has below reasons:

VaijanathSonvane_1-1724421563445.png

This code typically indicates that the call was terminated because of an issue related to the voice codec or an incompatible network configuration, specifically related to codec negotiation or media handling. 

Troubleshooting Steps:

  • Verify the codecs configured on both ends of the call (calling device and receiving device). Ensure that both support the same codecs and that they are properly configured.
  • Look at the complete SIP call flow (INVITE, 200 OK, ACK, etc.) to see if there were any issues during the codec negotiation phase. Review logs from the CUBE Router and CUCM for any additional error messages or warnings that might provide more context.  As @Roger Kallberg mentioned, post the logs.
  • Investigate the network path between the devices to ensure that there are no issues with IP routing. Is the service provider RTP Connection IP c=IN IP4 10.232.135.132 reachable from CUBE?

 

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-23-2024 01:10 PM

I took another look at your output and noticed this.

14220: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14221: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14222: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14223: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14224: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Media Stream Parameters: Stream Type: voice-only, Stream State: STREAM_ADDING, Negotiated Codec: No Codec , Negotiated DTMF Type: inband-voice, Stream Index: 1
14225: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14226: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config
14227: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/FSM/Media-State: Event: E_IPIP_MEDIA_SERV_EV_PEER_CHNL_IND, Current State: S_IPIP_MEDIA_SERV_STATE_IDLE, Next State: S_IPIP_MEDIA_SERV_STATE_INIT_XCODER_RESERVED
14228: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/API: ccsip_xcoder_reserve (-1)
14229: Aug 23 10:35:08.196: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_sig_ip_address_to_bind: Dialpeer bind configured, interface addr failure
14230: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: bind interface address not available
14231: Aug 23 10:35:08.195: //19524/576DD1000000/CUBE_VT/SIP/MISC/Error: resolve_media_ip_address_to_bind: Invalid dialpeer bind media config

It looks like there might be an issue with your dial peer configuration. If you could share your complete configuration and explain what dial peers that are used for what we might be able to help you identify any potential issue(s).



Response Signature


Go to solution
Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎08-27-2024 02:53 AM

Dear team,

Please find the attached log and 10.232.135.132 reachable from CUBE.

Preview file
52 KB
Preview file
14 KB
Preview file
64 KB
Preview file
44 KB
0 Helpful

Go to solution
Bothra Group
Level 1
Level 1
In response to Bothra Group

‎08-27-2024 03:00 AM

Dear Roger,

Please see the below dial-peers.


BOTHRA_KOLKATA#sh run | s dial-peer
dial-peer voice 210 voip
description ### LAN OUTGOING_DIALPEER FROM CUBE TO CUCM ###
translation-profile incoming ITSP_CUCM
destination-pattern +913349506...
session protocol sipv2
session target ipv4:172.17.27.59
session transport udp
incoming uri via CUCM
voice-class sip early-offer forced
voice-class sip options-keepalive up-interval 30 down-interval 10 retry 2
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
no voice-class sip midcall-signaling block
dtmf-relay sip-notify rtp-nte sip-kpml
codec g711ulaw
fax rate 14400
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-throug h g711ulaw
no vad
dial-peer voice 211 voip
description ### WAN Incoming from ISP to Cube###
translation-profile incoming ITSP_CUCM
session protocol sipv2
session transport udp
incoming called-number +913349506...
voice-class sip early-offer forced
voice-class sip bind control source-interface GigabitEthernet0/0/1
voice-class sip bind media source-interface GigabitEthernet0/0/1
no voice-class sip midcall-signaling block
dtmf-relay sip-notify rtp-nte sip-kpml
codec g711ulaw
no vad
dial-peer voice 212 voip
description ###LAN Incoming dial-peer from cucm to cube ###
session protocol sipv2
incoming called-number .
incoming uri via CUCM
voice-class sip early-offer forced
voice-class sip options-keepalive up-interval 30 down-interval 10 retry 2
voice-class sip bind control source-interface GigabitEthernet0/0/0
voice-class sip bind media source-interface GigabitEthernet0/0/0
no voice-class sip midcall-signaling block
dtmf-relay sip-notify rtp-nte sip-kpml
codec g711ulaw
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-throug h g711ulaw
no vad
dial-peer voice 213 voip
description ### WAN Outgoing dialpeer frm cube to itsp ###
destination-pattern .T
session protocol sipv2
session target dns:ims.airtel.in
session transport udp
voice-class sip early-offer forced
no voice-class sip block 180
voice-class sip options-keepalive up-interval 30 down-interval 10 retry 2
voice-class sip session refresh
voice-class sip bind control source-interface GigabitEthernet0/0/1
voice-class sip bind media source-interface GigabitEthernet0/0/1
dtmf-relay sip-notify rtp-nte sip-kpml
codec g711ulaw
no vad
BOTHRA_KOLKATA#

0 Helpful

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 03:13 AM

I can see this in your shared configuration file, but what I can’t easily understand is what is the intended purpose of each of the dial peers. That’s what I’m asking you to explain, not to simply post the configuration of the dial peers.



Response Signature


Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 03:06 AM

Please enable all of the suggested debugs and collect the output into one text file as requested.



Response Signature


Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 03:23 AM

As your using sub-interfaces on GigabitEthernet0/0/0 to set the IP address you cannot use that on the CM facing dial peers as the bind. You’ll need to use the sub-interface for the bind. Please update your configuration with this and redo the test.



Response Signature


Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 04:28 AM - edited ‎08-27-2024 08:44 AM

Do these changes on your dial peers and try again with all the suggested debugs running at the same time.

 

dial-peer voice 210 voip
 no translation-profile incoming ITSP_CUCM !Not needed on outbound dial peer
 no incoming uri via CUCM !Not needed on outbound dial peer
 voice-class sip bind control source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 voice-class sip bind media source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
!
voice class uri PSTN sip !Create a class uri to be used for inbound dial peer match from PSTN/ITSP
 host ipv4:<IP address as seen in VIA header for inbound calls from PSTN>
!
dial-peer voice 211 voip
 no incoming called-number +913349506... ! Remove match for called number to use the below match instead
 incoming uri via PSTN !Use info in VIA header to match inbound calls from PSTN/ITSP
!
dial-peer voice 212 voip
 translation-profile incoming ITSP_CUCM !Moved from DP 210 as it looks to be used by the inbound dial peer for calls comming from CM
 no incoming called-number . !Not needed on inbound dial peer as you use VIA header info with command incoming uri via CUCM
 voice-class sip bind control source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 voice-class sip bind media source-interface GigabitEthernet0/0/0.1 !Change the bind to the sub-interface
 no voice-class sip options-keepalive up-interval 30 down-interval 10 retry 2 !Not needed on inbound dial peer

 

Collect the debug output if there is still problem and post it in one file please.

Edit: I added a few things to the suggested changes as I missed the inbound translation used on DP 210. It is now removed from that DP and added to DP 212 as that with my suggested changes should be the only viable inbound DP matched for calls coming from CM.



Response Signature


Go to solution
Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎08-27-2024 05:21 AM

Dear Roger,

I have changed the configuration as you suggested but now outgoing calls not initializing and immediately beep sound coming.

i have enabled debug commands and see the below log as I'm unbale to attach the file. getting error that does not match its file extension.

 

Log Buffer (102400 bytes):

Aug 27 12:09:00.209: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK151125836df08
From: <sip:172.17.27.59>;tag=172980605
To: <sip:172.17.27.89>
Date: Tue, 27 Aug 2024 12:09:00 GMT
Call-ID: 23611b80-1f018270-14429-3b1b11ac@172.17.27.59
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.17.27.59:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Aug 27 12:09:00.210: //72256/FA4F605D9A81/SIP/Media/sipSPICopyStunConfigFromPeerToCCB: STUN Usage is not enabled
Aug 27 12:09:00.210: //72256/FA4F605D9A81/SIP/Media/sipSPISetMediaSrcAddr: Media src addr for stream 1 = 10.239.164.110
Aug 27 12:11:00.305: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.17.27.89:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.27.59:5060;branch=z9hG4bK151191803ff11
From: <sip:172.17.27.59>;tag=735202613
To: <sip:172.17.27.89>
Date: Tue, 27 Aug 2024 12:11:00 GMT
Call-ID: 6ae7a780-1f018270-1442f-3b1b11ac@172.17.27.59

User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.17.27.59:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Aug 27 12:11:00.306: //72265/41E4927F9A8A/SIP/Media/sipSPICopyStunConfigFromPeerToCCB: STUN Usage is not enabled
Aug 27 12:11:00.307: //72265/41E4927F9A8A/SIP/Media/sipSPISetMediaSrcAddr: Media src addr for stream 1 = 10.239.164.110

Regards,

Hari

 

0 Helpful

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-27-2024 05:33 AM

That debug output only contains a SIP option ping message. There is no call attempt visible.



Response Signature


0 Helpful

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-28-2024 09:16 AM

Where you able to collect logs from your gateway that contains output for a call attempt? If you don’t see any call activity in your gateway it means that your CM isn’t sending the call to the gateway. Is your SIP trunk between CM and the gateway in an up state? What does a DNA in CM tell you, does it say that the call would be routed via the SIP trunk to your gateway?



Response Signature


0 Helpful

Go to solution
Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎08-28-2024 10:56 PM

Dear Roger,

I have changed the below lines, and now outbound calls are working fine but incoming is not working from outside. Thank you so much for your assistance. I have attached present running configuration and logs.

voice-class sip bind control source-interface GigabitEthernet0/0/0.1 
 voice-class sip bind media source-interface GigabitEthernet0/0/0.1

 Regards,

Hari

Preview file
82 KB
Preview file
14 KB
0 Helpful

Go to solution
Roger Kallberg
VIP
VIP
In response to Bothra Group

‎08-29-2024 04:00 AM - edited ‎08-30-2024 07:20 AM

From what I can tell you're sending the call back to the service provider instead of sending it to CM. This is what the debugs shows.

image.pngimage.pngimage.pngimage.pngimage.png
As you can see the calls is matched inbound on dial peer 211 and this is based on your configuration what you expect it to do, but then instead of matching dial peer 210 to send the call to CM it matches dial peer 213 that sends the call back to your service provider. This happens since you translate the called number on ingress from the SP to the last three digits, then it doesn't match DP 210 as that is matching in +E.164 format, it will instead match DP 213 that has destination-pattern .T as that matches basically anything.

Using this type of broad match is a quite bad and dangerous thing to do as it opens up for call loops or at least hair-pinning as in your case here. I would suggest that you change the destination pattern on DP 213 to something that only matches outbound calls, what that would be depends on how you make outbound calls. For example it might be destination-pattern 0T if you use a zero (0) to make outbound calls.

Since you route to CM in +E.164 format on DP 210 and the SP is sending the called number to you in +E.164 format you don't need to do any translation of the called number, that is if you have the directory numbers in CM in +E.164 format. If you don't and have it in for example last three digit format you'd need to do a translation, but that is better done on egress when the call leaves the outbound dial peer towards CM. To do that you should do these changes.

 

voice translation-rule 210
 rule 1 /^\+913349506\(...\)$/ /\1/
!
voice translation-profile TO_CUCM_OUT
 translate called 210
!
dial-peer voice 210 voip
 translation-profile outgoing TO_CUCM_OUT

 

 

To be clear the above is only needed if you do not have the directory numbers in CM in +E.164 format.

To clean up your configuration and have it as what I've previously suggested please do these changes.

 

service timestamps log datetime msec
service password-encryption
service sequence-numbers
!
voice service voip
 mode border-element
  no allow-connections h323 to h323
  no allow-connections h323 to sip
  no allow-connections sip to h323
!
voice class uri PSTN sip
 host ipv4:10.232.135.130
!
no voice translation-rule 18
no voice translation-rule 100
no voice translation-rule 110
no voice translation-rule 150
!
no voice translation-profile E164_FORMAT
no voice translation-profile ITSP_CUCM
!
dial-peer voice 210 voip
 no translation-profile incoming ITSP_CUCM
 no incoming uri via CUCM
!
dial-peer voice 211 voip
 no translation-profile incoming ITSP_CUCM
 no incoming called-number .%
 incoming uri via PSTN
!
no ntp server 10.232.135.130
no ntp server 172.17.27.59

 

 

This will remove the translation that you currently have on ingress from the SP so that DP 210 is matched on egress and sends the call to CM, it will as well remove some incorrect and/or unneeded configuration that I urge you do please follow as suggested.



Response Signature


Customers Also Viewed These Support Documents