SER example accounting

SIP Express Router

example: accounting calls to numerical destinations


  1. $Id: acc.cfg,v 1.3 2003/06/03 03:18:12 jiri Exp $

  1. ------------------ module loading ----------------------------------

loadmodule "modules/tm/tm.so"
loadmodule "modules/acc/acc.so"
loadmodule "modules/sl/sl.so"
loadmodule "modules/maxfwd/maxfwd.so"
loadmodule "modules/rr/rr.so"

  1. ----------------- setting module-specific parameters ---------------

  1. — acc params --
  2. set the reporting log level
modparam("acc", "log_level", 1)
  1. number of flag, which will be used for accounting; if a message is
  2. labeled with this flag, its completion status will be reported
modparam("acc", "log_flag", 1 )

  1. ------------------------- request routing logic -------------------

  1. main routing logic

route{

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

  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 (len_gt( max_len )) {
sl_send_reply("513", "Wow — Message too large");
break;
};

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


  1. labeled all transaction for accounting
setflag(1);

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

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

}

See also



Back to SER tips and tricks

SIP Express Router

example: accounting calls to numerical destinations


  1. $Id: acc.cfg,v 1.3 2003/06/03 03:18:12 jiri Exp $

  1. ------------------ module loading ----------------------------------

loadmodule "modules/tm/tm.so"
loadmodule "modules/acc/acc.so"
loadmodule "modules/sl/sl.so"
loadmodule "modules/maxfwd/maxfwd.so"
loadmodule "modules/rr/rr.so"

  1. ----------------- setting module-specific parameters ---------------

  1. — acc params --
  2. set the reporting log level
modparam("acc", "log_level", 1)
  1. number of flag, which will be used for accounting; if a message is
  2. labeled with this flag, its completion status will be reported
modparam("acc", "log_flag", 1 )

  1. ------------------------- request routing logic -------------------

  1. main routing logic

route{

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

  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 (len_gt( max_len )) {
sl_send_reply("513", "Wow — Message too large");
break;
};

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


  1. labeled all transaction for accounting
setflag(1);

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

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

}

See also



Back to SER tips and tricks

Created by: oej, Last modification: Fri 19 of Sep, 2003 (19:43 UTC)
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+