From SIPfoundry sipXecs IP PBX, The Open Source SIP PBX for Linux - Calivia

This procedure applies to all 4.0.x upgrades

Contents 1 Before you upgrade to sipXecs 4.0.2. 1.1 Local DNS Zone Files 1.2 Update 'yum' 2 Doing the Upgrade 2.1 Command Line (recommended) 2.2 GUI Upgrade (only should be attempted on CentOS distributions)

Before you upgrade to sipXecs 4.0.2.

See also sipXecs 4.0.1 Upgrade for notes on how to upgrade from versions < 4.

Local DNS Zone Files

The local domain bind zone is overwritten; if:

• You are using the system as a DNS server, and
• You have made any manual changes to the zone file

then before doing the upgrade, you should add the following lines to the beginning of the file /etc/named.conf:

 // WARNING: Name server configuration is a sipX automatically generated file.
 //          Contents may be overwritten unless you change the mode to "Manual".
 //          Available modes:
 //          "Master"    - Master name server (on primary server).
 //          "Slave"     - Slave named server (on distributed server).
 //          "Caching"   - Caching only name server.
 //          "Manual"    - Blocks future automatic updates.
 // DNS_MODE="Manual"

this will protect your changes from any automated updates by sipXconfig.

Update 'yum'

Make sure that you have the current version of the 'yum' utility; run:

 yum update yum

and confirm the update if requested.

---

Doing the Upgrade

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 sipxecs restart

If any services are disabled or you are seeing issues after the upgrade, try this from the command line first:

 service sipxecs stop
 sipxconfig.sh --first-run
 service sipxecs 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. 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.

1. The available packages will be shown that are to be updated.
2. Click on Install updates and restart when finished.
3. For distributed servers, the Command Line option is the only working option. This is fixed in this release (XX-5929).