In general, GNU GK does call authentication upon receiving ARQ message from registered endpoint. That's why I wrote "ARQ authenticators". All GK authentication methods (alias,username/password,mysql,ldap,radius) are implemented for authenticating registered endpoints. But if you want to allow calls from unregistered endpoints to be authenticated somehow (by IP or alias), you have a chance to do it only upon reciving Q.931 Setup message (unregistered endpoints do not send ARQ). I wrote Q.931 Setup authenticator module for radius, but you are free to add your own modules. If your endpoints use H.235 security (username/password), then you will need authentication/authorization to be done upon receiving ARQ. ----- Original Message ----- From: "Allen Williams" <anw@csunv.com> Sent: Sunday, September 21, 2003 12:22 AM > Although I'm almost positive that what I need is what you're calling the > Q.931 Setup message, since you are associating that with radius, and I'm > using my radius server to authenticate, I would still like to know the > difference. What's the difference using Q.931 Setup (and I know what that > is- the call control that runs over both ISDN, PRI & BRI, as will as in ISUP > on SS7), but what I don't understand is its link to radius specifically, and > what is the alternative, the "ARQ Authenticators" you mention? H.323 ARQ > doesn't have anything in it to support limiting call duration, does it? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
