Hey,
Is it possible that Kamailio 1.5.x silently discarded modparams that
were not valid and Kamailio 3.0 doesn't ?
David
On 2010-06-25 10:11, Klaus Darilion wrote:
IIRC the problem is that the string is interpreted as
pattern, thus
"pua" matches "pua_dialoginfo" and "pua".
So you have to specify "pua" separately.
regards
Klaus
Am 25.06.2010 15:28, schrieb David:
> Hey,
>
> Is this format still valid in Kamailio 3.0 ?
>
> modparam("module1|module2|module3", "db_url",
> "mysql://me:secret@server/database")
>
>
> This line :
>
>
modparam("auth_db|usrloc|acc|domain|avpops|presence|presence_xml|pua|dialog",
>
> "db_url",
"mysql://kamailiodev:kamailiosecret@192.168.1.10/kamailiodev")
>
> gives me this error :
> -e
> 0(9334) ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter
> <db_url> not found in module <pua_dialoginfo>
> 0(9334) : <core> [cfg.y:3333]: parse error in config file
> /etc/kamailio/kamailio.cfg, line 399, column 153: Can't set module
> parameter
> ERROR: bad config file (1 errors)
> 0(9334) ERROR: dialog [dlg_db_handler.c:177]: invalid database handle
>
> Funny thing is I have not set the module parameter for pua_dialoginfo,
> looks like kamailio is getting confused with my pipes, if I name each
> parameter one at a time, it works fine.
>
> Any thoughts on this?
>
> David
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users