If so there might be a workarround: make sure that you enable the
use_domain
parameter of the registrar module.
This settings solved my problem Andrei. Thanks very much. If you could make a seperate page just for parameter setting for every module it will be very great andrei. If you need my help I can do that for you.
I followed the suggestion given by Jiri for multiple domains as below, I think he missed the param for the registrar module which took my head off.
fragments:
# -- multi-domain modparam("domain", "db_mode", 1) modparam("usrloc|group", "use_domain", 1)modparam("registrar","use_domain",1)
...
if (!is_from_local()) { # check against domain-module table .... /* outbound */ break; };
# our domains ...
if (!www_authorize("", "subscriber")) { # challenge if none or invalid credentials www_challenge("", "0"); break; };
Thanks a lot.
Kannaiyan
----- Original Message ----- From: "Andrei Pelinescu-Onciul" pelinescu-onciul@fokus.fraunhofer.de To: "Kannaiyan Natesan" nkans@lycos.co.uk Cc: "Jiri Kuthan" jiri@iptel.org; serusers@lists.iptel.org Sent: Thursday, November 27, 2003 8:49 AM Subject: Re: [Serusers] SER Crash
On Nov 27, 2003 at 01:18, Kannaiyan Natesan nkans@lycos.co.uk wrote:
SER is only stable from few seconds to few minutes.
Does it crash? Do you get a coredump?
Do you use a cvs head config with 0.8.12? If so there might be a workarround: make sure that you enable the
use_domain
parameter of the registrar module.
If it still crashes:
Try to start ser with debugging and loggind to stderr: ser -dd -E -w. -f your.cfg 2>/tmp/log (if you use a config not derived from the standard one, you might have to add log_stderror=yes)
Before starting ser, run "ulimit -c unlimited" and make sure ser is allowed to dump core in the current dir (-w .). If you get the core make a tar.gz with it + ser binaries and sources (if you compiled it by yourself) and either put it on some web/ftp site or send it to serhelp@lists.iptel.org.
Andrei