Upgrading a XiVO PBX is done by executing commands through a terminal on the server.
Downgrade is not supported
The upgrade consists of the following steps:
- switch the version via
- upgrade via the
xivo-upgradeutility: it will upgrade the system (Debian packages) and the XiVO PBX packages
The following applies to XiVO PBX >= 2016.03. For older version, see Version-specific upgrade procedures section.
You must stop all services (
xivo-service stop all) on Media Servers linked to your XiVO Main before the upgrade.
Preparing the upgrade¶
There are two cases:
- Upgrade to another LTS XiVO PBX version,
- Upgrade to the latest Bugfix release of your current installed LTS version.
Upgrade to another LTS version¶
To prepare the upgrade you should:
Switch the sources to the new XiVO PBX LTS version with
xivo-dist, for example, to switch to Gaia LTS version:
Read carefully the Release Notes starting from your current version to the version you target (read even more carefully the New features and Behavior changes between LTS)
Check the specific instructions and manual steps from your current LTS to your targetted LTS and all intermediate LTS: see Manual steps for LTS upgrade
Check also if you are in a specific setup that requires a specific procedure to be followed (e.g. Upgrading a cluster).
And then upgrade, see Upgrading
Upgrade to latest Bugfix release of an LTS version¶
After the release of an LTS version (e.g. Freya) we may backport some bugfixes in this version. We will then create a subversion (e.g. Freya .04) shipping these bugfixes. These bugfix version does not contain any behavior change.
To upgrade to the latest subversion of your current installed version you need to:
Read carefully the Release Notes starting from your installed version (e.g. Freya.00) to the latest bugfix release (e.g. Freya.04).
Verify that the debian sources list corresponds to your installed LTS or refix it, for example for Freya:
And then upgrade, see Upgrading
About xivo-upgrade script usage see xivo-upgrade script
After having prepared your upgrade (see above), you can upgrade:
When ready, launch the upgrade process. All XiVO PBX services will be stopped during the process:
(Izar only) If you’re using
chan_sipon your Izar XiVO you must do again the Fallback to chan_sip SIP channel driver procedure.
Check that all services are running:
xivo-service status all
Check that all the docker services are in the correct version. Compare the output of
xivo-dcomp versionwith the table in Release Notes
Check that services are correctly working like SIP registration, ISDN link status, internal/incoming/outgoing calls etc.
- Upgrading a cluster
- Migrate XiVO from
i386(32 bits) to
- Asterisk upgrade procedure
- XiVOCC Recording upgrade procedure
- Debian 9 (stretch) Upgrade Notes
- Debian 10 (Buster) Upgrade Notes
- Debian 11 (Bullseye) Upgrade Notes
- Outcall to Route Upgrade Guide
- ELK 7 Upgrade Notes
Version-specific upgrade procedures¶
If your XiVO PBX is below 2016.03 you have first to Switch to xivo.solutions mirrors.
- Switch to xivo.solutions
- Other Version Specific Procedures
Upgrading to/from an archive version¶
See Release Notes for version specific informations.