Hi Mark, it is a nice feature. Actually, I had a similar idea. Unfortunatelly, I am currently busy with preparation of 2.0.7 release. It would require some reengineering GkAuthenticator API (to accept non-const RRQ objects), but it should not be difficult to implement. The authenticator would just add/remove aliases from RRQ m_terminalAlias field and it should work fine. ----- Original Message ----- From: "Mark Vevers" <mark@vevers.net> If anyone has any suggestions on my first question (how to assign E.164 numbers to connecting endpoints) please let me know - I really can't see how to do this within the existing infrastructure? If not can the developers speak up and let me know if it would be possible to add this and if they can't find the time themselves some pointers as to how they might do it if they were to do so? (I.e. where they would put it - what would be acceptable etc as if I find the time to add C++ to my prog languages I would like the patch to be acceptable to be integrated into the main code base). My idea would be to send back a cisco-avpair of type "cisco-h323-ivr-in" with additional aliases in the radius response that get added to the aliases for that endpoint? ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
