----- Original Message -----
From: "Mark Lipscombe" <markl@gasupnow.com>
Sent: Sunday, August 24, 2003 1:55 AM
Subject: [Openh323gk-users] RADIUS + Child Gatekeepers
> My RADIUS daemon is configured with a list of users which are e164
> numbers, so the default choice for the User-Name RADIUS field was
> unsuitable, so I made a small addition to send Calling-Station-Id in the
> Login-Check request, which picks e_dialedDigits over other fields. I'm
> not sure if this is the most desirable way to do this, but I've attached
> the patch to radauth.cxx to this message.
I am not sure whether Calling-Station-Id should be sent to Radius server
upon receiving RRQ. I was thinking about a similar problem and found
the following idea - let's include whole alias list with 'h323-ivr-out' attribute.
For example:
Acesss-Request {
User-Name = "testuser",
h323-ivr-out = "aliases:testuser,1111234,1111235"
}
Then radius server has an option to validate whole alias list and either
throw away aliases that are not permitted for the given user or reject
request because of invalid aliases. Sample answer could look like:
Access-Accept {
h323-ivr-in="aliases:testuser,1111234"
}
---
Michal Zygmuntowicz
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
