<p dir="ltr">I'm using port 12221 for rtpproxy (from default script) and port 12223 for OpenSIPS. Are those 'bad ports' like the error says?</p>
<div class="gmail_quote">On 19 Aug 2015 06:48, "Nabeel" <<a href="mailto:nabeelshikder@gmail.com">nabeelshikder@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>The rtpproxy error is resolved with your suggestion, but I still get the 'bad port' errors in the log followed by CANCEL of the call:</div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">ERROR:core:parse_via: bad port<br>ERROR:core:parse_via: <SIP/2.0/TCP 10.61.208.143:46032:-1;rport;branch=z9hG4bK78006#015#012Max-Forwards: 70#015#012To: <<a href="mailto:sip%3A%2B447984977774@sipdomain.com" target="_blank">sip:+447984977774@sipdomain.com</a>;transport=tcp>#015#012From: <<a href="mailto:sip%3A%2B447479189410@sipdomain.com" target="_blank">sip:+447479189410@sipdomain.com</a>>;tag=z9hG4bK93013084#015#012Call-ID: <a href="http://358919227046@10.61.208.143#015%23012CSeq" target="_blank">358919227046@10.61.208.143#015#012CSeq</a>: 1 CANCEL#015#012Contact: <sip:<a href="tel:%2B447479189410" value="+447479189410" target="_blank">+447479189410</a>@10.61.208.143:46032;transport=tcp>#015#012Expires: 3600#015#012User-Agent: Agent/1.3.4/MP-S168#015#012Content-Length: 0#015#012#015#012><br>ERROR:core:parse_via: parsed so far:<SIP/2.0/TCP <a href="http://10.61.208.143:46032" target="_blank">10.61.208.143:46032</a>><br>ERROR:core:get_hdr_field: bad via<br>DBG:core:set_err_info: ec: 1, el: 3, ei: 'error parsing Via'<br>DBG:core:get_hdr_field: error exit<br>INFO:core:parse_headers: bad header field<br>ERROR:core:parse_msg: message=<CANCEL <a href="mailto:sip%3A%2B447984977774@sipdomain.com" target="_blank">sip:+447984977774@sipdomain.com</a>;transport=tcp SIP/2.0#015#012Via: SIP/2.0/TCP 10.61.208.143:46032:-1;rport;branch=z9hG4bK78006#015#012Max-Forwards: 70#015#012To: <<a href="mailto:sip%3A%2B447984977774@sipdomain.com" target="_blank">sip:+447984977774@sipdomain.com</a>;transport=tcp>#015#012From: <<a href="mailto:sip%3A%2B447479189410@sipdomain.com" target="_blank">sip:+447479189410@sipdomain.com</a>>;tag=z9hG4bK93013084#015#012Call-ID: <a href="http://358919227046@10.61.208.143#015%23012CSeq" target="_blank">358919227046@10.61.208.143#015#012CSeq</a>: 1 CANCEL#015#012Contact: <sip:<a href="tel:%2B447479189410" value="+447479189410" target="_blank">+447479189410</a>@10.61.208.143:46032;transport=tcp>#015#012Expires: 3600#015#012User-Agent: Agent/1.3.4/MP-S168#015#012Content-Length: 0#015#012#015#012><br>ERROR:core:receive_msg: Unable to parse msg received from [<a href="http://188.29.165.141:46315" target="_blank">188.29.165.141:46315</a>]<br>ERROR:core:tcp_handle_req: receive_msg failed</blockquote><div><br></div><div><br></div><div>The SIP trace of the call is here:</div><div><br></div><div><a href="http://pastebin.com/dNpau6GT" target="_blank">http://pastebin.com/dNpau6GT</a></div><div><br></div><div>I am using the default config scripts. Please advise how to fix this. </div><div><br></div><div><br></div><div> </div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 14 August 2015 at 18:36, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<tt>yes, you should.<br>
<br>
Regards,<br>
</tt><span>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
</span><div><div><div>On 14.08.2015 18:06, Nabeel wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">Should I make the same change to rtpproxy_offer?</p>
<p dir="ltr"> if (is_method("INVITE")) { <br>
if (isflagset(NAT)) {<br>
rtpproxy_offer("ro");<br>
} <br>
</p>
<div class="gmail_quote">On 14 Aug 2015 13:09, "Bogdan-Andrei
Iancu" <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <tt>I see....you have
a </tt><tt>onreply_route[handle_nat] in your script,
doing:</tt><tt><br>
</tt><tt><br>
</tt><tt> if ( isflagset(NAT) )</tt><tt><br>
</tt><tt> rtpproxy_answer("ro");</tt><tt><br>
</tt><tt><br>
</tt><tt>Change that to :</tt><tt><br>
</tt><tt><br>
</tt><tt> if ( isflagset(NAT) &&
has_body("application/sdp") )</tt><tt><br>
</tt><tt> rtpproxy_answer("ro");</tt><tt><br>
</tt><tt><br>
</tt><tt>Regards,</tt><br>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>On 14.08.2015 15:04, Nabeel wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">The 'ringing' stage of a call is when the
error occurs. Why should 180 Ringing lead to an error?
</p>
<div class="gmail_quote">On 14 Aug 2015 12:47,
"Bogdan-Andrei Iancu" <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <tt>Hi,<br>
<br>
ACK request or 180 ringing reply are part of a
call and they do not have a body.<br>
<br>
It depends on your scripting to see when the
rtpproxy are called (for what sip message).<br>
<br>
You may use the script_trace() function :<br>
<a href="http://www.opensips.org/Documentation/Script-CoreFunctions-1-11#toc42" target="_blank">http://www.opensips.org/Documentation/Script-CoreFunctions-1-11#toc42</a><br>
to see which sip messages to generate the err log.<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>On 14.08.2015 14:15, Nabeel wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">Hi Bogdan,</p>
<p dir="ltr">Thanks, but I had no intentions of
using a SIP message without a body; all I'm
trying to do is make a normal call with
OpenSIPS. </p>
<p dir="ltr">Please explain why I'm getting a SIP
message without a body and how do I fix it? </p>
<div class="gmail_quote">On 14 Aug 2015 11:12,
"Bogdan-Andrei Iancu" <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <tt>Hi
Nabeel,<br>
<br>
You may get this error when calling the
rtpproxy functions for a SIP message
without a body.<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>On 14.08.2015 09:58, Nabeel wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I am getting this error when making
some calls:</div>
<div><br>
</div>
<div>
<div>ERROR:rtpproxy:force_rtp_proxy:
Unable to parse body</div>
</div>
<div><br>
</div>
<div>I think this may be related to
'rtpproxy_offer' and 'rtpproxy_answer'
in the config file but I don't know
how to fix it. I am using the default
OpenSIPS config.</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>
</blockquote></div>