I think the rule of thumb when doing a yum update currently is: 1. shut down sipx services 2. yum update 3. start sipx services 4. login to sipx and re-send the server profile 5. phones rebooting might be "normal" during an upgrade if the corresponding vm template chaanges, to get them the current template configurations.
On Wed, Mar 2, 2011 at 1:04 AM, Kumaran < [email protected]> wrote: > Hi All, > I Yum update from sipXconfig sipXconfig (4.4.0- > 2011-02-19EST00:30:27 swift) to sipXconfig (4.4.0- 2011-03-01EST10:46:34 > swift) then I restarted the config server using cmd sipxproc -r > ConfigServer and after few second phones got rebooted automatically and > after login to superadmin got a message "one or more services failed" in > job status failed message for time out message for one of our > phone which also got rebooted.Please guide us to know whether this > behavior is fine. > > Rgrds > Kumaran T > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
