[Serusers] ser/radius accounting not happening
Jan Janak
jan at iptel.org
Thu Jan 22 00:59:56 CET 2004
Send me all columns, please.
Jan.
On 21-01 08:50, Madan wrote:
>
> here is the radacct table which records the accounting, let me know if you
> need other details
>
>
> +---------------------+---------------------+
> | AcctStartTime | AcctStopTime |
> +---------------------+---------------------+
>
> 2004-01-19 18:11:48 | 0000-00-00 00:00:00 |
> | 2004-01-19 18:11:48 | 0000-00-00 00:00:00 |
> | 2004-01-19 18:12:01 | 2004-01-19 18:12:01 |
> | 2004-01-19 18:12:19 | 2004-01-19 18:12:19 |
> | 2004-01-20 18:43:14 | 0000-00-00 00:00:00 |
> | 2004-01-20 18:43:15 | 0000-00-00 00:00:00 |
> | 2004-01-20 18:43:53 | 2004-01-20 18:43:53 |
>
>
> ----- Original Message -----
> From: "Jan Janak" <jan at iptel.org>
> To: "Madan" <madan.r at net4india.net>
> Cc: <serusers at lists.iptel.org>
> Sent: Tuesday, January 20, 2004 9:18 PM
> Subject: Re: [Serusers] ser/radius accounting not happening
>
>
> > Could you post some examples of start and stop records with the same
> > time ?
> >
> > Jan.
> >
> > On 17-01 08:35, Madan wrote:
> > > Hi List,
> > > I 'am facing a problem with ser/radius configuration which is working
> fine except for the accounting part. In freeradius accounting details I see
> that both start and stop time is same, can somebody help me on how to fix
> this.
> > >
> > > here is my ser.cfg
> > >
> > > #
> > > # ----------- global configuration parameters ------------------------
> > > debug=9 # debug level (cmd line: -dddddddddd)
> > > fork=no
> > > log_stderror=yes # (cmd line: -E)
> > > listen=10.0.0.1
> > > /* 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"
> > > loadmodule "/usr/local/lib/ser/modules/uri.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"
> > > loadmodule "/usr/local/lib/ser/modules/auth_radius.so"
> > > loadmodule "/usr/local/lib/ser/modules/group_radius.so"
> > >
> > >
> > > # ----------------- setting module-specific parameters ---------------
> > >
> > > # -- usrloc params --
> > >
> > > modparam("usrloc", "db_mode", 2)
> > > modparam("auth_radius",
> "radius_config","/usr/local/etc/radiusclient/radiusclient.conf")
> > > #modparam("auth_radius", "service_type", 15)
> > >
> > > # -- rr params --
> > > # add value to ;lr param to make some broken UAs happy
> > > modparam("rr", "enable_full_lr", 1)
> > > modparam("acc", "log_level", 1)
> > > modparam("acc", "radius_flag", 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
> > > record_route();
> > > # loose-route processing
> > > # t_relay();
> > > # break;
> > > # };
> > >
> > > if (loose_route()) {
> > >
> > > if (method=="BYE" || method=="CANCEL") {
> > > log (1, "BYE or CANCEL\n");
> > > setflag(1);
> > > };
> > >
> > >
> > > 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 (method=="REGISTER") {
> > >
> > > log(1, "REGISTER: Authenticating user\n");
> > >
> > > if (!radius_www_authorize("")) {
> > > log(1, "REGISTER: challenging user\n");
> > > www_challenge("", "0");
> > > break;
> > > };
> > > save("location");
> > > break;
> > > };
> > >
> > >
> ############################################################################
> ##############################
> > > if (uri=~"^sip:44[127][0-9]+ at .*$")
> > > {
> > >
> > > if (rewritehostport("10.0.0.8:5060"))
> > > {
> > > if (!t_relay())
> > > {
> > > sl_reply_error();
> > > };
> > >
> > > }
> > > else
> > > {
> > > sl_reply_error ();
> > > };
> > > break;
> > >
> > > }
> > > else if (method=="INVITE")
> > > {
> > > sl_send_reply("403", "Call cannot be served here");
> > >
> > > };
> > >
> > >
> > > # account completed transactions via syslog
> > > setflag(1);
> > >
> > >
> > >
> ############################################################################
> ###################################
> > > if (method=="INVITE") {
> > >
> > > log(1, "INVITE\n");
> > > setflag(1); /* set for accounting (the same value as in
> > > log_flag!) */
> > > };
> > >
> > > if (method=="MESSAGE") {
> > > log(1, "MESSAGE\n");
> > > setflag(1); /* set for accounting (the same value as in
> > > log_flag!) */
> > > };
> > >
> > > if (method=="BYE" || method=="CANCEL") {
> > > log (1, "BYE or CANCEL\n");
> > > setflag(1);
> > > };
> > >
> > > # native SIP destinations are handled using our USRLOC DB
> > > if (!lookup("location")) {
> > > sl_send_reply("404", "Not Found");
> > > break;
> > > };
> > > if (!t_relay()) {
> > > sl_reply_error();
> > > break;
> > > };
> > >
> > >
> > > }
> > >
> > >
> >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers at lists.iptel.org
> > > http://lists.iptel.org/mailman/listinfo/serusers
> >
> >
>
More information about the sr-users
mailing list