Below is the call flow.
PSTN user----->SIP Provider---->SIP trunk(CUCM)------FXS port(VG224).
here calls from a specific mobile service provider is failing as our cucm sending wrong IP address as RTP connection address in 200 OK message
INVITE coming in:
07/18/2017 13:43:00.503 CCM|//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 1032 from 10.141.6.254:[5060]:
INVITE sip:+33149187446@10.140.25.17:5060 SIP/2.0
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf63c3612137c9c90
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
To: <sip:+33149187446@10.140.25.17>
Call-ID: 2030454806_1884190@10.141.6.254
CSeq: 5609 INVITE
Max-Forwards: 68
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE,NOTIFY,UPDATE,OPTIONS
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: <sip:+33612174955@10.141.6.254:5060>
P-Asserted-Identity: <sip:+33612174955@ISBC003.ORT.BOUYGTEL.NET;user=phone>
Supported: timer
Session-Expires: 1800
Min-SE: 90
Content-Length: 275
Content-Disposition: session; handling=required
Content-Type: application/sdp
v=0
o=Sonus_UAC 21738 32447 IN IP4 10.141.6.254
s=SIP Media Capabilities
c=IN IP4 10.141.6.4
t=0 0
m=audio 21260 RTP/AVP 8 18 96
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=sendrecv
a=ptime:20
============================================
sending 100 Trying
07/18/2017 13:43:00.503 CCM|//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 1032 from 10.141.6.254:[5060]:
INVITE sip:+33149187446@10.140.25.17:5060 SIP/2.0
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf63c3612137c9c90
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
To: <sip:+33149187446@10.140.25.17>
Call-ID: 2030454806_1884190@10.141.6.254
CSeq: 5609 INVITE
Max-Forwards: 68
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE,NOTIFY,UPDATE,OPTIONS
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: <sip:+33612174955@10.141.6.254:5060>
P-Asserted-Identity: <sip:+33612174955@ISBC003.ORT.BOUYGTEL.NET;user=phone>
Supported: timer
Session-Expires: 1800
Min-SE: 90
Content-Length: 275
Content-Disposition: session; handling=required
Content-Type: application/sdp
v=0
o=Sonus_UAC 21738 32447 IN IP4 10.141.6.254
s=SIP Media Capabilities
c=IN IP4 10.141.6.4
t=0 0
m=audio 21260 RTP/AVP 8 18 96
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=sendrecv
a=ptime:20
======================================================================
sending 180 ringing
07/18/2017 13:43:00.551 CCM|//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 10.141.6.254:[5060]:
SIP/2.0 180 Ringing
Date: Tue, 18 Jul 2017 11:43:00 GMT
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
Allow-Events: presence
P-Asserted-Identity: "PC-SECU PC-Securite" <sip:+33149187446@10.140.25.17>
Supported: Geolocation
Remote-Party-ID: "PC-SECU PC-Securite" <sip:+33149187446@10.140.25.17>;party=called;screen=yes;privacy=off
Content-Length: 0
To: <sip:+33149187446@10.140.25.17>;tag=55cf195e-f1d7-4a01-9cad-5c6e8fd60383-71636967
Contact: <sip:+33149187446@10.140.25.17:5060>
Call-ID: 2030454806_1884190@10.141.6.254
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf63c3612137c9c90
CSeq: 5609 INVITE
================================================================
Sending 200 OK (here CUCM is supposed to send the IP address of the VG224 GW in c=IN IP4 SDP parameter, but it wrongly sending IP address 10.141.6.4, this is the IP address of SIP provider RTP connection IP address. So Telco rejecting the call from their side)
07/18/2017 13:43:09.221 CCM|//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 10.141.6.254:[5060]:
SIP/2.0 200 OK
Date: Tue, 18 Jul 2017 11:43:00 GMT
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
Allow-Events: presence
P-Asserted-Identity: "PC-SECU PC-Securite" <sip:+33149187446@10.140.25.17>
Supported: replaces
Supported: Geolocation
Remote-Party-ID: "PC-SECU PC-Securite" <sip:+33149187446@10.140.25.17>;party=called;screen=yes;privacy=off
Content-Length: 278
Require: timer
To: <sip:+33149187446@10.140.25.17>;tag=55cf195e-f1d7-4a01-9cad-5c6e8fd60383-71636967
Contact: <sip:+33149187446@10.140.25.17:5060>
Content-Type: application/sdp
Call-ID: 2030454806_1884190@10.141.6.254
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf63c3612137c9c90
CSeq: 5609 INVITE
Session-Expires: 1800;refresher=uas
v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 10.140.25.17
s=SIP Call
c=IN IP4 10.141.6.4
t=0 0
m=audio 21260 RTP/AVP 8 18 96
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:18 G729/8000
a=ptime:20
a=fmtp:18 annexb=no
a=inactive
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
===========================================================
receive ACK
07/18/2017 13:43:09.235 CCM|//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 356 from 10.141.6.254:[5060]:
ACK sip:+33149187446@10.140.25.17:5060 SIP/2.0
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf77f1cf9137c9c90
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
To: <sip:+33149187446@10.140.25.17>;tag=55cf195e-f1d7-4a01-9cad-5c6e8fd60383-71636967
Call-ID: 2030454806_1884190@10.141.6.254
CSeq: 5609 ACK
Max-Forwards: 70
Content-Length: 0
======================================================================================
Receives BYE from Telco
07/18/2017 13:43:09.235 CCM|//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 380 from 10.141.6.254:[5060]:
BYE sip:+33149187446@10.140.25.17:5060 SIP/2.0
Via: SIP/2.0/UDP 10.141.6.254:5060;branch=z9hG4bK06Bf7802bf0137c9c90
From: <sip:+33612174955@10.141.6.254>;tag=gK06622447
To: <sip:+33149187446@10.140.25.17>;tag=55cf195e-f1d7-4a01-9cad-5c6e8fd60383-71636967
Call-ID: 2030454806_1884190@10.141.6.254
CSeq: 5610 BYE
Max-Forwards: 70
Reason: Q.850;cause=41
Content-Length: 0
