[RADIATOR] Prepaid Card solution.

[Heikki Vatiainen]

On 01/18/2012 09:27 AM, Purevbat. Ya wrote:

Hello,

> First I’ll try to describe our billing & Radius server’s current status.
> 
> When customer made their payment we’re setting one month access
> permission on AAA server like: 2012.Jan.18 – 2012.Feb.18
> 
> This customer access will expire Feb 18^th even customer didn’t even
> logged first 10 days.
> 
> What we would like to do is:

This is possible with Radiator. For a simple prepaid case, please look
at file goodies/prepaid.cfg  As you can see, this example uses SQL
database which is updated by different RADIUS requests.

For more complex cases, such as what you are planning, the functionality
can be implemented with user defined Hooks that run during
authentication process.

For example: once password authentication is successful, a hook called
PostAuthHook is run. The hook can then access the prepaid SQL database
and update the information based on the rules you specified.

For more information about the hooks, see the reference manual ref.pdf
and goodies/hooks.txt file in the Radiator distribution.

These kinds of hooks have been built but as in your case, they are not
generic but depend on e.g, database, what information is required and
available about users, authentiation process and other case by case
requirements.

So in summary, what your require looks possible. I do know these kinds
of time based quotas have been implemented for e.g. Wi-Fi guest access
purposes.

Thanks!
Heikki


> When customer made their payment we should set two date ranges.
> 
> 1.       2012.Jan.18 – 2012.July.18 this range’s meaning is when
> customer didn’t used his/her modem.
> 
> 2.       A. Add 30 days to customer’s account. Expire date should be +30
> days since customer first used his account. Ex: Payment made on Jan
> 18^th but customer 1^st used his/her account on Jan 23th. In this case
> expire date should be Feb 23th.
> 
> B. is there any options that 30 days are decrease only when only when
> customer logged or not on that day. Ex: Jan18th 30 days remaining.
> Customer logged on Jan 21th, Jan 22th, 23th and 28th. On Jan 30^th
> Remaining Day: 26 Days left. (because 4 days used.)
> 
> (In this case we didn’t mentioned about data volume. J please consider
> like data volume not reached to 0)
> 
> We would like to use Prepaid card, prepaid card works like mentioned above.
> 
> Is it possible?
> 
> We’ll looking forward to hear from you soon.
> 
> Tnx.
> 
>  
> 
>  
> 
> Хүндэтгэсэн,
> 
> Я.Пүрэвбат
> 
>  
> 
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.