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-----Hello Solomon -
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Hugh Irvine
Sent: Wednesday, August 21, 2002 5:25 PM
To: Solomon Sokolovsky
Cc: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Interim-Updates!
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.
