sr-users February 2005

sr-users@lists.kamailio.org

215 participants
467 discussions

Re: Re: [Serusers] ser dead but subsys locked

by info＠beeplove.com

See this, [root@croaker admin]# ser -f /etc/ser/ser.cfg -c -ddd &> ser.log [root@croaker admin]# vim ser.log ## I have removed few lines from ser.log that seems unimportant. [root@croaker admin]# cat ser.log 0(26776) read 4076494534 from /dev/random 0(26776) seeding PRNG with 889008826 0(26776) test random number 1332590677 0(26776) shm_mem_init: success 0(26776) DEBUG: register_fifo_cmd: new command (print) registered 0(26776) DEBUG: register_fifo_cmd: new command (uptime) registered 0(26776) DEBUG: register_fifo_cmd: new command (version) registered 0(26776) DEBUG: register_fifo_cmd: new command (pwd) registered 0(26776) DEBUG: register_fifo_cmd: new command (arg) registered 0(26776) DEBUG: register_fifo_cmd: new command (which) registered 0(26776) DEBUG: register_fifo_cmd: new command (ps) registered 0(26776) DEBUG: register_fifo_cmd: new command (kill) registered 0(26776) loading module //lib/ser/modules/mysql.so 0(26776) loading module /lib/ser/modules/sl.so 0(26776) loading module /lib/ser/modules/tm.so 0(26776) loading module /lib/ser/modules/rr.so 0(26776) loading module /lib/ser/modules/maxfwd.so 0(26776) loading module /lib/ser/modules/usrloc.so 0(26776) loading module /lib/ser/modules/registrar.so 0(26776) loading module /lib/ser/modules/auth.so 0(26776) loading module /lib/ser/modules/auth_db.so 0(26776) set_mod_param_regex: usrloc matches module usrloc 0(26776) set_mod_param_regex: found <db_mode> in module usrloc [/lib/ser/modules/usrloc.so] 0(26776) set_mod_param_regex: auth_db matches module auth_db 0(26776) set_mod_param_regex: found <calculate_ha1> in module auth_db [/lib/ser/modules/auth_db.so] 0(26776) set_mod_param_regex: auth_db matches module auth_db 0(26776) set_mod_param_regex: found <password_column> in module auth_db [/lib/ser/modules/auth_db.so] 0(26776) find_export: found <mf_process_maxfwd_header> in module maxfwd_module [/lib/ser/modules/maxfwd.so] 0(26776) find_export: found <sl_send_reply> in module sl_module [/lib/ser/modules/sl.so] 0(26776) find_export: found <sl_send_reply> in module sl_module [/lib/ser/modules/sl.so] 0(26776) find_export: found <record_route> in module rr [/lib/ser/modules/rr.so] 0(26776) find_export: found <loose_route> in module rr [/lib/ser/modules/rr.so] 0(26776) find_export: found <t_relay> in module tm [/lib/ser/modules/tm.so] 0(26776) find_export: found <save> in module registrar [/lib/ser/modules/registrar.so] 0(26776) find_export: found <lookup> in module registrar [/lib/ser/modules/registrar.so] 0(26776) find_export: found <sl_send_reply> in module sl_module [/lib/ser/modules/sl.so] 0(26776) find_export: found <t_relay> in module tm [/lib/ser/modules/tm.so] 0(26776) find_export: found <sl_reply_error> in module sl_module [/lib/ser/modules/sl.so] 0(26776) routing table 0: 0(26776) WARNING: could not rev. resolve 192.168.71.3 config file ok, exiting... 0(26776) DEBUG: tm_shutdown : start 0(26776) DEBUG: tm_shutdown : empting hash table 0(26776) DEBUG: tm_shutdown: releasing timers 0(26776) DEBUG: tm_shutdown : removing semaphores 0(26776) DEBUG: tm_shutdown : done 0(26776) shm_mem_destroy 0(26776) destroying the shared memory lock Listening on 127.0.0.1 [127.0.0.1]:5060 192.168.71.3 [192.168.71.3]:5060 Aliases: localhost:5060 localhost.localdomain:5060 croaker:5060 [root@croaker admin]# cat /etc/ser/ser.cfg # # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ #debug=3 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E) /* Uncomment these lines to enter debugging mode debug=7 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 "//lib/ser/modules/mysql.so" loadmodule "/lib/ser/modules/sl.so" loadmodule "/lib/ser/modules/tm.so" loadmodule "/lib/ser/modules/rr.so" loadmodule "/lib/ser/modules/maxfwd.so" loadmodule "/lib/ser/modules/usrloc.so" loadmodule "/lib/ser/modules/registrar.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/lib/ser/modules/auth.so" loadmodule "/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 ( msg:len > 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("iptel.org", "subscriber")) { # www_challenge("iptel.org", "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(); }; } Help .. please Mohammad Evan Borgstrom <evan.borgstrom(a)ca.mci.com> wrote on 02/03/2005, 07:08:58 PM: > This means that ser has crashed... most likely a bad config file. > Try running: ser -c > > That will test your config file, you can also try ser -c -d for more > debugging info. > > -Evan > > On Thu, 2005-02-03 at 19:06 +0100, info(a)beeplove.com wrote: > > Hello List: > > > > I have able to to compile ser from source. > > I also have setup ser database. > > > > My problem is: > > > > ############################ > > [root@croaker ~]# service ser start > > [ OK ] > > [root@croaker ~]# service ser status > > ser dead but subsys locked > > ############################## > > > > This issue might have discussed before, but I was not able to find > > *Search* in archive. > > Would anybody please send me link to search in the archive. > > > > Thanks > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers -- Mohammad Khan

