Re: [Serusers] Problem with TM initialialization

Guys, It’s stange, because I guess this module doesn’t depend on anyone else. Am I wrong? I’m trying to run it in a i686 kernel. May this be the problem? version: ser 0.8.11-r1 (i386/linux) flags: STATS:Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 @(#) $Id: main.c,v 1.1 2006/11/22 15:56:27 malmeida Exp $ main.c compiled on 06:45:02 Aug  3 2007 with gcc-3.3 3.3 nocserver:/tools/ciscoenvcontrol# uname -a Linux nocserver 2.6.15-23-686 #1 SMP PREEMPT Tue May 23 14:03:07 UTC 2006 i686 GNU/Linux The ser.cfg file is the default, as you can see bellow: # ----------- global configuration parameters ------------------------ debug=10         # debug level (cmd line: -dddddddddd) 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" listen=200.231.193.7 # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database #loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/ser/modules/auth.so" #loadmodule "/usr/local/lib/ser/modules/auth_db.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- modparam("usrloc", "db_mode",   0) # -- 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         if (!method=="REGISTER") record_route();         # subsequent messages withing a dialog should take the         # path determined by record-routing         if (loose_route()) {                 # mark routing logic in request                 append_hf("P-hint: rr-enforced\r\n");                 route(1);                 break;         };         if (!uri==myself) {                 # mark routing logic in request                 append_hf("P-hint: outbound\r\n");                 route(1);                 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("iptel.org", "subscriber")) { #                               www_challenge("iptel.org", "0"); #                               break; #                       };                         save("location");                         break;                 };                 lookup("aliases");                 if (!uri==myself) {                         append_hf("P-hint: outbound alias\r\n");                         route(1);                         break;                 };                 # native SIP destinations are handled using our USRLOC DB                 if (!lookup("location")) {                         sl_send_reply("404", "Not Found");                         break;                 };         };         append_hf("P-hint: usrloc applied\r\n");         route(1); } route[1] {         # send it out now; use stateful forwarding as it works reliably         # even for UDP2TCP         if (!t_relay()) {                 sl_reply_error();         }; } Thanks in advance! Fernando ________________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Fernando Schmitt Sent: Friday, August 03, 2007 9:17 PM To: serusers(a)lists.iptel.org Subject: [Serusers] Problem with TM initialialization Guys, I’m receiving the following output when running ser: 0(5705) Aug 03 06:58:26 DEBUG: register_fifo_cmd: new command (sl_stats) registered  0(5705) Aug 03 06:58:26 DEBUG: MD5 calculated: 103d8e7e9fc1a3538c1143a96b22bab4  0(5705) Aug 03 06:58:26 DEBUG: init_mod: tm  0(5705) Aug 03 06:58:26 TM - initializing...  0(5705) Aug 03 06:58:26 Call-ID initialization: '79dff3eb'  0(5705) Aug 03 06:58:26 DEBUG: register_fifo_cmd: new command (t_uac_dlg) registered  0(5705) Aug 03 06:58:26 DEBUG: register_fifo_cmd: new command (t_hash) registered  0(5705) Aug 03 06:58:26 DEBUG: lock_initialize: lock initialization started  0(5705) Aug 03 06:58:26 init_mod(): Error while initializing module tm ERROR: error while initializing modules Do you know why? Thanks!