[OpenSER-Users] OpenSER 1.3 NAT Config Issues

Ali Jawad ali.jawad at splendor.net
Mon Feb 11 14:17:59 CET 2008


Thanks Henning for the hint, I have read through the docs, can anyone
please confirm my findings 

> modparam("nathelper", "rtpproxy_disable", 1)
Should be 
modparam("nathelper", "rtpproxy_sock", "udp:localhost:25061") "If
mediaproxy is running UDP on port 25061"

And according to 
http://www.openser.org/docs/modules/1.3.x/registrar.html#AEN438

In was removed, as the module internally loads this value from the
"USRLOC' module (see the "nat_bflag"  USRLOC parameter). '"
So 
modparam("registrar", "nat_flag", 6)
Will end up as 
# modparam("registrar", "nat_flag", 6)
modparam("usrloc", "nat_bflag", 6)



Thx

-----Original Message-----
From: Henning Westerholt [mailto:henning.westerholt at 1und1.de] 
Sent: Monday, February 11, 2008 3:04 PM
To: users at lists.openser.org
Cc: Ali Jawad
Subject: Re: [OpenSER-Users] OpenSER 1.3 NAT Config Issues

On Monday 11 February 2008, Ali Jawad wrote:
> Hi All I am trying to configure mediaproxy to be used with OpenSER 1.3
> following the tutorial from
>
> http://siprouter.onsip.org/doc/gettingstarted/ch08.html#id2660207
>
> So far I got two errors
>
> modparam("nathelper", "rtpproxy_disable", 1)
>
> ERROR:core:set_mod_param_regex: parameter <rtpproxy_disable> not found
> in module <nathelper>
>
> Feb 11 14:50:13 [3207] CRITICAL:core:yyerror: parse error in config
> file, line 194, column 19-20: Can't set module parameter
>
>
> modparam("registrar", "nat_flag", 6)
>
> Feb 11 14:50:13 [3207] ERROR:core:set_mod_param_regex: parameter
> <nat_flag> not found in module <registrar>
>
> Feb 11 14:50:13 [3207] CRITICAL:core:yyerror: parse error in config
> file, line 200, column 19-20: Can't set module parameter
>
> What should I use instead of
> [..]

Hi,

perhaps you can check the module documentation of the registrar and
nathelper 
module for 1.3 to get the new syntax? :-) There exists also a porting 
document on the wiki which address this issues.

Cheers,

Henning

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





More information about the Users mailing list