Hi Gabriel, PrefixCapacities are a bit particular in regards to reload, but in a different way than you describe: When you reload your config, the stats counters get reset to zero and the new prefix limits are read in. If you have ongoing calls while you do the reload your stats counter will be _lower_ than they should (and calls may fail on the overloaded gateway). At least that is the intended behaviour since migrating the call stats to a new set of capacity settings is a very hard job. So, please re-test without reloading to see if your counters get properly decremented. They were in my tests, but of course I might have overlooked something. If somebody wants to tackle the stats migration between different capacity setting, feel free to send me a patch. ;-) Regards, Jan Gabriel Georgescu wrote: > Hi, > > I think there may be a problem with the new feature 'PrefixCapacities'. > It works well until the maximum call limit is reached. But then it > will reject all further calls even if there is room for them. > It looks like the counter remains at the maximum value and is never > decreased beginning with that point. > I'm not sure if this happens always or only after a config reload. I > tested only after config reload. > > All the best, > Gabriel -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------- 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/
