At 14:39 13/10/2004, Evgeny Ivanov wrote:

Anyone using *BSD and SER ?

Yes, our SER servers run on FreeBSD quite nicely.

peter

Hi

I have finally manged to get the acc.so module up and running, it no logs in fine, and I can get Xlite (the UA I am using) to REGISTER and login, and I can see new user logged in details in the connection table in the SER database...but acc table is empty.

I copied the default accounting example, and pasted it into my config below. All the auth etc with db works, but when I initiate a call, I see the INVITE flags being sent to my console, hence I figure the ser.cfg file should picmk these up and send to acc table in DB...but alas table is empty, neideas

- # # $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=9 # 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=no */

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" loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so" loadmodule "/usr/local/lib/ser/modules/acc.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) #modparam("auth_radius", "radius_config", "/usr/local/etc/radiusclient/radiusclient.conf") # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) #

modparam("auth_db", "db_url", "mysql://ser:pass@server.com/ser") modparam("usrloc", "db_url", "mysql://ser:pass@server.com/ser") modparam("acc", "db_url", "mysql://ser:pass@server.com/ser")

#modparam("group", "db_url", "mysql://ser:pass@server.com/ser") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)

# ----------------- Accounting Parameters ---------------

# set the reporting log level # #modparam("acc", "log_level", 1) # number of flag, which will be used for accounting; if a message is # labeled with this flag, its completion status will be reported modparam("acc", "db_flag", 1) modparam("acc", "log_level", 2) modparam("acc", "db_missed_flag", 1) modparam("acc", "failed_transactions", 1)

# ----------------- setting module-specific parameters ---------------

# ------------------------- request routing logic -------------------

# main routing logic

route{

/* ********* ROUTINE CHECKS ********************************** */

if( (method=="INVITE") || (method=="ACK") || (method=="BYE") || (method=="REGISTER")) { setflag(1); }

# filter too old messages if (!mf_process_maxfwd_header("10")) { log("LOG: Too many hops\n"); sl_send_reply("483","Too Many Hops"); break; };

if ( msg:len > max_len ) { sl_send_reply("513", "Message too big"); break; };

# Process record-routing if (loose_route()) { t_relay(); break; };

# labeled all transaction for accounting setflag(1);

# record-route INVITES to make sure BYEs will visit our server too if (method=="INVITE") record_route();

# forward the request statefuly now; (we need *stateful* forwarding, # because the stateful mode correlates requests with replies and # drops retranmissions; otherwise, we would have to report on # every single message received) if (!t_relay()) { sl_reply_error(); break; };

}

tks

Iqbal

you need first to create a transaction to get the accounting information, you have loaded the tm module but you don't use any of its methods for relaying the request or replying to a request. The acc data is stored when the transaction completes, due to some tm callback functions. As a start point, see the tm and acc module documentation or the sample config for accounting (sip_router/examples/acc.cfg).

Daniel

On 10/13/04 22:11, Iqbal wrote:

Hi

After having tried mysql accounting, I dropped it and recompiled acc.so to support radius, well again it all logs in successfully, and authenticates the user with the user in the radius database.

BUT once again when I try to send accouting packets it fails, I have checked all the docs, set the setflag command etc etc, and my config is below...but I still see no errors on ser debug or even in mysql.

---

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/mysql.so" loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/acc.so" loadmodule "/usr/local/lib/ser/modules/auth_radius.so"

modparam("rr", "enable_full_lr", 1) modparam("acc","log_level",1) modparam("auth_radius","radius_config","/usr/local/etc/radiusclient/radiusclient.conf") modparam("auth_radius","service_type",15) modparam("acc", "db_url", "mysql://ser_usr:p1cK0@193.218.160.14/ser") modparam("acc", "service_type", 15) modparam("acc", "radius_flag", 1) modparam("acc", "radius_missed_flag", 3)

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; }; record_route();

if (method=="INVITE" || method=="BYE" || method=="CANCEL") { setflag(1); };

#Authorise via radius

           if (method=="REGISTER") {


            if (!radius_www_authorize("")) {
                           www_challenge("", "1");
                   };

                   save("location");
                   break;
           };

}

---

Now this seems to be the simplest config I can have, the UA authenticates fine, when I dial a number, I see the invite message appearing in the debug logs of SER

---

12(10813) SIP Request: 12(10813) method: <INVITE> 12(10813) uri: sip:3333333@server.com 12(10813) version: <SIP/2.0> 12(10813) parse_headers: flags=1 12(10813) Found param type 235, <rport> = <n/a>; state=6 12(10813) Found param type 232, <branch> = <z9hG4bK7991809E736B4750A6A288DC25D3FFD4>; state=16 12(10813) end of header reached, state=5 12(10813) parse_headers: Via found, flags=1 12(10813) parse_headers: this is the first via 12(10813) After parse_msg... 12(10813) preparing to run routing scripts... 12(10813) DEBUG : is_maxfwd_present: searching for max_forwards header 12(10813) parse_headers: flags=128 12(10813) end of header reached, state=9 12(10813) DEBUG: get_hdr_field: <To> [34]; uri=[sip:3333333@server.com] 12(10813) DEBUG: to body [sip:3333333@server.com

---

hence I figure that th INVITE tag should get recognised and using the setflag(1) parameter and radius_flag section, it should all work...but it dont :-(...help

Iqbal

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers