Hi Alfred,
You are right that some rules should be followed to get interoperability.
That's why the default value is one that basically guarantee that. Only
if you really know what you are doing, you should start changing this
parameter.
I see a need to be able to control this param, mainly because in some
cases I really want to force rtpproxy on my platform, even if already
dome by other servers...and this because I really want to controll the
traffic. I having an automatic system to disable the proxy based on some
hdr is not something I want to have.
shortly, if people use the default cfg, nothing changes. For other
people, looking from more complex scenario, this param is what they need.
regards,
bogdan
Alfred E. Heggestad wrote:
Hi
I think the "a=nortpproxy:yes" attribute should be standardised somehow.
Otherwise you will end up with massive interop problems between various
OpenSER/SER installations all using their own locally configured
attribute.
/alfred
Bogdan-Andrei Iancu wrote:
Hi Klaus,
It will change both - what is added and what is looking after.
regards,
bogdan
Klaus Darilion wrote:
Hi!
does this only change the inserted string or does it also change the
string which will be searched for by nathelper module to prevent
proxy-chains?
Bogdan-Andrei Iancu wrote:
Hi everybody,
Thanks to a contribution from Jeremie, nathelper module offers the
possibility to configure the "a=nortpproxy:yes\r\n" string. This is
a string marker added by nathelper when rtpproxy is enabled.
The new "nortpproxy_str" parameter:
http://www.openser.org/docs/modules/1.2.x/nathelper.html#AEN217
allows you to both change or disable this string marker.
For more see:
http://openser.org/pipermail/users/2006-September/006519.html
regards,
Bogdan
_______________________________________________
Devel mailing list
Devel(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel