Versions Compared

Version Old Version 12 New Version 13
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

When performing an upgrade is always a good idea to backup your production system. It is also good to perform the update on a test system first in order to mitigate risks in production.

Warning

There is a bug in 4.0.4 that breaks upgrading using the web user interface. Specifically, it disables use of the CentOS repositories during the upgrade, which causes some prerequisites to be unavailable, which makes the upgrade fail. The bug has been fixed in 4.2 (and a bunch of other improvements to the upgrade interface have been made too).

The best way to avoid the problem is to just do the upgrade from the shell command line (you must be logged in as 'root'):

Check your yum repository configuration to make sure that it points to the stable release area:

Code Block
[sipxecs-stable] name=SIPfoundry sipXecs pbx - latest stable version baseurl=

It is also NOT recommended you use the administration web interface to upgrade your system from one version to another. The administration web interface for upgrading is best used for minor bug updates.

You can upgrade from any version to any version as long as you follow the manual steps both before and after your upgrade.

Step 1. Follow each of the Before instructions starting with the version you currently have installed. Then come back to this step and continue.

Step 2. Visit download area and decide what version is right for you based on the version numbers. Find the link to the file that ends in .repo and right click in your web browser and copy the link.

Table of Contents
includeBefore*
indent20px
styledisc

Then in a root window on the system you wish to upgrade run

Code Block

 wget -o /etc/yum.repos.d/sipxecs.repo  <URL to repo file here>

Example:

Code Block

 wget -o /etc/yum.repos.d/sipxecs.repo http://download.sipfoundry.org/pub/sipXecs/LatestStable/CentOS/$releasever/$basearch/RPM
gpgcheck=0
enabled=1

...

sipxecs-4.0.4-centos-x86-64.repo

Step 3. Shutdown sipxecs and update your system.

Code Block

service sipxecs stop
yum update -y

If you have multiple systems in a cluster (all managed by one Management server), upgrade all the systems as above

...

reboot (management system first).
Log in to the the management UI, go to System -> Servers, select the management server, and press Send Profiles.
Reboot each distributed server, and when it is up select it on the servers page and press Send Profiles.

Step 4.

...

Follow each of the Before instructions starting with the version you currently have installed. Then come back to this step and continue.

Table of Contents
includeAfter*
indent20px
styledisc

Before upgrading from 3.10.x

The local domain bind zone is "emptied", if you are using the system as a DNS server, you should copy or backup your zone file before the update. It doesn't effect other zone files on the system, just the one sipx is attached to.

After upgrading from 3.10.x

The DHCP 120 test will fail if you are using the on board DHCP server. To correct this you need to add the following to the /etc/dhcpd.conf and restart dhcpd (service dhcpd restart). This is not required if you aren't using the Counterpath Enterprise Clients.

Code Block
# header section of dhcpd.conf
option sip-servers-name code 120 = text;

# subnet section of dhcpd.conf
option sip-servers-name      "<hostname>:12000/cmcprov/login";

...

Before upgrading from 4.0.4

If you originally installed your system from the sipfoundry ISO in 4.0.4 and are having issues updating, here's some help:

...

  • Edit the repo to make it JUST a CentOS repo again - remove these lines and save it:
    Code Block
    [sipxecs-stable]
name=SIPfoundry sipXecs pbx - latest stable version
baseurl=[http://sipxecs.sipfoundry.org/pub/sipXecs/4.0.4/CentOS/5/i386/RPM/]
gpgcheck=0
gpgkey=[https://secure2.pingtel.com/RPM-GPG-KEY-pingtel]
enabled=1
  • Get the correct repo for sipx:
    Code Block
    
cd /etc/yum.repos.d
wget http://download.sipfoundry.org/pub/sipXecs/sipxecs-4.2.1-centos-i386.repo

...

After upgrading from 4.0

...

.

...

4

...

Warning
title

If you have voicemail messages from the old version, let's say <=4.0.X, you might hit the XX-9461
A quick fix for that is:

Code Block
# fix all bad messages 
export TZONE=`date +%Z` 
find /var/sipxdata/mediaserver/data/ -name '*.xml' -exec sed -i "s|\([AP]M\)\s\+</timestamp>|\1 ${TZONE}</timestamp>|g" {} \;
Note
title

If you have customized versions of vxml files, you'll lose them starting on 4.2.0 as VXML are no longer used for Voicemail.

...

Before upgrading to 4.2.0

  • Remove the old repo file:
    Example:
    Code Block
      rm sipxecs-4.2.0-centos-i386.repo
    and get the newest sipfoundry one
After upgrading to 4.2.0
No special instructions
Before upgrading from 4.2.1
  • Remove the old repo file.
     Example: 
     Code Block
    wget http://download.sipfoundry.org/pub/sipXecs/  rm sipxecs-4.2.1-centos-i386.repo


    Issue a 
     Code Block
    yum update
     to 4.2.1 (sipfoundry)
After upgrading to 4.2.1
No special instructions
Before upgrading to 4.4.0
No special instructions
After upgrading to 4.4.0
No special instructions