Upgrading a Wazo is done by executing commands through a terminal on the server. You can connect to the server either through SSH or with a physical console.
To upgrade your Wazo to the latest version, you must use the
wazo-upgrade script. You can
start an upgrade with the command:
Warning: You can't use wazo-upgrade if you have not run the wizard yet. Upgrading from a deprecated version is not supported.
This script will update Wazo and restart all services.
There are 2 options you can pass to wazo-upgrade:
-dto only download packages without installing them. This will still upgrade the package containing wazo-upgrade.
-fto force upgrade, without asking for user confirmation
wazo-upgrade uses the following environment variables:
WAZO_CONFD_PORTto set the port used to query the HTTP API of wazo-confd (default is
- Read all existing upgrade notes starting from your version to the latest version.
- For custom setups, follow the required procedures described below (e.g. HA cluster).
- To download the packages beforehand, run
wazo-upgrade -d. This is not mandatory, but it does not require stopping any service, so it may be useful to reduce the downtime of the server while upgrading.
- When ready, run
wazo-upgradewhich will start the upgrade process. Telephony services will be stopped during the process
- When finished, check that all services are running (the list is displayed at the end of the upgrade).
- Check that services are correctly working like SIP registration, ISDN link status, internal/incoming/outgoing calls, Wazo Client connections etc.
When upgrading from Wazo 18.03, you should follow the specific procedure for Upgrading from Wazo 18.03.
Here are the steps for upgrading a cluster, i.e. two Wazo with high availability:
On the master : deactivate the database replication by commenting the cron in
On the slave, deactivate the xivo-check-master-status script cronjob by commenting the line in
On the slave, start the upgrade:
When the slave has finished, start the upgrade on the master:
When done, launch the database replication manually:
wazo-master:~$ xivo-master-slave-db-replication <slave ip>
Reactivate the cronjobs (see steps 1 and 2)
See our recommendation on how to upgrade to a specific version of Wazo
You may encounter the following error:
The following signatures were invalid: EXPKEYSIG 3F1BF7FC527FBC6A Wazo Release Key <email@example.com>
This error happens on all Wazo Platform servers installed before 21.01. See also: the issue ticket.
To fix the issue, run the following commands:
curl http://mirror.wazo.community/wazo_current.key | apt-key add - curl http://mirror.wazo.community/wazo_current.key | apt-key --keyring /etc/apt/trusted.gpg.d/wazo-keyring.gpg add - wazo-upgrade
When upgrading Wazo, if you encounter problems related to the system locale, see
If wazo-upgrade fails or aborts in mid-process, the system might end up in a faulty condition. If in doubt, run the following command to check the current state of Wazo's firewall rules:
If, among others, it displays something like the following line (notice the DROP and 5060):
0 0 DROP udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5060
Then your Wazo will not be able to register any SIP phones. In this case, you must delete the DROP rules with the following command:
iptables -D INPUT -p udp --dport 5060 -j DROP
Repeat this command until no more unwanted rules are left.