Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
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
174
Views
2
Helpful
4
Replies

Outgoing sip calls issue via sip trunk

Go to solution
NurlanED
Level 1
Level 1

‎05-01-2024 11:32 AM

Hey, everybody.


I am experiencing problems with outgoing calls, including from a cell phone to a landline. I believe the problem may be on the ISP side, but I'm having a hard time gathering evidence to support that theory.

PS. VGWdebug02- I get messages from İTSP even when there are no calls

SIP Call messages tracing is e

AZENCRRT01#
May 1 16:28:43.644: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:192.168.33.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
Max-Forwards: 70
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>
Contact: <sip:nocallerid@192.168.33.5:5060>
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
CSeq: 102 OPTIONS
User-Agent: 16LTS
Date: Wed, 01 May 2024 16:28:43 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


May 1 16:28:43.645: //124570/B6043256A8A7/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>;tag=274D0D15-DF2
Date: Wed, 01 May 2024 20:28:43 GMT
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 373

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

nabled
AZENCRRT01#
May 1 16:27:43.626: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:0514339314@10.150.152.98:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.7.15:5060;branch=z9hG4bK1ad78b1b4f09a2
From: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
To: <sip:0514339314@10.150.152.98>
Date: Wed, 01 May 2024 16:27:43 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
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.16.7.15:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 0000393100105000a000025041000001;remote=00000000000000000000000000000000
Cisco-Guid: 3138416384-0000065536-0000016939-0252121260
Session-Expires: 1800
P-Asserted-Identity: "test" <sip:11118@172.16.7.15>
Remote-Party-ID: "test" <sip:11118@172.16.7.15>;party=calling;screen=yes;privacy=off
Contact: <sip:11118@172.16.7.15:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="CSFjahangirtes";bfcp
Max-Forwards: 69
Content-Length: 0


May 1 16:27:43.628: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0514339314@192.168.33.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11B1537
Remote-Party-ID: "test" <sip:11118@192.168.33.6>;party=calling;screen=yes;privacy=off
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3138416384-0000065536-0000016939-0252121260
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1714580863
Contact: <sip:11118@192.168.33.6:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Session-Expires: 1800
Content-Length: 0


May 1 16:27:43.628: //124567/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.16.7.15:5060;branch=z9hG4bK1ad78b1b4f09a2
From: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
To: <sip:0514339314@10.150.152.98>
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Content-Length: 0


May 1 16:27:43.641: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11B1537;received=192.168.33.6;rport=62522
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
CSeq: 101 INVITE
Server: 16LTS
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Session-Expires: 1800;refresher=uas
Contact: <sip:0514339314@192.168.33.5:5060>
Content-Length: 0


May 1 16:27:43.642: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:192.168.33.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK634877e7;rport
Max-Forwards: 70
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as72e0e71c
To: <sip:192.168.33.6>
Contact: <sip:nocallerid@192.168.33.5:5060>
Call-ID: 7845dea4133b109428c282932f404a1b@192.168.33.5:5060
CSeq: 102 OPTIONS
User-Agent: 16LTS
Date: Wed, 01 May 2024 16:27:43 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


May 1 16:27:43.642: //124569/92409E42A8A6/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK634877e7;rport
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as72e0e71c
To: <sip:192.168.33.6>;tag=274C22B3-C82
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: 7845dea4133b109428c282932f404a1b@192.168.33.5:5060
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 373

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

May 1 16:27:43.682: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11B1537;received=192.168.33.6;rport=62522
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>;tag=as40992e1e
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
CSeq: 101 INVITE
Server: 16LTS
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Session-Expires: 1800;refresher=uas
Contact: <sip:0514339314@192.168.33.5:5060>
Content-Type: application/sdp
Require: timer
Content-Length: 261

v=0
o=root 2005401543 2005401543 IN IP4 192.168.33.5
s=16PBX
c=IN IP4 192.168.33.5
t=0 0
m=audio 27794 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv

May 1 16:27:43.683: //124567/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.7.15:5060;branch=z9hG4bK1ad78b1b4f09a2
From: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
To: <sip:0514339314@10.150.152.98>;tag=274C22DC-106C
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:0514339314@10.150.152.98>;party=called;screen=no;privacy=off
Contact: <sip:0514339314@10.150.152.98:5060;transport=tcp>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 273

v=0
o=CiscoSystemsSIP-GW-UserAgent 4718 6059 IN IP4 10.150.152.98
s=SIP Call
c=IN IP4 10.150.152.98
t=0 0
m=audio 8474 RTP/AVP 0 8 101
c=IN IP4 10.150.152.98
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

May 1 16:27:43.746: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:0514339314@10.150.152.98:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.16.7.15:5060;branch=z9hG4bK1ad78c7e7d7052
From: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
To: <sip:0514339314@10.150.152.98>;tag=274C22DC-106C
Date: Wed, 01 May 2024 16:27:43 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
User-Agent: Cisco-CUCM14.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Session-ID: 0000393100105000a000025041000001;remote=a7448ca08df7b93abbc0d1ab39738103
Content-Type: application/sdp
Content-Length: 237

v=0
o=CiscoSystemsCCM-SIP 39738103 1 IN IP4 172.16.7.15
s=SIP Call
c=IN IP4 172.16.7.15
b=TIAS:64000
b=AS:80
t=0 0
m=audio 27794 RTP/AVP 0 101
a=ptime:20
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

May 1 16:27:43.747: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0514339314@192.168.33.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11C22F4
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>;tag=as40992e1e
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 244

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

May 1 16:27:57.225: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:11118@192.168.33.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK72d91cec;rport
Max-Forwards: 70
From: <sip:0514339314@192.168.33.5>;tag=as40992e1e
To: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
CSeq: 102 BYE
User-Agent: 16LTS
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0