19 years, 3 months

[Serusers] Rewriting Record-Route headers

by Evan Borgstrom

Hey all, I've implemented re-writing of URI's based on 7 & 10 digit numbers fine in SER but the problem is that our gateway that connects us to the PSTN lines is doing verification on the Record-Route headers. So when I rewrite 5551212 into 12345551212 the INVITE message shows the following and the PSTN gateway returns a 404 not found because it cant forward 5551212 to the PSTN. INVITE sip:12345551212@1.1.1.4:5060 SIP/2.0. Record-Route: <sip:5551212@1.1.1.2;ftag=4b2deae9ab74b4ebo0;lr=on>. Is there anyway to rewrite the Record-Route part of the headers? -Evan

19 years, 3 months

[Serusers] ser dead but subsys locked

by info＠beeplove.com

Hello List: I have able to to compile ser from source. I also have setup ser database. My problem is: ############################ [root@croaker ~]# service ser start [ OK ] [root@croaker ~]# service ser status ser dead but subsys locked ############################## This issue might have discussed before, but I was not able to find *Search* in archive. Would anybody please send me link to search in the archive. Thanks -- Mohammad Khan

19 years, 3 months

[Serusers] Error :WebGlimpse Search

by info＠beeplove.com

I was doing a search on this link: http://www.iptel.org/webglimpse/ After clicking the 'submit', I was forwarded to this page: http://www.iptel.org/cgi-bin/webglimpse/home/www/wg2?query=ser+dead+but+sub… which says, -- Glimpse Archive Configuration File not found Cannot open configuration file /home/www/wg2/archive.cfg Thanks, Mohammad Khan

19 years, 3 months

Re: Re: [Serusers] Trying to install ser-0.8.14 from source

by info＠beeplove.com

Andrea Federico <andreafederico(a)mail.com> wrote on 02/03/2005, 04:34:39 PM: > if you have problem first of all you must > look in to the past seruser mail !!!! > > http://www.archivum.info/serusers%40iptel.org/2004-11/msg00515.html > Yes, I should search in the archive first!! Thank anyway, for sending the link and clearify this. Mohammad > > > > > > Nobody replied me! > > :-(( > > > > MOhammad > > > > > > > > > > info(a)beeplove.com wrote on 02/01/2005, 11:26:01 PM: > > > > > > Hello List: > > > I am trying to install ser-0.8.14 from source. > > > > > > I ran make and got the lines below: > > > > > > Makefile.rules:77: action.d: No such file or directory > > > Makefile.rules:77: crc.d: No such file or directory > > > Makefile.rules:77: data_lump.d: No such file or directory > > > Makefile.rules:77: data_lump_rpl.d: No such file or directory > > > Makefile.rules:77: dprint.d: No such file or directory > > > Makefile.rules:77: dset.d: No such file or directory > > > Makefile.rules:77: error.d: No such file or directory > > > Makefile.rules:77: fifo_server.d: No such file or directory > > > Makefile.rules:77: flags.d: No such file or directory > > > Makefile.rules:77: forward.d: No such file or directory > > > > > > Any idea, how to fix it. > > > > > > Thanks, > > > > > > -- Mohammad Khan > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > -- > > Mohammad Khan > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > -- > ___________________________________________________________ > Sign-up for Ads Free at Mail.com > http://promo.mail.com/adsfreejump.htm -- Mohammad Khan

19 years, 3 months

