Aivis,
you can easily solve this situation by either handling Accounting-On
query (that closes all calls in the database from this gatekeeper) or by using Accounting-Update event and periodically checking
which active calls have not been updated for too long time.
But I guess Accounting-On would be the best place to close any
hanging calls.
----- Original Message ----- From: "Aivis Olsteins" <aivis@xxxxxxxxxxxxxxxx>
Sent: Thursday, November 11, 2004 9:46 AM
Even not to mention situation when gk crashes (is killed, or network goes down) and accounting-stop messages do not arrive ever. Sessions ten can "hang" forever.
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/