[Serusers] Re: Can you help me!

Hello, How are you! I'am glad to receiving your letter! I'd give my question information.I beg your help! Thank you very much! 1,operating system: my Redhat7.3 (Linux 2.4.18-3) 2,SER distribution: ser 0.8.11 (i386/linux) 3, SER configuration file : # $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ #debug=8 # debug level (cmd line: -dddddddddd) #fork=no #log_stderror=yes # (cmd line: -E) alias="Lserver.net" # Uncomment these lines to enter debugging mode debug=8 fork=no log_stderror=yes 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" loadmodule "/usr/lib/ser/modules/auth_db.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_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==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; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol record_route(); # loose-route processing if (loose_route()) { t_relay(); break; }; # 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==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("Lserver.sict.net", "subscriber")) { www_challenge("Lserver.sict.net", "0"); break; }; save("location"); 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; use stateful forwarding; that # works reliably even if we forward from TCP to UDP if (!t_relay()) { sl_reply_error(); }; } 4, SER logs : When I apply the following configuration options: debug=8, log_stderror=yes, fork=no. show this information: ..... 0(0) DEBUG: udp_init: trying SO_RCVBUF: 262140 0(0) DEBUG: setting SO_RCVBUF; set=262140,verify=131070 0(0) DEBUG: setting SO_RCVBUF has no effect 0(0) DEBUG: udp_init: trying SO_RCVBUF: 133118 0(0) DEBUG: setting SO_RCVBUF; set=133118,verify=131070 0(0) DEBUG: setting SO_RCVBUF has no effect 0(0) INFO: udp_init: SO_RCVBUF is finally 131070 0(0) WARNING: using only the first listen address (no fork) 1(4499) DBG: open_uac_fifo: opening fifo... 1(4499) DEBUG: fifo /tmp/ser_fifo opened, mode=438 0(4497) DEBUG: init_mod_child (1): tm 0(4497) DEBUG: callid: '763e7fde-4497(a)127.0.0.1' 0(4497) DEBUG: init_mod_child (1): usrloc 1(4499) DEBUG: init_mod_child (-1): tm 1(4499) DEBUG: callid: '763e7fde-4499(a)127.0.0.1' 1(4499) DEBUG: init_mod_child (-1): usrloc 2(4500) INFO: fifo process starting: 4500 2(4500) DEBUG: init_mod_child (-2): tm 2(4500) DEBUG: callid: '763e7fde-4500(a)127.0.0.1' 2(4500) DEBUG: init_mod_child (-2): usrloc 1(4499) DEBUG: init_mod_child (-1): auth_db 0(4497) DEBUG: init_mod_child (1): auth_db 2(4500) DEBUG: init_mod_child (-2): auth_db 2(4500) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... It's no longer running,always stop! why? My SER log is : .... Oct 7 13:30:05 Lserver ser: WARNING: could not rev. resolve 210.72.128.44 Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: Listening on Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 127.0.0.1 [127.0.0.1 ]:5060 Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 192.168.0.179 [192.1 68.0.179]:5060 Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 210.72.128.44 [210.7 2.128.44]:5060 Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: Aliases: Lserver.sict.net:5060 loc alhost:5060 localhost.localdomain:5060 Lserver:5060 Lserver.net:* Oct 7 13:30:06 Lserver 10月 7 13:30:05 ser: ser startup succeeded Oct 7 13:49:07 Lserver 10月 7 13:49:07 ser: ser shutdown failed Oct 7 13:50:42 Lserver ser: parse error (14,1-2): parse error Oct 7 13:50:42 Lserver ser: parse error (14,1-2): Oct 7 13:51:24 Lserver ser: WARNING: could not rev. resolve 210.72.128.44 [root@Lserver /]# ----- Original Message ----- From: "Daniel-Constantin Mierla" <Daniel-Constantin.Mierla(a)fokus.fraunhofer.de> To: "郝育鹏" <haoypeng(a)sict.ac.cn> Cc: <serusers(a)iptel.org> Sent: Monday, October 06, 2003 7:26 PM Subject: Re: [Serusers] Can you help me! Hello, did you add some users into database? Please follow the guidelines from http://www.iptel.org/ser/bugs/ and send us the result. We can't guess everything what happen into your system only from config file. You have commented some global parameters and that changed the behavior SER should have with default config file -- you even commented the number of children that means ser listens only on first network interface (I have to double check it, but it should be like that), and that is usually 127.0.0.1. We need the log messages, network dumps and so on ... Regards, "Daniel