SIPfoundry

Mailing Lists

Issue Tracker

< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[sipx-users] sipXecs 4.0.2 released

We're delighted to announce that version 4.0.2 of sipXecs is now available.

We expect this to be the last fix release in 4.0 - the next planned release is 4.2.0; this could of course change if a sufficiently serious problem is uncovered.

sipXecs 4.0.2 Release Notes
23 Bug Fixes
6 Improvements/New Features

Upgrading to sipXecs 4.0.2

There are two ways to upgrade from earlier releases:

Command Line (recommended)

As root:

Clear your rpm cache: 
yum clean all
Download and install the updates (this assumes you have already configured the sipXecs stable repo available at http://www.sipxecssw.org/pub/sipXecs/): 
yum update
When prompted, confirm the update

When the update has finished, restart sipXecs services:
service sipxpbx restart
If any services are disabled or you are seeing issues after the upgrade, try this from the command line first:
service sipxpbx stop
sipxconfig.sh --first-run
service sipxpbx start

GUI Upgrade (only should be attempted on CentOS distributions)

The reason this isn't currently recommended is that this method provides very little information on the status of the upgrade. This is being tracked as XX-6524. It also will NOT  upgrade other servers in your cluster due to an issue fixed in this update XX-5929. If you do use this it may be good to monitor the update log file on the server to know what is going on. That can be seen by doing this from the command line
tail -f /var/sipxdata/tmp/update.output
When you see Complete! In the log file you need to restart the system.
  1. From sipXconfig go to System -> Software Updates and click on check for updates.  Note: The system will check automatically and you will see a notification that an update is available if you don't do the above.
  2. The available packages will be shown that are to be updated.
  3. Click on Install updates and restart when finished.
  4. For distributed servers, the Command Line option is the only working option. This is fixed in this release (XX-5929).