[OpenSIPS-Users] ERROR:rtpproxy:force_rtp_proxy: Unable to parse body

Bogdan-Andrei Iancu bogdan at opensips.org
Fri Aug 14 19:36:38 CEST 2015


yes, you should.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 14.08.2015 18:06, Nabeel wrote:
>
> Should I make the same change to rtpproxy_offer?
>
>     if (is_method("INVITE")) {
>                if (isflagset(NAT)) {
>                       rtpproxy_offer("ro");
>                }
>
> On 14 Aug 2015 13:09, "Bogdan-Andrei Iancu" <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>> wrote:
>
>     I see....you have a onreply_route[handle_nat] in your script, doing:
>
>         if ( isflagset(NAT) )
>             rtpproxy_answer("ro");
>
>     Change that to :
>
>         if ( isflagset(NAT) && has_body("application/sdp") )
>             rtpproxy_answer("ro");
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>     On 14.08.2015 15:04, Nabeel wrote:
>>
>>     The 'ringing' stage of a call is when the error occurs.  Why
>>     should 180 Ringing lead to an error?
>>
>>     On 14 Aug 2015 12:47, "Bogdan-Andrei Iancu" <bogdan at opensips.org
>>     <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hi,
>>
>>         ACK request or 180 ringing reply are part of a call and they
>>         do not have a body.
>>
>>         It depends on your scripting to see when the rtpproxy are
>>         called (for what sip message).
>>
>>         You may use the script_trace() function :
>>         http://www.opensips.org/Documentation/Script-CoreFunctions-1-11#toc42
>>         to see which sip messages to generate the err log.
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>         OpenSIPS Founder and Developer
>>         http://www.opensips-solutions.com
>>
>>         On 14.08.2015 14:15, Nabeel wrote:
>>>
>>>         Hi Bogdan,
>>>
>>>         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.
>>>
>>>         Please explain why I'm getting a SIP message without a body
>>>         and how do I fix it?
>>>
>>>         On 14 Aug 2015 11:12, "Bogdan-Andrei Iancu"
>>>         <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>>
>>>             Hi Nabeel,
>>>
>>>             You may get this error when calling the rtpproxy
>>>             functions for a SIP message without a body.
>>>
>>>             Regards,
>>>
>>>             Bogdan-Andrei Iancu
>>>             OpenSIPS Founder and Developer
>>>             http://www.opensips-solutions.com
>>>
>>>             On 14.08.2015 09:58, Nabeel wrote:
>>>>             Hi,
>>>>
>>>>             I am getting this error when making some calls:
>>>>
>>>>             ERROR:rtpproxy:force_rtp_proxy: Unable to parse body
>>>>
>>>>             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.
>>>>
>>>>
>>>>
>>>>             _______________________________________________
>>>>             Users mailing list
>>>>             Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>>>             http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150814/d472b366/attachment-0001.htm>


More information about the Users mailing list