[Devel] Openser / Nathelper question

[Bogdan-Andrei Iancu]

Hi Tim,

as you can see the the SDP contains "a=nortpproxy:yes" which means 
another rtpproxy was inserted on the way and the nathelper does not try 
again to force rtpproxy....

check your configuration as something is not right - there is a rtproxy 
marker into SDP but the IP does not seam to be altered.

a work around, see the force_rtp_proxy(flags), the "f" flag:
        http://openser.org/docs/modules/1.0.x/nathelper.html#AEN267

regards,
bogdan

Tim Barrett wrote:

> Bogdan,
>
> The can't extract body message was related to the BYE message and not 
> the okay.
>
> I have included the message and header for the oka in case you can 
> spot any reason why
> "force_rtp_proxy("r","10.242.209.10")" in onreply_route is not 
> changing the contact IP and rtp port.
>
> 3(3539) msgbuf[SIP/2.0 200 OK
> From: "unknown"<sip:10 at 10.242.209.10:5060>;tag=13763711702
> To: <sip:51 at 10.242.209.10:5060>;tag=0-13c4-4407080b-ccde0-bf5
> Call-ID: 6072FCBF-78E6-475A-BB4C-9899681C5F14 at 192.168.100.20
> CSeq: 1 INVITE
> Via: SIP/2.0/UDP 10.242.209.10;branch=z9hG4bK3567.5b078e35.0
> Via: SIP/2.0/UDP 
> 192.168.100.20;received=168.192.100.250;rport=15060;branch=z9hG4bKc0a8641400000018440707360000071400000007 
>
> Contact: <sip:51 at 168.192.200.250:5060>
> Record-Route: <sip:10.242.209.10;lr;ftag=13763711702>
> Content-Type: application/SDP
> Content-Length: 241
>
> v=0
> o=Intel_IPCCLib 116034812 116034813 IN IP4 192.168.200.1
> s=Intel_SIP_CCLIB
> c=IN IP4 192.168.200.1
> t=0 0
> a=direction:active
> m=audio 49152 RTP/AVP 0
> a=fmtp:98 mode=20
> a=nortpproxy:yes
> a=ptime:20
> a=rtpmap:0 PCMU/8000
> a=sendrecv
> ] msgbody <v=0
> o=Intel_IPCCLib 116034812 116034813 IN IP4 192.168.200.1
> s=Intel_SIP_CCLIB
> c=IN IP4 192.168.200.1
> t=0 0
> a=direction:active
> m=audio 49152 RTP/AVP 0
> a=fmtp:98 mode=20
> a=nortpproxy:yes
> a=ptime:20
> a=rtpmap:0 PCMU/8000
> a=sendrecv
>
>>
>