xx xx wrote: > > Hi Alex, > I had the same situation. Actually the problem for me was that I have always received m_h245socket != NULL using some CPEs. With others I have no problems. To solve this I commented this checks and now gk works well - just checks the disconnect reason and thus I can easyily control when to fail over the call. > > Actually many carriers gives fast start response and still can't complete the call, so I think thes checks are quite restrictive and not should be done. > I think your solution is too broad for general GnuGk code. Are you sure your callers can establish the 2nd call after they have received H.245 responses from the first failing call ? Or could this result in multiple more retries that all just fail ? > My problem is that my gk crashes very often 1-2 times a day (with this checks and without them, no difference). Can you please share your experience including pwlib, openh323 version. I have some more reports of high load installations crashing with 2.2.4 while others run fine. The current guess is that there is a race condition someplace where we handle multiple messages for the same call. But so far no specific cause has been found. Regards, Jan -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
