I know we could do some other ways like run a scheduled procedure to scan
the subaccounts every night and switch the expired user to other service
type. But that is too much of the challenge for the staff, they will have to
remember to schedule the procedure every time they change the server or move
Emerald to other server, or when they recover server from backup.
Even better, if Emerald has a interface to specify when the particular
service type expired, the different type of service user will be allowed to
connect to. I know that going to create problem for accounting because the
CALLS table does not record service type that user connect to. May be add
this field to CALLS table will speed up Calls Consolidation process quiet a
lot as well?
>and then modify the RadConfigs proc to return the alternate set if the user
I check the DB, there are two store proc RadGetATConfigs & RadGetConfigs, I
am using RadiusNT 2.5 & Emerald 2.1.1. Which one is the proc you talk about
on the above, RadGetConfigs? Because this one take the parameter @AccountID
which is the SubAccountID that user is using to login?
For more information about this list, including removal,
please see http://www.iea-software.com/maillist.html