> On Fri, 20 Dec 1996, Pete Kruckenberg wrote:
> > Another cool feature (which may already exist) would be to allow call-back
> > to the (varying) caller ID number, in addition to the fixed call-back
> > number. I guess this would be more of a RADIUS server feature?
>
> What I could /really/ use is the ability for the PM3 to grab the
> caller-ID info, check a list of local prefixes, and only answer
> if it's a local call. If the caller-ID info is non-local, a
> call-back could be initiated (checks a list of allowed call-back
> prefixes).
While your application is fairly specific, I think that there will be a
lot of ISPs who will be setting up most or all of their ISDN customers on
a call-back type of thing. The call-back will save the customer a lot of
money (because they can buy a fully-measured ISDN line, which is cheaper),
while not costing the ISP anything extra (assuming that the ISP is using
flat-rate PRI or BRI service).
Looking through the RADIUS docs, I notice that a PPP (Framed) callback
session requires a Location parameter, rather than just a phone number
(like the Callback-Login does). I guess this is so for some potential
security reason? So, even if the RADIUS server was equiped to handle
dynamic call-back using the Calling-ID, the PM isn't able to.
Requiring the Location as the Callback-Framed parameter, instead of a
phone number, introduces a huge management issue. Now, when a new
call-back customer is set up, I have to add them to my user management
system, and also add a Location to each PM they might hit. That's a lot of
work. I would really prefer to keep the security and all user-related
information in the RADIUS server. That would also allow for a modified
RADIUS server that would support fully dynamic call-backs, based on
either a fixed number or the calling-id.
Pete Kruckenberg
pete@inquo.net