Hi, did you have IRRCheck=True in your original config ? Or was the parameter completely missing ? Regards, Jan Lucian Gheorghe wrote: > With this in the gatekeeper.ini : > > [CallTable] > DefaultCallTimeout=7200 > IRRFrequency=0 > IRRCheck=False > > it didn't crash anymore. I can't do exactly what you want because this is a > production environment and this happened every since we updated from version > 2.0.7 to 2.2.3. > > I just downloaded the CVS version and will update to that version tonite, > but since we added those lines in the config it didn't crash. > > It was very strange because all other equipments were sending IRR and gnugk > worked fine. When a Cisco ATA 186 sent an IRR message gnugk just died. This > didn't happen in version 2.0.7. > > Best Regards, > Lucian -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________________ 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/
