To verify if the client did connect on the wrong #, you would have to make a
SQL query to look up the calls table and do a search for the DNIS # that the
customer is not allowed to access via their account. If they tried
accessing it, then you can charge them or call them to mention they are not
using the proper phone number.
-----Original Message-----
From: Robb Bryn <rbryn@cape-fear.net>
To: 'RadiusNT@iea-software.com' <RadiusNT@iea-software.com>
Date: February 9, 1998 1:05 PM
Subject: RadiusNT/USR Total Control/ 56k question....
>I am investigating the feasibility of moving our current setup (NT RRAS) to
>use RadiusNT with a USR Total Control Unit and have a few questions.
>
>Is it possible with RadiusNT to manage users logging into a Total Control
>Unit and restrict their bandwidth/connect rates? To be more specific we
>have three accounts setup for our users 1 - 33.6 account, 2 - 56k acct, 3 -
>128k ISDN acct, each with flat rate pricing plans. The question is - How
>can I restrict my 33.6 accounts from logging on at 56k? Keep in mind they
>will all be logging into the same unit. Is this something that RadiusNT
>can handle?
>
>Thanks
>Robb Bryn
>
>___________________________________________________________
>Robert L. Bryn Cape Fear Live
>Webmaster PO Box 4741
>rbryn@cflive.com Wilmington, NC. 28406
>http:\\www.cflive.com (910)392-9887
>
>The Ultimate Online Magazine for Wilmington
>___________________________________________________________
>
>
>
>
> ----------------------------------------------------------
> RadiusNT Mailing List lists@iea-software.com
>