Is there a way to reload a module from the console, so that we could isolate the amount of failure is necessary for these types of changes? For me this would be a pretty big improvement in reliability, although I may just see it that way because I am still figuring out configurations.
I will say that I was able today to do an * reload during the day, by just watching the phone lines and waiting for all of them to go free. This of course will get harder as we add more sites into the central system. -- Jonathan Moore Director of Technology Winfield Public Schools Office 620.221.5100 Fax 620.221.0508 Quoting Rich Adamson <[EMAIL PROTECTED]>: > > Another concern I have on this front is that it seems like some updates > require > > an asterisk restart rather than just issueing a reload command from the * > > console. This that correct, or I am just not running the system correctly? > For > > instance it seems like I couldn't get zapata.conf changes to go into > effect > > without closing * and starting it again. It also seems like some changes > in > > sip.conf don't go into effect either. > > You are exactly correct. I've not attempted to categorize which changes > actually require a start/stop vs reload, but would assume those config > entries that are actually used by modules (where the modules are unloaded > and loaded during stop/start) is part of the issue. > > > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > Visit Winfield Public Schools at http://usd465.com ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
