(RADIATOR) Interim-Updates!

[Skeeve Stevens]

Sooooo.. if they are on a looong time, you can simply take the last
accounting record for that session id?
 
Hmmm..    I am trying to work out how the best deal with customers who
are on for LONG periods of times... weeks - perhaps months in the DSL
world.
 
Daily usage statistics start to get quite complicated in these cases....
any advice on how one would go about tabulating such data?   maybe
taking the last alive record for that day, and minusing the last alive
record for the previous day to get the data for that day?   damn that is
going to take some processing power :(
 
...Skeeve

-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of Hugh Irvine
Sent: Thursday, August 22, 2002 4:52 PM
To: skeeve at skeeve.org
Cc: radiator at open.com.au
Subject: Re: (RADIATOR) Interim-Updates!


Hello Skeeve -

The accounting counters start when a session starts on the NAS and the
accounting alive requests contain the value of the counters when the
request is sent (the values are *not* deltas). The accounting stop shows
the final values for each of the counters. Of course you should do some
testing to verify that your NAS does actually do the right thing (TM).

BTW - many operators simply use accounting stops only.

regards

Hugh


On Wednesday, August 21, 2002, at 10:24 PM, Skeeve Stevens wrote:



Hey Hugh,
 
    We are actually writing our own billing system.... and I am not
quite sure about these alive records.
 
Is the data these alive records a cumulative amount 'since' the start or
the previous alive record.... and... if there is a stop record, can that
simply be considered the last alive record?
 
...Skeeve


-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of Hugh Irvine
Sent: Wednesday, August 21, 2002 5:25 PM
To: Solomon Sokolovsky
Cc: radiator at open.com.au
Subject: Re: (RADIATOR) Interim-Updates!

Hello Solomon -

Radiator will automatically log Interim-Updates (radius accounting alive
requests), however you will need to use a billing system that
understands them to process them correctly. You will find a list of
billing systems we have tested against here:

http://www.open.com.au/radiator/technical.html#billing

regards

Hugh


On Tuesday, August 20, 2002, at 07:07 PM, Solomon Sokolovsky wrote:

Hi All,
 
We want to be able to use this for broadband customers which don't
disconnect for ages, and use
the Interim-Updates functions like what Cisco and Redback use.  But need
to be able to accumulate the usage and
understand it correct!  The Interim-Updates need to be accumulated in
relation to the start and stop packets.  Do you know of any billing
system, able to work with Radiator and understand Interim-Updates?  Is
it possible to have a script which can in the Radius which calculated
the required info and get it imported in to a billing package?
 
Thanks All!
Solomon


NB: I am travelling this week, so there may be delays in our
correspondence.

--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.





NB: I am travelling this week, so there may be delays in our
correspondence.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020826/3a2b40c4/attachment.html>