If your gateway does not support H.235 and CAT passwords, you cannot use it with RadAuth. If you are using gk 2.2, you can put two auth rules: RadAuth=optional;RRQ RadAliasAuth=optional;RRQ default=reject;RRQ This way, if authentication (no matter succesfull or not) can be performed with RadAuth, only RadAuth is checked. If not, RadAliasAuth is tried. If none of the above could determine the authentication status, the request is rejected. Lokotes <lokotes@xxxxxxxxxxxx> wrote: >When setting the Gatekeeper::Auth to RadAliasAuth gateway registers to >GK without any problem but... when changing to RadAuth - registration >fails. After looking into radius, mysql and GK logs I\'ve figured out that: >- GK returns RADAUTH RRQ Auth failed - no m_tokens >- radius doesn\'t notice anything as well as mysql > >so, authorization stops at GK ! >I really need this type of authorization so maybe there is another way >to make gateway work with GK? > >P.S. >standard H323 clients (terminals) register correctly. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