May 1 16:27:57.225: //124567/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:11118@172.16.7.15:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.150.152.98:5060;branch=z9hG4bK11D7DD
From: <sip:0514339314@10.150.152.98>;tag=274C22DC-106C
To: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Max-Forwards: 70
Timestamp: 1714580877
CSeq: 101 BYE
Reason: Q.850;cause=16
Content-Length: 0


May 1 16:27:57.226: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK72d91cec;rport
From: <sip:0514339314@192.168.33.5>;tag=as40992e1e
To: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
Date: Wed, 01 May 2024 20:27:57 GMT
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0


May 1 16:27:57.235: //124567/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.150.152.98:5060;branch=z9hG4bK11D7DD
From: <sip:0514339314@10.150.152.98>;tag=274C22DC-106C
To: "test" <sip:11118@172.16.7.15>;tag=39738103~aacb92ca-d987-46c4-8ba2-eb001de99838-60367323
Date: Wed, 01 May 2024 16:27:57 GMT
Call-ID: bb106f00-1f0125da-778a8-f0710ac@172.16.7.15
Server: Cisco-CUCM14.0
CSeq: 101 BYE
Content-Length: 0

VGWdebug02

AZENCRRT01#
May 1 16:28:43.644: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:192.168.33.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
Max-Forwards: 70
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>
Contact: <sip:nocallerid@192.168.33.5:5060>
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
CSeq: 102 OPTIONS
User-Agent: 16LTS
Date: Wed, 01 May 2024 16:28:43 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


May 1 16:28:43.645: //124570/B6043256A8A7/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>;tag=274D0D15-DF2
Date: Wed, 01 May 2024 20:28:43 GMT
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 373

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

 

Labels:
0 Helpful
2 Accepted Solutions

Accepted Solutions

Go to solution
Maren Mahoney
VIP
VIP

‎05-02-2024 11:34 AM

It is the far-end Asterisk system that is hanging up the call, and it is doing so after the call is established and in progress for approximately 13.5 seconds. It is showing normal call clearing as its reason, like someone hung up. But if the BYE is in error, you'd have to look at the Asterisk system logs to determine why it is disconnecting the call.

Maren

 

May 1 16:27:43.747: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0514339314@192.168.33.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11C22F4
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>;tag=as40992e1e
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 244

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

May 1 16:27:57.225: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:11118@192.168.33.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK72d91cec;rport
Max-Forwards: 70
From: <sip:0514339314@192.168.33.5>;tag=as40992e1e
To: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
CSeq: 102 BYE
User-Agent: 16LTS
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

View solution in original post

Go to solution
NurlanED
Level 1
Level 1
In response to Maren Mahoney

‎05-03-2024 03:46 AM

Thank you Maren, 

This information was very helpful to me.

View solution in original post

0 Helpful
4 Replies 4

Go to solution
b.winter
VIP
VIP

‎05-02-2024 01:36 AM - edited ‎05-02-2024 01:38 AM

Which problems do you face? You didn't mention anything. "I have a problem" is not a problem description.

The call in the logs show a normal succesfull call, which lasts for about 12s. No issue there.

And please don't post any logs directly into the forum message. It will make the thread endlessly long and unreadable.
Save the logs as a txt-File and attach it to the message.

0 Helpful

Go to solution
Roger Kallberg
VIP
VIP

‎05-02-2024 06:19 AM

Those messages that you refer to as received when there is no calls are know as SIP option ping. That is used for the other end to know that your end is alive and operational.

This is from your shared information is an example of that.

May 1 16:28:43.644: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:192.168.33.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
Max-Forwards: 70
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>
Contact: <sip:nocallerid@192.168.33.5:5060>
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
CSeq: 102 OPTIONS
User-Agent: 16LTS
Date: Wed, 01 May 2024 16:28:43 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


May 1 16:28:43.645: //124570/B6043256A8A7/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK2356431d;rport
From: "nocallerid" <sip:nocallerid@192.168.33.5>;tag=as70170e10
To: <sip:192.168.33.6>;tag=274D0D15-DF2
Date: Wed, 01 May 2024 20:28:43 GMT
Call-ID: 52e3325d52c1d9351ecbf6d626bb3845@192.168.33.5:5060
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
CSeq: 102 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 373

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



Response Signature


Go to solution
Maren Mahoney
VIP
VIP

‎05-02-2024 11:34 AM

It is the far-end Asterisk system that is hanging up the call, and it is doing so after the call is established and in progress for approximately 13.5 seconds. It is showing normal call clearing as its reason, like someone hung up. But if the BYE is in error, you'd have to look at the Asterisk system logs to determine why it is disconnecting the call.

Maren

 

May 1 16:27:43.747: //124568/BB106F000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0514339314@192.168.33.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.6:5060;branch=z9hG4bK11C22F4
From: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
To: <sip:0514339314@192.168.33.5>;tag=as40992e1e
Date: Wed, 01 May 2024 20:27:43 GMT
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 244

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

May 1 16:27:57.225: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:11118@192.168.33.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.33.5:5060;branch=z9hG4bK72d91cec;rport
Max-Forwards: 70
From: <sip:0514339314@192.168.33.5>;tag=as40992e1e
To: "test" <sip:11118@192.168.33.6>;tag=274C22A5-1427
Call-ID: 923E7B1E-70E11EF-A8A595C6-60A3C178@192.168.33.6
CSeq: 102 BYE
User-Agent: 16LTS
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

Go to solution
NurlanED
Level 1
Level 1
In response to Maren Mahoney

‎05-03-2024 03:46 AM

Thank you Maren, 

This information was very helpful to me.

0 Helpful
Customers Also Viewed These Support Documents