[OpenSIPS-Users] Rtp proxy issue

[Alex Balashov]

It means you are applying the NAT UAC test function for SDP to a request 
that does not have an SDP payload.

It should only be applied to messages that contain SDP payloads.  Easy 
way to check:


    if(search("Content-Type: application/sdp"))

Also, only the following kinds of messages can contain SDP descriptors:

1) Initial INVITEs;

2) Sequential INVITEs;

3) 200 OKs to INVITE transactions;

4) Non-100 1xx provisional messages -- these are usually 183 Session in 
Progress and 180 Ringing messages.  However, technically, any non-100 
1xx message can contain an SDP body per the RFC.  In practise, this is 
rare, so t_check_status("200|183|180") will work for most scenarios. 
But if you want to be strictly correct, do:

   if((t_check_status("200|183|180") && search("Content_Type: 
application/sdp")) || search("Content-Type: application/sdp"))

michel freiha wrote:

> Hi all,
> I'm getting the below error when trying to make a call through OpenSIPS
> 
> DBG:core:parse_headers: flags=ffffffffffffffff
> Mar  6 20:43:29 [7117] ERROR:nathelper:extract_body: message body has 
> length zero
> Mar  6 20:43:29 [7117] ERROR:nathelper:force_rtp_proxy2_f: can't extract 
> body from the message
> 
> Can you explain please how this is affecting the call specially that the 
> call is working fine
> 
> Regards
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-- 
Alex Balashov
Evariste Systems
Web    : http://www.evaristesys.com/
Tel    : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775