You are probably using the signaling routed mode, but the signaling channel for the call is not routed through both gatekeepers. This result in the call state "connected" for the first gatekeeper and "unconnected" for the second one. Timeout for unconnected calls is 180 seconds. It will be possible to disable this timeout in 2.0.7 version of the gk. The best solution for you would be to force the signaling channel to be routed to the second gatekeeper. ----- Original Message ----- From: "James Lertora" <jlertora@patton.com> Sent: Monday, December 22, 2003 11:28 PM I had posted a question about getting a three minute timeout a few weeks back. I am using two GKs on two separate networks in an alternate GK setup. Basically they are mirrored. When I monitor the monitor port on the GK I can consistently reproduce getting a 180 time restriction on calls from one endpoint to another, both endpoints registering on separate GKs. Is this a confirmed bug by anyone here using the GKs in a topology as this ? ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
