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
<[email protected]> 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
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
