Could you be a little more specific (some example, a trace log fragment)? In case of network failure (signalling channel failure) it is possible that the gatekeeper did not discover call being dropped. But under usual circumstances one of the call parties detects the failure and sends ReleaseComplete or DRQ. ----- Original Message ----- From: "K R" <kennethrouted@hotmail.com> Sent: Tuesday, December 16, 2003 9:39 AM > I understand that GNUGK does not handle network failure very well, but > network connectivity to my gatekeeper was never disrupted. Of late, after > upgrading to 2.0.7 which fixes the previous bug where source signalling > address disappears, calls in the status port hanged till the > CallDurationLimit is reached. These calls are not discovered on the > originating gateway. > > Where should I look to fix this? ------------------------------------------------------- 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/
