Upgrading CompletePBX from v.4.00 to 4.5

Document version: 1.0

This document provides instructions for upgrading Xorcom CXR1000/2000/3000 and CXE2000/3000/4000 Servers running CompletePBX v.4.00.0 to the version 4.5. There is another document that describes the updating procedures for the Twinstar servers (CTS2000/3000/4000.)

Prior to performing the upgrade, it is strongly recommended that you backup your current server using the Xorcom Rapid Recovery tool (https://www.xorcom.com/Rapid-Recovery).

IMPORTANT NOTE!

The Schmooze commercial modules are not supported in this version. Most of them have been replaced with modules that have been developed by Xorcom, as detailed in the following table:

CompletePBX v.4.0 CompletePBX v.4.5 replacement
System Admin System Settings
EndPoint Manager Endpoint Manager
Extension Routes Routing Groups
FaxPro FaxMaster
Emergency Notification n/a
Text To Speech n/a

You will be requested to confirm those changes. This will be an opportunity to stop the upgrade process.

Upgrade Procedure

1. Download the version upgrade tool and unpack it:

cd /tmp 
wget http://updates.xorcom.com/servers/tools/cpbx-4-4.5-upgrade.tar.gz 
tar xzf cpbx-4-4.5-upgrade.tar.gz 

2. Run the upgrade script:

cd cpbx-4-4.5-upgrade 
./run-upgrade 

You will be prompted for the commercial modules removal.

The amount of time required to complete the upgrade process depends on the available Internet bandwidth. It can be quite lengthy. The upgrade log is saved in the upgrade.log file. The run-upgrade script performs the upgrading in several stages. The current stage is saved in the stage file that is created in the same folder where the script is installed.

If the script fails for any reason (e.g., particular YUM repository is temporarily unavailable, etc.) then it is usually safe enough to run the script again. The run-upgrade will resume from the point where it was interrupted.

If the software upgrade has been completed successfully the following message will appear:

*** Upgrade completed successfully.
 Reboot the PBX. 

3. Reboot the server.

That’s it!