Having worked with gnugk and a lot of not_so_standard gateways and gatekeepers (read: cheap trash) I realised that in order for gnugk to deal with them, the distinction between gateways and gatekeepers is getting smaller and smaller. Gnugk itself can receive calls directly as a gateway, thus functioning like a soft switch. As I understand it, the real difference between a gateway and a gatekeeper is (in theory) the ability to route calls, but this is done by most gateways as well; and the LRQ and registration mechanisms. Therefore my suggestion is this: Unify the neighbor and the permanentendpoints sections into a single neighbor section. The <gkidentifier>=<type> where type is 'gateway' or 'terminal' would replace the old permanentendpoints section and add a lot more control, like Accept and Reject prefixes, capacity, round-robin, maybe even hunting and also rewriting of numbers. I know what I am proposing sounds a lot like the Cisco dial-peers that I am used to work on and maybe there are better solutions, but this seems an elegant way to solve all the problems that arose lately, not only to me, but to other users on the list as well. Managing destinations would also be simpler. Anyway, that's my two morning cents. ------------------------- E-Mail powered by MadNet. http://www.madnet.ro/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&opÌk _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id?49 Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
