Opengk Developers, Just thinking about putting my 2 cents into this conversation. An idea I had is using an external program for all authentications, removing the need for any particular methodology. Think of it this way * A RAS or q.931 request comes in * It sends a bunch of predetermined variables to an application (as defined in the ini file) * the application does it's work * application returns a bunch of variables in return that GNUGK knows how to handle For reporting back to a application use the status port. so for something like RADIUS etc:- * A user tries to make a call on GNUGK * An external application talks to the RADIUS server telling it the IP, Username, Password or whatever the information the application needs. * Application returns OK and a time limit of 400 seconds * GNUGK approves and handles this call disengage it in 400 secs This would as I see it stop the bloating of GNUGK as it tries to accomplish all the different models of authing. Instead developers can work on auth libraries catered for each situation in whatever language they choose... Maybe there is a better way to handle calls between applications, I'm not sure, however using this kind of methodology means that GNUGK development can become more focused on other areas... Just a thought. Andrew ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
