hi all, I am trying to run nathelper with rtpproxy, and I am currently using a configuration based on a supposedly working standard example config, but I haven't got it to work yet.
I took a look at an example configuration for SER as an application layer gateway,between two RFC1918 networks, and noticed that rtpproxy was called with some parameters in there (i.e. force_rtp_prpoxy(EI), obviously denoting the direction from External network tow an Internal one)
Does anyone know if these parameters are mandatory? Or if someone has a currently working nathelper/rtpproxy configuration, please provide any feedback on that.
I also keep getting a "cannot extract body from the message" error from the rtpproxy.
Cheers
maka wrote:
hi all, I am trying to run nathelper with rtpproxy, and I am currently using a configuration based on a supposedly working standard example config, but I haven't got it to work yet.
I took a look at an example configuration for SER as an application layer gateway,between two RFC1918 networks, and noticed that rtpproxy was called with some parameters in there (i.e. force_rtp_prpoxy(EI), obviously denoting the direction from External network tow an Internal one)
Does anyone know if these parameters are mandatory? Or if someone has a currently working nathelper/rtpproxy configuration, please provide any feedback on that.
Yes, they are if you are using rtpproxy in the "bridge" mode. The reason for that is that rtpptoxy has no way to see if the message goes from inside out or vice versa.
-Maxim
I also keep getting a "cannot extract body from the message" error from the rtpproxy.
Cheers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Thank you Maxim. Is this(bridge) the right mode for using rtpproxy in conjunction with nathelper? There was no nathelper and fix_nated_contact() or fix_nated_sdp() involved in the alg.cfg sample configuration file, but I assume this is due to that both the internal and external networks are RFC1918. Is there a special way to invoke rtpproxy when using with nathelper, or a special way beyond the one that is specified in the nathelper example configuraiton?
On Fri, 11 Mar 2005 21:09:59 +0200, Maxim Sobolev sobomax@portaone.com wrote:
maka wrote:
hi all, I am trying to run nathelper with rtpproxy, and I am currently using a configuration based on a supposedly working standard example config, but I haven't got it to work yet.
I took a look at an example configuration for SER as an application layer gateway,between two RFC1918 networks, and noticed that rtpproxy was called with some parameters in there (i.e. force_rtp_prpoxy(EI), obviously denoting the direction from External network tow an Internal one)
Does anyone know if these parameters are mandatory? Or if someone has a currently working nathelper/rtpproxy configuration, please provide any feedback on that.
Yes, they are if you are using rtpproxy in the "bridge" mode. The reason for that is that rtpptoxy has no way to see if the message goes from inside out or vice versa.
-Maxim
I also keep getting a "cannot extract body from the message" error from the rtpproxy.
Cheers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
maka -
Maxim Sobolev