<div dir="ltr">Dear Alex,<br><br>I did what you asked me to do and I still getting the same error....Please find below the config:<br><br><br>if(!cr_route("default", "0", "$rU", "$rU", "call_id")){<br>
sl_send_reply("403", "Not allowed");<br> } else {<br> # In cas of failure, re-route the request<br> t_on_failure("1");<br> t_on_reply("1");<br>force_rtp_proxy();<br>
<br><br>t_relay();<br> }<br><br><br><br>onreply_route[1] {<br># if (t_check_status("2[0-9][0-9]") )<br> if((t_check_status("200|183|180") && search("Content_Type: application/sdp")) || search("Content-Type: application/sdp"))<br>
<br><br>{<br> force_rtp_proxy();<br> }<br>exit;<br>}<br><br><br><br>Is there anything that I should add?<br><br>Regards<br><br><div class="gmail_quote">On Sun, Mar 8, 2009 at 11:59 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It means you are applying the NAT UAC test function for SDP to a request that does not have an SDP payload.<br>
<br>
It should only be applied to messages that contain SDP payloads. Easy way to check:<br>
<br>
<br>
if(search("Content-Type: application/sdp"))<br>
<br>
Also, only the following kinds of messages can contain SDP descriptors:<br>
<br>
1) Initial INVITEs;<br>
<br>
2) Sequential INVITEs;<br>
<br>
3) 200 OKs to INVITE transactions;<br>
<br>
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:<br>
<br>
if((t_check_status("200|183|180") && search("Content_Type: application/sdp")) || search("Content-Type: application/sdp"))<br>
<br>
michel freiha wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
Hi all,<br>
I'm getting the below error when trying to make a call through OpenSIPS<br>
<br>
DBG:core:parse_headers: flags=ffffffffffffffff<br>
Mar 6 20:43:29 [7117] ERROR:nathelper:extract_body: message body has length zero<br>
Mar 6 20:43:29 [7117] ERROR:nathelper:force_rtp_proxy2_f: can't extract body from the message<br>
<br>
Can you explain please how this is affecting the call specially that the call is working fine<br>
<br>
Regards<br>
<br>
<br></div></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote>
<br>
<br>
-- <br>
Alex Balashov<br>
Evariste Systems<br>
Web : <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
Tel : (+1) (678) 954-0670<br>
Direct : (+1) (678) 954-0671<br>
Mobile : (+1) (678) 237-1775<br>
</blockquote></div><br></div>