RE: (RADIATOR) Cisco AS5300 VoIP / Radiator

2001-02-14 Thread Kitabjian, Dave

> ...One interesting thing to 
> note is that the AS5300 seems to be sending a null User-Name 
> ("") when they use account/PIN.

That seems odd to me. After the initial "pre-authentication", as the
documents suggest, ours prompts for an Account Number and PIN, and the
Gateway plugs them into the RADIUS Username and Password attributes,
respectively.

However, you can probably get this behavior to be anything you want based on
what IVR script you select in the Gateway...

Dave

===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) Cisco AS5300 VoIP / Radiator

2001-02-13 Thread Hugh Irvine


Hello Jeremy -

At 17:54 -0500 01/2/13, List Account wrote:
>Hi,
>
>  We're trying to setup Radiator to work with our Cisco AS5300 to 
>do Voice over IP.  We have things (basically) working, it will 
>authenticate off of caller ID, etc.  But, there are a few extras 
>we'd like to do and need some advice on.
>
>  First, has anyone used Simultaneous-Use with the AS5300 using 
>account numbers and PINs?  For example, Joe User dials in, enters an 
>account number, a PIN, and makes a call.  Let's say his wife picks 
>up the phone at some other location, dials in, and enters the same 
>account number and PIN.  It shouldn't let her use it if he's already 
>on.  One interesting thing to note is that the AS5300 seems to be 
>sending a null User-Name ("") when they use account/PIN.
>
>  Second, whenever multiple users are dialed into the unit, only 
>one user is showing up in the online user database.  I have the 
>radwho.cgi setup to work with it, and it only shows one entry in the 
>database.  We are just using a standard DBM database file for now, 
>until we get things working, at which point we'll migrate it to 
>something better.
>
>  If anyone has any ideas that may help, it would be appreciated.
>Thanks. :)
>

If you use a , you can provide your own queries 
to tailor the simultaneous use behaviour to your own requirements.

regards

Hugh

-- 

NB: I am travelling this week, so there may be delays in our correspondence.

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.

===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



(RADIATOR) Cisco AS5300 VoIP / Radiator

2001-02-13 Thread List Account

Hi,

 We're trying to setup Radiator to work with our Cisco AS5300 to do Voice over IP. 
 We have things (basically) working, it will authenticate off of caller ID, etc.  But, 
there are a few extras we'd like to do and need some advice on.

 First, has anyone used Simultaneous-Use with the AS5300 using account numbers and 
PINs?  For example, Joe User dials in, enters an account number, a PIN, and makes a 
call.  Let's say his wife picks up the phone at some other location, dials in, and 
enters the same account number and PIN.  It shouldn't let her use it if he's already 
on.  One interesting thing to note is that the AS5300 seems to be sending a null 
User-Name ("") when they use account/PIN.

 Second, whenever multiple users are dialed into the unit, only one user is 
showing up in the online user database.  I have the radwho.cgi setup to work with it, 
and it only shows one entry in the database.  We are just using a standard DBM 
database file for now, until we get things working, at which point we'll migrate it to 
something better.

 If anyone has any ideas that may help, it would be appreciated.
Thanks. :)

 Jeremy


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.