If your reload time is so long, it's possible that some of your gateways or your billing backend have long response times. To reload the config, the gatekeeper has to lock all calls. This means no outgoing call setup is in progress and all auth/acct modules finished their work. Otherwise the gatekeeper waits till all tasks have finished. I am not sure, if using SQL config will improve performance (it will definitelly improve config management). ----- Original Message ----- From: "Jirí Gubík" <jgubik@xxxxxxxxxxx> Sent: Wednesday, June 27, 2007 8:30 PM > Hi, > I noticed increased duration of reload time with increased number of > routing informations in config file. Our current config files are around > 200KB. We use only internal and neighbor routing policy. Current reload > time is more than 1 minute, which is too long. We need to reload our > gatekeepers several times per day. I currently added to config 500 more > destinations and reload time was almost 5min or some of gatekeepers > crashed. > Will transfer of config file to SQL help? Or should we focus to move all > routing to virtual queue? Is any example application of handling virtual > queue available? > Thanks for answers. > Jiri ------------------------------------------------------------------------- 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/
