...
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 | ||||||
|---|---|---|---|---|---|---|
|
Then in a root window on the system you wish to upgrade run
...
| Code Block |
|---|
wget -o /etc/yum.repos.d/sipxecs.repo http://download.sipfoundry.org/pub/sipXecs/sipxecs-4.0.4-centos-x86-64.repo |
Step 3. Shutdown sipxecs and update your system.
...
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 | ||||||
|---|---|---|---|---|---|---|
|
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
...
- 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
Before upgrading to 4.2.0
- Remove the old repo file:
Example:Code Block rm sipxecs-4.2.0-centos-i386.repo
Before upgrading from 4.2.1
- Remove the old repo file.
Example:Code Block rm sipxecs-4.2.1-centos-i386.repo
Before upgrading to 4.4.0
No special instructions
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"; |
After upgrading from 4.0.4
...
| Note | ||
|---|---|---|
| ||
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
After upgrading to 4.2.0
No special instructions
Before upgrading from 4.2.1
...
After upgrading to 4.2.1
No special instructions
...
No special instructions
After upgrading to 4.4.0
...