[Serusers] Radius Auth WITHOUT Domain?

by Arnd Vehling

Hi, we have a customer whose radius server is not able to auth a <userid>@<realm> scheme required by the auth_radius module. Does anyone know if its possible to do a www and proxy auth via radius without sending the domain/realm part? If i call www_radius_auth with an empy ("") realm the module extracts the domain from the current uri. Is it possible to surpress this? regards, Arnd

19 years, 3 months

[Serusers] Rewriting URI domain part

by Luca Corti

Hello, I'm forwarding calls to a PSTN gateway. If I call a numeric number from a client the default domain is @mydomain. I'd like it to become @pstn (or any string) so that the clients can call pstn numbers without entering a domain suffix. thanks Luca

19 years, 3 months

[Serusers] Loose Routing ramifications

by justiceguy＠pobox.com

Hello list, I am new to SER and trying to understand the ramifications and downsides of SIP Loose Routing versus Strict. I have read RFC3261 and some net documentation, but I'm still having trouble seeing the big picture. In particular, we are testing a SIP route to an ITSP, and they have specified to us "no SIP loose routing". I'm trying to understand, why do providers do this? What is the downside? What are Industry Best Practices? We have some downstream customers that might be connecting Asterisk IAX to us, and then we will be routing these calls via SIP to the ITSP provider. It seems to me that there might be ramifications for loose versus strict routing in how we process these calls. Can anyone with SIP routing experience explain best practices or Advantages/Disadvantages, or point me to a link? I found a document that explains the 'problem' with Strict routing: Strict routing (Route/Record-Route as defined in bis-05 and before) was too strict. Service logic could not affect routing of the initial request. * Strict routing conflates the request target with the next hop destination. * Strict route processing throws away the information in the received Request-URI. * Behavior of UAs with default-outbound-proxies problematic. * Brittle system failure if any element misroutes. TIA, Jason Ostrom

19 years, 3 months

Re: [Serusers] Trying to install ser-0.8.14 from source

by info＠beeplove.com

Nobody replied me! :-(( MOhammad info(a)beeplove.com wrote on 02/01/2005, 11:26:01 PM: > > Hello List: > I am trying to install ser-0.8.14 from source. > > I ran make and got the lines below: > > Makefile.rules:77: action.d: No such file or directory > Makefile.rules:77: crc.d: No such file or directory > Makefile.rules:77: data_lump.d: No such file or directory > Makefile.rules:77: data_lump_rpl.d: No such file or directory > Makefile.rules:77: dprint.d: No such file or directory > Makefile.rules:77: dset.d: No such file or directory > Makefile.rules:77: error.d: No such file or directory > Makefile.rules:77: fifo_server.d: No such file or directory > Makefile.rules:77: flags.d: No such file or directory > Makefile.rules:77: forward.d: No such file or directory > > Any idea, how to fix it. > > Thanks, > > -- > Mohammad Khan > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers -- Mohammad Khan

19 years, 3 months

[Serusers] route to another sip server (newbie question)

by Ozan Blotter

i've checked so many examples and read but not yet find any clear one with real examples for routing calls to another sip server. config as follow: UA 1 : NAT : ROUTER A > INTERNET (SIP SER) INTERNET < ROUTER B : NAT : UA 2 (for now i'm testing on LAN but soon i'll place SER on a Public IP) and there's another sipserver at 212.XXX.32.YYY which we use as gateway, it connects all calls to PSTN. It's capable of doing billing,radius auth,sybase etc, all in one solution. i want to give users numbers like 833XXXXXXX (prepaid) and 834XXXXXXX (postpaid) i create users with dialupadmin, it registers, they can call each other there's no problem but when i try to add some prefix routing it does not register or call, i am not familiar with linux but can do some. what i need is i want to route all calls except beginning with 833 or 834 prefix to be routed to 212.XXX.32.YYY and if possible not to use SER's bandwidth. how can i ? thanks below is my ser.cfg # # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ #debug=7 #debug=3 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E) /* Uncomment these lines to enter debugging mode debug=7 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/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" # 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" loadmodule "/usr/local/lib/ser/modules/auth_radius.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 ( msg:len > 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("", "subscriber")) { # www_challenge("", "0"); # break; # }; if (!radius_www_authorize("")) { www_challenge("", "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(); }; } -- >>> please do not use >>> l.s.d(a)dnaofdesign.com >>> above account is stand by >>> use same account as >>> cosmocid(a)ispro.net.tr

19 years, 3 months

← Newer
1
...
40
41
42
43
44
45
46
47
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users February 2005