[OpenSIPS-Users] Upgrade from openser 1.3 to opensips 1.6

[Ovidiu Sas]

The parameters for rtpproxy_offer/answer are the same as the old
parameters for force_rtp_proxy.
The swap flag was no longer necessary and therefor removed.

Regards,
Ovidiu Sas

On Wed, Mar 2, 2011 at 1:35 AM, Andrew O. Zhukov <gnugk at telegroup.com.ua> wrote:
> On 03/01/2011 06:59 PM, Ovidiu Sas wrote:
>>
>> The README file has a straight forward example:
>> http://www.opensips.org/html/docs/modules/devel/nathelper.html#id293550
>>
>> Let me know if that is not enough.
>
> It's not enough.
>
> openser use a pussle algorithm to inform rtp proxy when to start
> rtp proxy.
>
> As I undersand you simlify it using rtpproxy_offer->rtpproxy_answer.
> Good job. Thanks.
>
> If I'll keep old style algorthm and use
> rtpproxy_answer instead of rtp_proxy
> does the rtpproxy get a right parameters set or not?
>
>
>
>>
>> Regards.
>> Ovidiu Sas
>>
>> On Tue, Mar 1, 2011 at 11:54 AM, Andrew O. Zhukov
>> <gnugk at telegroup.com.ua>  wrote:
>>>
>>>> Force_rtp_proxy() was replaced by rtpproxy_offer() (first step) and
>>>> rtpproxy_answer() (second step). See:
>>>>       http://www.opensips.org/html/docs/modules/1.6.x/nathelper.html
>>>>>
>>>>> and
>>>
>>> Bogdan,
>>>
>>> As I understand. If I use the very old style stabile working config with
>>> nat
>>> fags, (!search("^Content-Length:[ ]*0")), other tricks it would be done
>>> to change:
>>>
>>> force_rtp_proxy(); to the rtpproxy_answer();
>>>
>>> And everyting will be ok.
>>>
>>> Is it correct?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>
>