<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:10pt"><div>HI All,</div><div><br></div><div>We are using opensips 1.5.3-1 with media proxy 2.4.2-1</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div><br></div><div>sip trace. I have highlighted the corrupted sdp line. <br></div><div><br></div><div><br></div><div>U 2011/07/19 13:40:37.279456 220.233.253.162:5060 -> 58.96.1.2:5060<br>INVITE sip:XXXXXXXXXX@58.96.1.15;user=phone SIP/2.0.<br>Route:
<sip:58.96.1.2;lr=on;ftag=6cb89dff62723a57196e58aeb9f6d18e;nat=yes>.<br>Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE.<br>Supported: 100rel,from-change,timer.<br>User-Agent: OxO_GW_710/135.002.<br>Session-Expires: 43200;refresher=uac.<br>P-Asserted-Identity: <sip:61439063069@58.96.1.2;user=phone>.<br>Contact: <sip:61439063069@172.16.16.10;transport=UDP;user=phone>.<br>Content-Type: application/sdp.<br>To: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=3a60010f-3863.<br>From: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.<br>Call-ID: b6e8a93851a9060ce6b03a73bcd642d3@172.16.16.10.<br>CSeq: 1211550125 INVITE.<br>Via: SIP/2.0/UDP 172.16.16.10;rport;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9.<br>Max-Forwards: 70.<br>Content-Length: 215.<br>.<br>v=0.<br>o=default 1311046964 1311046966 IN IP4 172.16.16.10.<br>s=-.<br>c=IN IP4 172.16.16.10.<br>t=0 0.<br>m=audio 32000 RTP/AVP 18
106.<br>a=sendrecv.<br>a=rtpmap:106 telephone-event/8000.<br>a=fmtp:106 0-15.<br>a=ptime:40.<br>a=maxptime:120.<br><br><br>U 2011/07/19 13:40:37.284308 58.96.1.2:5060 -> 220.233.253.162:5060<br>SIP/2.0 100 Giving a try.<br>To: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=3a60010f-3863.<br>From: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.<br>Call-ID: b6e8a93851a9060ce6b03a73bcd642d3@172.16.16.10.<br>CSeq: 1211550125 INVITE.<br>Via: SIP/2.0/UDP 172.16.16.10;rport=5060;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9;received=220.233.253.162.<br>Server: Exetel Voip.<br>Content-Length: 0.<br>.<br><br><br>U 2011/07/19 13:40:37.284406 58.96.1.2:5060 -> 58.96.1.15:5060<br>INVITE sip:XXXXXXXXXX@58.96.1.15;user=phone SIP/2.0.<br>Record-Route: <sip:58.96.1.2;lr=on;ftag=6cb89dff62723a57196e58aeb9f6d18e;nat=yes>.<br>Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE.<br>Supported:
100rel,from-change,timer.<br>User-Agent: OxO_GW_710/135.002.<br>Session-Expires: 43200;refresher=uac.<br>P-Asserted-Identity: <sip:61439063069@58.96.1.2;user=phone>.<br>Contact: <sip:61439063069@220.233.253.162:5060;transport=UDP;user=phone>.<br>Content-Type: application/sdp.<br>To: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=3a60010f-3863.<br>From: <sip:XXXXXXXXXX@58.96.1.2;user=phone>;tag=6cb89dff62723a57196e58aeb9f6d18e.<br>Call-ID: b6e8a93851a9060ce6b03a73bcd642d3@172.16.16.10.<br>CSeq: 1211550125 INVITE.<br>Via: SIP/2.0/UDP 58.96.1.2;branch=z9hG4bKff37.ac7f65a6.0.<br>Via: SIP/2.0/UDP 172.16.16.10;received=220.233.253.162;rport=5060;branch=z9hG4bK442522244c8b1ab3aa05203ea0e6e2f9.<br>Max-Forwards: 69.<br>Content-Length: 274.<br>P-hint: rr-enforced.<br>.<br>v=0.<br>o=default 1311046964 1311046966 IN IP4 172.16.16.10.<br>s=-.<br style="background-color: rgb(255, 0, 127);"><span style="background-color: rgb(255, 0, 127);">c=IN IP4
220.233.253.16258.96.1.2. <-- This should be c=IN IP4 58.96.1.2.</span><br>t=0 0.<br>m=audio 55222 RTP/AVP 18 106.<br>a=sendrecv.<br>a=rtpmap:106 telephone-event/8000.<br>a=fmtp:106 0-15.<br>a=ptime:40.<br>a=maxptime:120.<br>a=direction:active.<br>a=oldmediaip:172.16.16.10.<br></div><div><br></div></div></body></html>