[freeside] Radius Check Items

[Kenny Elliott]

> >   I need to add the ability to add radius check items to a service
> > definition. Currently if I add additional radius items to
> the svc_acct
> > and part_svc (I don't need to add them anywhere else
> right) they will
> > be treated as Radius reply items only. Adding check items
> allows me to
> > support NAS-Port-Type and ICRadius' Simultaneous-Login.
> The best I've
> > come up with so far is to add 'radiuscheck_' fields to
> the database
> > and supporting scripts. Do you see any problems with this?
>
> That should work for now - though I'd ask that you use
> something no longer
> than `radius_' - maybe `rcheck_' ?  The problem is the
> resultant fields
> in part_svc:
>
> svc_acct__radius_Attribute_flag
>
> which already overflow PostgreSQL default of 31 characters
> for some RADIUS
> attributes.  Come to think of it, it might be better to use
> something as
> short as possible - `rc_' ?

Any prefix would work really. I would suggest though that the radius_
fields be renamed to follow along with the new fields. rr_ and rc_
perhaps
or maybe radrep_ and radchk_.

> > Are there
> > any reasons  you would not like to do it this way and
> perhaps do it
> > another.
>
> Longer-term, I need to do something about the length of the
> column names -
> The SQL1992 standard defines 18 character column names,
> which would be a
> reasonable goal.

Maybe the thing to do would be to separate these out to separate
tables.
then we could simply use something like id, attrib_name, attrib_value
to
store all of the radius values. It could be two separate tables or one
with
a field to indicate weather it's a check or reply field.

> >   I also noticed in the TODO file that Tim Jung was
> looking for a way
> > to support pre-paid cards. I'm ccing this to him so he
> will see it but
> > I wanted to mention for those who did not know that
> ICRadius supports
> > Monthly-Time-Limit and Total-Time-Limit attributes. This
> probably will
> > not solve all of the issues related to pre-paid cards but
> way assist
> > in that effort.
>
> There's support for pre-paid cards via dollar amount - see
> the end of
> htdocs/docs/signup.html.
>
> There isn't any support for time tracking yet, although I
> have specced out
> a RADIUS monitoring system which would provide this functionality.

Yes, that's what I was getting at. With ICRadius at least you could
create
a Total-Time-Limit attribute and set that to the time on the card.
There would
need to be a way to put the time into that field depending on what the
time
limit for that card was at account creation. There would also need to
be a way
for the customer to buy more time via something like the signup
server.