Re: Cannot Limit Calls Based on DNIS # and Multi POPs

Dale E. Reed Jr. ( (no email) )
Tue, 20 Jan 1998 23:47:38 -0800

Rudy Komsic wrote:
>
> sorry for repost... but I did not see any reply to this.

It currently can not be done. We'll look into the possibility of enhancing
server port access to handle DNIS and NAS-Port-Type as well.

> -----Original Message-----
> From: Rudy Komsic <rudyk@cyberglobe.net>
> To: RadiusNT@iea-software.com <RadiusNT@iea-software.com>
> Date: January 8, 1998 1:29 AM
> Subject: Bug: Cannot Limit Calls Based on DNIS # and Multi POPs
>
> >Hello,
> >
> >Just to give out our basic Layout on how we are currently using our new
> >Chassis system to limit Theft of Service, we are configured with ISDN PRI
> >Connections (47 Lines per chassis) and we have 3 Phone numbers for our
> >clients to call in on. Line 1 is for up to 33.6k Only, Line 2 is for 33.6k
> >and X2, and Line 3 is for 33.6k, X2, and ISDN. Our USR Total Control
> >Chassis have a feature that allows us to setup DNIS Pre Initialization
> >before pickup so that we can limit the speed for our clients.
> >
> >The Problem is how do I set the Radius Attribute NAS-Port-DNIS for a
> >specific group login to the DNIS number the client is ONLY to dial. For
> >Example I tried the following to see if it would limit login to the
> >specified DNIS #:
> >
> >Framed-Protocol: PPP
> >Framed-Address: 255.255.255.254
> >Session-Timeout: 28800
> >Idle-Timeout: 1200
> >NAS-Port-DNIS: 0001 (Line #1 for 33.6k only)
> >
> >Now, if I called on line #2, the NAS returns the Info to the RadiusNT
> >software, is has NAS-Port-DNIS as 0002 but I discovered that RadiusNT has
> NO
> >support to check to see if NAS-Port-DNIS is the one the client is allowed
> to
> >use. Can you please tell me how to do this feature? If this feature is
> not
> >available, could you please add this feature in ASAP so that we can
> simplify
> >with Multipurpose Chassis?
> >
> >Also, can you add support for Multiple DNIS numbers as well for MultiPOPs.
> >
> >Thank you for your prompt reply.
> >
> >PS: BTW, there may be a bug with USR's Total Control Modem Code 5.6.7 and
> >Netserver Code 3.6.28 with RadiusNT. When we establish a connection via a
> >Radius account, it works but when we try to login a user via the NT User
> >Manager account, it fails. This currently works with the older code but
> the
> >newer code fails.
> >
> >----
> >Rudy Komsic
> >President - Cyberglobe Communications Inc.
> >4996 Place de la Savane, Montreal, Quebec, H4P 1Z6, Canada
> >E-Mail: rudyk@cyberglobe.net Phone: (514)342-3883 Fax:(514)342-5139
> >
> >
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com

-- Dale E. Reed Jr.  (daler@iea.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |   http://www.iea-software.com