Dear All, I managed to solve my own problem, and I'm posting the solution to save time to whomever may make the same mistake in the future. a) when you set up a child gatekeeper, you must also define it as a neighbor in the parent one... somehow I had dropped this section from my configuration file in the course of tests (since I did reach in the past few days the functionality I described, that section must have been present in previous versions of my files) b) it is perfectly legal to 'delegate' the whole available e.164 space to the child. with these modifications the endpoints registered with the internal gatekeeper can call outside and be called, and the external ones registering with the external gatekeeper can call outside (of course) and also be called as long as the routing policy is internal,neighbor,parent. Sorry for the noise. Best regards Alessandro -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
