I'll forward this reply to the openh323gk-users group. Please see comments inline. ----- Original Message ----- From: "Razvan Radu" <razvan.radu@coretech.ro> Sent: Wednesday, November 12, 2003 9:55 AM > from what I can figure out you are the maintainer for radius modules > (in case you are not I think that I misdirected my questions) > > 1. on what version are you developing new code 2.0 or 2.2 ? On both versions. But 2.2 branch is more likely to receive so called "experimental" features. > 2. is it possible to add a configuration directive not to use chap > passwords ? > but to fill out the User-Password attribute with the plain password > BTW: is the communication between the endpoint and gatekeeper secured > in any way ? You can use RadAliasAuth module and FixedPassword config variable. BTW: It depends on what do you mean by secured communication? If you mean "encrypted" then the answer is no, if you mean "the password is encrypted" the answer is yes. > 3. is there a way to know what module is being used (modauth or > modaliasauth) It's rather impossible. > and what request is being served (RRQ, ARQ or Setup) > alone this lines is it safe to assume that only ARQ and Setup > requests place > the Calling-Station-Id and Called-Station-Id attributes Yes. RRQ requests will never contain these attributes and ARQ/Setup requests will always contain at least one of them. You can also test for presence of call related h323-... attributes. > and also that only ARQ requests are used for registered endpoints > and only Setup requests are used for unregistered endpoints > (is it possible to receive both ARQ and Setup from the same endpoint?) Yes, it's very likely for registered endpoint and signalling routed gk mode. If RadAliasAuth module is configured for ARQ and Setup events, it will send Access-Request first when ARQ is received and then when Setup is received. > is it possible to include a attribute that specifies this information, > something like new-attr = aliasauth;ARQ ? (perhaps with a config param) You can derive you own authenticator class and override OnSendPDU virtual method to append any custom attributes you need. > 4. from what I figure out in the ARQ request the Calling-Station-Id attribute > is filled out with the dialedDigits but on the accounting packets it > is filled out with the h323_ID. this is the intended functionality ? can it > be changed so that the accounting packets contain in the Calling-Station-Id > attribute the source dialedDigits ? (I have two gateways with callerid and > in my opinion it is more interesting to know from where the call in coming from) We are currently working on a fix for this issue - it should be ready very soon. > 5. feature: is it possible to use an radius return attribute to proxy a call ? > I think that this is a very useful feature for a internet service provider > that provides voip services to clients that have broadband wan, but > no sufficient internet bandwidth. This is an interesting feature and has been already requested, so it is likely to be included in near future. Regards, Michal Zygmuntowicz ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
