[OpenSIPS-Users] media-proxy invalid IP in sdp

Saul Ibarra Corretge saul at ag-projects.com
Tue Jul 19 09:03:20 CEST 2011


Hi,

On Jul 19, 2011, at 7:02 AM, Pasan Meemaduma wrote:

> HI All,
> 
> We are using opensips 1.5.3-1 with media proxy 2.4.2-1
> 
> I recently came across this problem where When the originator send a reinvite  media proxy put wrong IP address in sdp section. Is this a bug in media-proxy module? But there are other calls which doesn't have this issue.
> 
> This happens when an outgoing  call is try to transfer from one extension to another in a PBX . The initial outgoing call connect correctly.  It happens for the re invite.
> 
> 
> sip trace. I have highlighted the corrupted sdp line. 
> 
> 
> U 2011/07/19 13:40:37.279456 220.233.253.162:5060 -> 58.96.1.2:5060
> INVITE sip:XXXXXXXXXX at 58.96.1.15;user=phone SIP/2.0.
> Route: <sip:58.96.1.2;lr=on;ftag=6cb89dff62723a57196e58aeb9f6d18e;nat=yes>.
> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE.
> Supported: 100rel,from-change,timer.
> User-Agent: OxO_GW_710/135.002.
> Session-Expires: 43200;refresher=uac.
> P-Asserted-Identity: <sip:61439063069 at 58.96.1.2;user=phone>.
> Contact: <sip:61439063069 at 172.16.16.10;transport=UDP;user=phone>.
> Content-Type: application/sdp.
> To: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=3a60010f-3863.
> From: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.
> Call-ID: b6e8a93851a9060ce6b03a73bcd642d3 at 172.16.16.10.
> CSeq: 1211550125 INVITE.
> Via: SIP/2.0/UDP 172.16.16.10;rport;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9.
> Max-Forwards: 70.
> Content-Length: 215.
> .
> v=0.
> o=default 1311046964 1311046966 IN IP4 172.16.16.10.
> s=-.
> c=IN IP4 172.16.16.10.
> t=0 0.
> m=audio 32000 RTP/AVP 18 106.
> a=sendrecv.
> a=rtpmap:106 telephone-event/8000.
> a=fmtp:106 0-15.
> a=ptime:40.
> a=maxptime:120.
> 
> 
> U 2011/07/19 13:40:37.284308 58.96.1.2:5060 -> 220.233.253.162:5060
> SIP/2.0 100 Giving a try.
> To: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=3a60010f-3863.
> From: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.
> Call-ID: b6e8a93851a9060ce6b03a73bcd642d3 at 172.16.16.10.
> CSeq: 1211550125 INVITE.
> Via: SIP/2.0/UDP 172.16.16.10;rport=5060;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9;received=220.233.253.162.
> Server: Exetel Voip.
> Content-Length: 0.
> .
> 
> 
> U 2011/07/19 13:40:37.284406 58.96.1.2:5060 -> 58.96.1.15:5060
> INVITE sip:XXXXXXXXXX at 58.96.1.15;user=phone SIP/2.0.
> Record-Route: <sip:58.96.1.2;lr=on;ftag=6cb89dff62723a57196e58aeb9f6d18e;nat=yes>.
> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE.
> Supported: 100rel,from-change,timer.
> User-Agent: OxO_GW_710/135.002.
> Session-Expires: 43200;refresher=uac.
> P-Asserted-Identity: <sip:61439063069 at 58.96.1.2;user=phone>.
> Contact: <sip:61439063069 at 220.233.253.162:5060;transport=UDP;user=phone>.
> Content-Type: application/sdp.
> To: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=3a60010f-3863.
> From: <sip:XXXXXXXXXX at 58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.
> Call-ID: b6e8a93851a9060ce6b03a73bcd642d3 at 172.16.16.10.
> CSeq: 1211550125 INVITE.
> Via: SIP/2.0/UDP 58.96.1.2;branch=z9hG4bKff37.ac7f65a6.0.
> Via: SIP/2.0/UDP 172.16.16.10;received=220.233.253.162;rport=5060;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9.
> Max-Forwards: 69.
> Content-Length: 274.
> P-hint: rr-enforced.
> .
> v=0.
> o=default 1311046964 1311046966 IN IP4 172.16.16.10.
> s=-.
> c=IN IP4 220.233.253.16258.96.1.2.   <-- This should be c=IN IP4  58.96.1.2.
> t=0 0.
> m=audio 55222 RTP/AVP 18 106.
> a=sendrecv.
> a=rtpmap:106 telephone-event/8000.
> a=fmtp:106 0-15.
> a=ptime:40.
> a=maxptime:120.
> a=direction:active.
> a=oldmediaip:172.16.16.10.
> 

How are you using MediaProxy? Using engage_mediaproxy or the individual functions? Any chance you called use_media_proxy twice?


Regards,

-- 
Saúl Ibarra Corretgé
AG Projects








More information about the Users mailing list