Hi Emil,
 
Thanks for your infor.
 
I tried and it still didn't work. Now I doubt if the /etc/ser/ser.cfg (see the following) takes effect or not. I changed the settings and if I ran the server by command ' # ser ', no problem. But if I ran it like ' # ser -f ser.cfg ', then it told me
ERROR: bad config file (11 errors)
Actually I didn't change too much on the default ser.cfg.
 
Pls indicate.
_________________________________________________________________________________
#
# $Id: ser.cfg,v 1.12 2002/10/21 02:40:06 jiri Exp $
#
# simple quick-start config script
#
 
# ----------- global configuration parameters ------------------------
 
debug=9          # debug level (cmd line: -dddddddddd)
fork=no
log_stderror=no # (cmd line: -E)
check_via=no    # (cmd. line: -v)
dns=no           # (cmd. line: -r)
rev_dns=no      # (cmd. line: -R)
port=5060
children=4
fifo="/tmp/ser_fifo"
 
# ------------------ module loading ----------------------------------
 
# Uncomment this if you want to use SQL database
#loadmodule "//usr/lib/ser/modules/mysql.so"
 
loadmodule "//usr/lib/ser/modules/sl.so"
loadmodule "//usr/lib/ser/modules/tm.so"
loadmodule "//usr/lib/ser/modules/rr.so"
loadmodule "//usr/lib/ser/modules/maxfwd.so"
loadmodule "//usr/lib/ser/modules/usrloc.so"
loadmodule "//usr/lib/ser/modules/registrar.so"
 
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
#loadmodule "//usr/lib/ser/modules/auth.so"
 
# ----------------- setting module-specific parameters ---------------
 
# -- usrloc params --
 
modparam("usrloc", "db_mode",   0)
 
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
#modparam("usrloc", "db_mode", 2)
 
# -- auth params --
# Uncomment if you are using auth module
#
#modparam("auth", "secret", "alsdkhglaksdhfkloiwr")
#modparam("auth", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
#modparam("auth", "password_column", "password")
 
# -------------------------  request routing logic -------------------
 
# main routing logic
 
route{
 
        # initial sanity checks -- messages with
        # max_forwars==0, or excessively long requests
        if (!mf_process_maxfwd_header("10")) {
                sl_send_reply("483","Too Many Hops");
                break;
        };
        if (len_gt( max_len )) {
                sl_send_reply("513", "Message too big");
                break;
        };
 
        # Do strict routing if pre-loaded route headers present
        rewriteFromRoute();
 
        # if the request is for other domain use UsrLoc
        # (in case, it does not work, use the following command
        # with proper names and addresses in it)
        if (uri==sip.mycompany.com) {
 
                if (method=="REGISTER") {
 
# Uncomment this if you want to use digest authentication
#                       if (!www_authorize("iptel.org", "subscriber")) {
#                               www_challenge("iptel.org", "0");
#                               break;
#                       };
 
                        save("location");
                        break;
                };
 
                # attempt handoff to PSTN
                if (uri=~"^sip:[0-9]*@sip.mycompany.com") {
                        log(4, "Forwarding to PSTN\n");
                        forward(X.X.X.X,5060);
                        break;
                };
 
                # native SIP destinations are handled using our USRLOC DB
                if (!lookup("location")) {
                        sl_send_reply("404", "Not Found");
                        break;
                };
        };
        # forward to current uri now
        if (!t_relay()) {
                sl_reply_error();
        };
 
}
_____________________________________________________________________________
----- Original Message -----
From: Emil
To: Bo
Sent: Friday, March 14, 2003 5:43 PM
Subject: Re: [Serusers] SER log

Hi Bo,
 
Jan just helped me with a similar problem.
 
Debug level = 9 and fork t= no.
 
Tail /var/log messages and you will get plenty of info.
 
Emil
----- Original Message -----
From: Bo
To: serusers@lists.iptel.org
Sent: Saturday, March 15, 2003 12:35 AM
Subject: [Serusers] SER log

Hi,
 
Does anyone have any clue on the following problem?
 
I recompiled and installed SER in Redhat Linux 8.0. Unfortunately I tried all the possible options (debug level) in the ser.cfg, but the only messages I could see in the /var/log/messsages are as follows.
 
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is initially 65535
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is finally 262142
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is initially 65535
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is finally 262142
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is initially 65535
Mar 14 17:56:49 dda ser[15303]: INFO: udp_init: SO_RCVBUF is finally 262142
Mar 14 17:56:49 dda ser[15316]: INFO: fifo process starting: 15316
Mar 14 17:56:49 dda ser[15316]: SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
What should I do to see the detailed debugs?
 
Thanks,
 
Bo