Another reson can be that the gatekeeper somehow does not know the call has been connected (Connect message received). Default timeout to disconnect not connected calls is 180s. What does the status line shows after '!' command (the last two numbers are call duration and timeout). Make sure you did not set DefaultCallDurationLimit parameter to 180. Is the gatekeeper running signalling routed mode? ----- Original Message ----- From: "James Lertora" <jlertora@patton.com> Sent: Wednesday, November 26, 2003 12:17 AM > Yeah, the trace showed the GK ending the call. > I did play around with the TTL, but did not think this could affect it. > It is pretty consistent regarding the time, so it might not be the RTCP. > Our gateways (smart nodes) request 90 seconds when registering with the GK. > I read that if you set the TTL higher than requested by a gateway > then the GK will default to 60secs thus it seemed to cause lots of RRJ > requiring full registrations. It is strange that the TTL is set to 90 and > the hang-up is happening at twice that. Hmm.. ------------------------------------------------------- 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/
