Re: feature request

Rudy Komsic ( (no email) )
Sat, 6 Jun 1998 06:01:20 -0400

Also to ADD to this feature is a Limiter that WILL NOT Allow Clients to dial
the other Lines if they paid for this one service. It should reject his
connection.

Also, when will it be added to 2.5 Emerald as it was promised that it will be
in it?

-----Original Message-----
From: Brian Lube <brian@mpinet.net>
To: radiusnt@iea-software.com <radiusnt@iea-software.com>
Date: June 5, 1998 4:31 PM
Subject: Re: feature request

>I'm sorry, I didn't finish that sentence (I got interrupted by one of the
>other sysadmins here). I'm looking for this in the Radlogs table, so that
>when someone fails I can find out what number they are dialing into and
>from. This is nice for finding people who are hacking into my system.
>
>Brian Lube
>MPInet
>
>At 01:05 PM 6/5/98 -0700, you wrote:
>>Brian Lube wrote:
>>>
>>> I have a feature request for the next release of RadiusNT. I would
>>> *really* like to see it record custom fields (such as NASPortDNIS and
>>> Callerid). This would help me out *so* much.
>>>
>>> Just a request.
>>
>>If you are referring to the Calls table, it can already do this.
>>If you put fields in the Calls table matching the attribute names
>>(without the dashes) RadiusNT will populate the fields. It reads
>>the column list upon startup, so you have to restart it for the
>>changes to take affect.
>>
>>--
>>Dale E. Reed Jr. (daler@iea-software.com)
>>_________________________________________________________________
>> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
>> Internet Solutions for Today | http://www.iea-software.com
>>