Scott Lawrence wrote: > On Mon, 2008-10-20 at 15:16 -0400, Paul Mossman wrote: >> David wrote: >>> I now have code for FirstRunTask.java runTask() that will >>> regenerate the profiles and restart the gateway/phone >>> devices. The code in runTask is executed during a system >>> startup, including a system startup due to an upgrade. >>> >>> The original issue requested the regenerate/restart behaviour >>> only for upgrades. I was wondering if it would be a good idea >>> to regenerate/restart the devices on all system startups? >>> This would ensure that the system starts up cleanly, however >>> it may also take down established calls. But perhaps that's a >>> good thing since it will clear calls that CDR may not be >>> tracking properly? >>> >>> Please refer to the original issue: >>> http://track.sipfoundry.org/browse/XCF-2739 >> I don't think we need to worry about established calls going down. >> Phones tend to be smart enough to not reboot while in an active call. >> >> However, sending a restart to all phones upon system startup... I like >> that it freshens things up quite nicely. (BLF subscriptions for >> instance.) Actual customers might find it a bit drastic though. >> Consider consulting sipx-users. > > The goal of system management is to keep users from calling you with > problems. Good system managers do this mostly by preventing problems > from occurring, or solving them before users notice. Clever system > managers avoid doing things like causing every phone in the building to > restart in rapid succession - because it makes users nervous and some of > them call to report it. > > Most SIP phones have decided that it is important that they make some > kind of noise when they reboot (really bad idea, by the way), which > makes a mass reboot kind of unnerving in a big cubicle-office > environment. ("beep, beep, beep, beep, ....") > > I'd say this is something that should happen only when the administrator > explicitly says it should happen. > >
Restarting the phones every time you're restarting sipXconfig is an overkill. If admin really needs it, it can be done from UI. Or you can force the system into "freshly after upgrade mode" by running 'sipxconfig.sh --first-run' and restarting the system. And in 3.11 we have scheduled restarts: so to 'refresh things nicely' you can schedule the restart to happen in the middle of the night. As a side note: sipXconfig _always_ throttles phone restarts - even if you schedule them to happen at the same time they will be phased in. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
