Maybe your SQLAcct query has some errors? Or maybe you are using disconnect cause with UpdateQuery. It's valid only with StopQuery. Also, if Setup/ReleaseComplete is not received I am not sure if disconnect cause is set. ----- Original Message ----- From: "Suren Hakhnazaryan" <surenx@xxxxxxxxx> Sent: Saturday, May 26, 2007 8:49 PM > Hi > I've just debugged some numbers which were inserted into database with > disconnect cause code 0. > I've attached that file, for confidentiality I've changed the ip addresses > and the numbers. > Here's the info which will help you understand who calls who and by which > number. > > 1st number: 75583520326 > 2nd number: 75583691276 > 3rd number: 75584453804 > 4th number: 75586421554 > 5th number: 75591234689 > > Caller IPs: 90.90.90.90, 90.90.90.91, 90.90.90.92, 90.90.90.93 > > Calee/Destination IPs: 50.50.50.50, 50.50.50.51 > Gatekeeper IP: 50.50.50.55 > Gatekeeper Name: gk_main_1 > > In the file pay attention to the update query of postgresql which updates > the record and sets the disc_cause value to 0. > > If you have any suggestions please let me know. > Thanks in Advance. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________________ 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/
