Re: [RadiusNT] ISDN

Peter D. Mayer ( (no email) )
Thu, 10 Dec 1998 10:01:10 -0500

Just make sure you have NASPortType (tinyint) added to your Calls table.
This will log the type of port that someone is getting. If you want to
restrict logins by this information, I think you have to make it a Check
Attribute, which I've never tried.

The values for this attribute, according to RFC (I think) are
Async=0 (analog)
Sync=1 (leased line or T-1)

Hope this helps.
Peter D. Mayer
NetWalk System Administrator

-----Original Message-----
From: Rita Ruggeri <>
To: <>
Date: Thursday, December 10, 1998 6:57 AM
Subject: Re: [RadiusNT] ISDN

-----Original Message-----
From: Ted Olson <>
To: <>
Date: Wednesday, December 09, 1998 9:04 PM
Subject: Re: [RadiusNT] ISDN

>I don't know if that difference can be distinguished. (Anyone?) But as a
>practical matter we really don't care, we charge the same for a single-port
>ISDN connection as for single-port analog, it's only the port usage that's
>important (and maybe bandwidth in the future). With RadiusNT set to manage
>concurrent connections and an account set to "maximum 1 connection",
>2-channel ISDN won't work. If the subscriber wants 2-channel (who
>wouldn't?), you can increase their max concurrent connections limit to 2
>and charge accordingly.

But I want offering 2 services, RTC and ISDN.
I hoped RadiusNT can do it before user connecting.

>At 05:55 PM 12/4/98 +0100, you wrote:
>Does anyone can tell me how distinguish ISDN client and analogic client?
>I use ODBC trial version with database access and I'm looking for examples.