Re: How to charge based on accounting correctly

Hello Alan, Why not just update the users credit when the session is closed? Good question. The short answer is to charge as soon as possible. Store the last session length for a session. If the current packet has a smaller session length, ignore the packet. Otherwise, look at the

Re: How to charge based on accounting correctly

George Chelidze wrote: How much time can it keep the data? I don't think it's a good idea to resend the data after several hours. That's what the RFC says to do. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

How to charge based on accounting correctly

Hello, We have a system which sends radius accounting messages to our radius. Based on this accounting we charge subscribers. Interim accounting is enabled so for a normal session we get one Start, zero or more Interim-Update and one Stop packets. Every accounting packet except Start

Re: How to charge based on accounting correctly

George Chelidze wrote: To charge a session in chunks we calculate a difference between the recent value and the previous one. Why not just update the users credit when the session is closed? In our case we get Interim-Update records every 15 minutes, No. You *hope* to get them every 15