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" }
This sounds really good. I will make a patch based on your suggestion. One question I do have is whether there is any commonly accepted mechanism to inform the client that their RRQ is partially accepted, especially where prefixes are involved?
If there isn't such a mechanism, then perhaps it would be better to outright refuse the registration, rather than leaving endpoints wondering why things are only half working?
Cheers, Mark
------------------------------------------------------- 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/
