Hello all,
I am a student currently studying SIP with SER on a Slackware 10.2 system. I could have my test network working fine in proxy/registrar mode but I am having trouble in configuring SER for redirect mode. Actually I am totally new at SER administration and don't feel really comfortable in implementing code blocks into ser.cfg When I use the following ser.cfg file, SER simply ignore the redirect block and call alice at 192.168.1.2 whereas the call should be redirected to 192.168.1.4 I've been driftng all around the Internet gathering hints and tips for a few days but I'm still at that point. I guess it's a programming problem but can't find what's wrong exactly. Thank you in advance for your help.
Matthieu
Here is my uname -a result: Linux PC1 2.4.31 #6 Sun Jun 5 19:04:47 PDT 2005 i686 unknown unknown GNU/Linux
My SER build: version: ser 0.9.4 (i386/linux) flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, 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.197.2.1 2005/07/25 16:56:24 andrei Exp $ main.c compiled on 15:54:20 Sep 6 2005 with gcc 4.0.1
My ser.cfg file based upon default ser.cfg: # # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 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)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
listen=192.168.1.1
check_via=yes # (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" 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)
# 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 >= 2048 ) { 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; };
# redirect block, maybe at the wrong place if (uri=="sip:alice@192.168.1.2") { rewritehost("192.168.1.4"); sl_send_reply("302", "Redirect"); } }; 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(); }; }
_________________________________________________________________ Recherchez sur votre PC comme sur le Web avec Windows Desktop Search ! http://desktop.msn.fr/
I understand there are 2 kind of Linksys RT31p2. A NA version, and non NA version. Anybody knows what's the difference? I have a Linksys RT31 but I can't configure the "interdigit timer" and all other telephony related parameters.
I´d like to know what is the version which permits to configure all the telephony parameters? Do you know what is it?
Thanks in advance
Sebastian
RT31P2-NA is an unprovisioned version of the VoIP IAD. Meaning that you can customize it and it allows access to all of the config settings via the web interface.
RT31P2 is an IAD that has had firmware customized and burned for a particular VSP (ie. Vonage, AT&T, etc). It cannot be customized for another ISP without the original VSP unlocking the box for you.
It is my understanding that you must go through some sort of process to become an authorize VSP with Cisco/Linksys before you can buy the RT31P2-NA. You can't just pick one up at Best Buy...
Regards, Darren Nay
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Sebastian Milioto - INTERCOM Sent: Tuesday, November 15, 2005 10:32 AM To: serusers@lists.iptel.org Subject: [Serusers] Linksys RT31 NA??
I understand there are 2 kind of Linksys RT31p2. A NA version, and non NA version. Anybody knows what's the difference? I have a Linksys RT31 but I can't configure the "interdigit timer" and all other telephony related parameters.
I´d like to know what is the version which permits to configure all the telephony parameters? Do you know what is it?
Thanks in advance
Sebastian
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers