cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

123
Views
0
Helpful
0
Replies
Highlighted
Engager

SIP TRUNK CUCM to CLOUD PBX

Hi guys,

 

I would share with you a problem that happens when Cloud pbx trying to transfer a call to CUCM extension by SIP trunk. We have received a bye from CLOUD PBX.

 

Let me show the sip signling. May be someone can help the possible cause. So the guys is check the nat at moment.

INVITE:
10/30/2019 18:01:44.115 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 914 from 200.201.x.154:[5060]:
INVITE sip:8000@192.168.12.4:5060 SIP/2.0
Record-Route: <sip:200.201.x.154;lr;ftag=3204996662;did=286.c6d5ebb>
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK6b67.a6b6c53.0
Via: SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK2855112711
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>
Call-ID: 0_2444231384@192.168.81.155
CSeq: 2 INVITE
Contact: <sip:8300@177.105.72.98:1024>
Content-Type: application/sdp
Max-Forwards: 69
User-Agent: Yealink SIP-T19P_E2 53.83.0.35
Supported: replaces
Content-Length: 284

v=0
o=- 20015 20015 IN IP4 177.105.72.98
s=SDP data
c=IN IP4 177.105.72.98
t=0 0
m=audio 12464 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=ptime:20
a=sendrecv
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

trying – 100
10/30/2019 18:01:44.116 |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 200.201.x.154:[5060]:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK6b67.a6b6c53.0,SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK2855112711
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>
Date: Wed, 30 Oct 2019 20:01:44 GMT
Call-ID: 0_2444231384@192.168.81.155
CSeq: 2 INVITE
Allow-Events: presence
Content-Length: 0

Ringing – 180
10/30/2019 18:01:44.121 |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 200.201.x.154:[5060]:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK6b67.a6b6c53.0,SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK2855112711
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>;tag=c5e14bf4-f433-4657-a87b-ddf7bd938f36-30999313
Date: Wed, 30 Oct 2019 20:01:44 GMT
Call-ID: 0_2444231384@192.168.81.155
CSeq: 2 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Contact: <sip:8000@192.168.12.4:5060>
Record-Route: <sip:200.201.x.154;lr;ftag=3204996662;did=286.c6d5ebb>
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: "Recepcao-PE" <sip:8000@192.168.12.4>
Remote-Party-ID: "Recepcao-PE" <sip:8000@192.168.12.4>;party=called;screen=yes;privacy=off
Content-Length: 0

OK – 200 (SDP)
10/30/2019 18:01:45.718 |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 200.201.x.154:[5060]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK6b67.a6b6c53.0,SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK2855112711
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>;tag=c5e14bf4-f433-4657-a87b-ddf7bd938f36-30999313
Date: Wed, 30 Oct 2019 20:01:44 GMT
Call-ID: 0_2444231384@192.168.81.155
CSeq: 2 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Contact: <sip:8000@192.168.12.4:5060>
Record-Route: <sip:200.201.x.154;lr;ftag=3204996662;did=286.c6d5ebb>
Supported: replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: "Recepcao-PE" <sip:8000@192.168.12.4>
Remote-Party-ID: "Recepcao-PE" <sip:8000@192.168.12.4>;party=called;screen=yes;privacy=off
Content-Type: application/sdp
Content-Length: 212

v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 192.168.12.4
s=SIP Call
c=IN IP4 192.168.12.6
t=0 0
m=audio 17094 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

ACK
10/30/2019 18:01:45.790 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 801 from 200.201.x.154:[5060]:
ACK sip:8000@192.168.12.4:5060 SIP/2.0
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK6b67.a6b6c53.2
Via: SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK1903258121
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>;tag=c5e14bf4-f433-4657-a87b-ddf7bd938f36-30999313
Call-ID: 0_2444231384@192.168.81.155
CSeq: 2 ACK
Contact: <sip:8300@177.105.72.98:1024>
Proxy-Authorization: Digest username="8300", realm="acme.jrcpabx.com.br", nonce="5db9ec460000a7544aec52537acd0057c63b925c9386ff97", uri="sip:8000@acme.jrcpabx.com.br:5060", response="be928a5aab7159035b68e15efc61f451", algorithm=MD5
Max-Forwards: 69
User-Agent: Yealink SIP-T19P_E2 53.83.0.35
Content-Length: 0

BYE
10/30/2019 18:01:47.696 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 785 from 200.201.x.154:[5060]:
BYE sip:8000@192.168.12.4:5060 SIP/2.0
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK7b67.fa10e795.0
Via: SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK4283377024
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>;tag=c5e14bf4-f433-4657-a87b-ddf7bd938f36-30999313
Call-ID: 0_2444231384@192.168.81.155
CSeq: 3 BYE
Contact: <sip:8300@177.105.72.98:1024>
Proxy-Authorization: Digest username="8300", realm="acme.jrcpabx.com.br", nonce="5db9ec460000a7544aec52537acd0057c63b925c9386ff97", uri="sip:8000@192.168.12.4:5060", response="9e4de0520f38a4af1fef301a427fdd05", algorithm=MD5
Max-Forwards: 69
User-Agent: Yealink SIP-T19P_E2 53.83.0.35
Content-Length: 0

OK – 200
10/30/2019 18:01:47.700 |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 200.201.x.154:[5060]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.201.x.154:5060;branch=z9hG4bK7b67.fa10e795.0,SIP/2.0/UDP 177.105.72.98:1024;rport=1024;received=177.105.72.98;branch=z9hG4bK4283377024
From: "Recepção 8300" <sip:8300@acme.jrcpabx.com.br:5060>;tag=3204996662
To: <sip:8000@192.168.12.4:5060>;tag=c5e14bf4-f433-4657-a87b-ddf7bd938f36-30999313
Date: Wed, 30 Oct 2019 20:01:47 GMT
Call-ID: 0_2444231384@192.168.81.155
CSeq: 3 BYE
Content-Length: 0

 

 

 

The Specialist form Cloud PBX share the screen of the signaling in his server.SIP_tools.jpg

 

 

Daniel Sobrinho
Everyone's tags (1)
CreatePlease to create content
Content for Community-Ad
Future of Work Virtual Summit Day 5

Cisco COVID-19 Survey