Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Updates

The PBX is updated with apt, from the vendor’s signed repository. Nothing installs by itself: a new version is reported, and the operator chooses when to install it.

Declaring the repository

The vendor gives you the repository address (here https://repo.vendor.example):

sudo curl -fsSL https://repo.vendor.example/centrex-v3.gpg \
    -o /usr/share/keyrings/centrex-v3.gpg
sudo tee /etc/apt/sources.list.d/centrex-v3.sources >/dev/null <<'EOF'
Types: deb
URIs: https://repo.vendor.example
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/centrex-v3.gpg
EOF
sudo apt update

Being notified

The package list refreshes every day. When a newer version is waiting:

  • the health card of the diagnostics shows the installed version and the waiting one;
  • the centrex_mise_a_jour_disponible metric goes to 1 (MiseAJourDisponible alert, see Monitoring).

Updating

  1. Back up first (Backup).
  2. sudo apt update && sudo apt upgrade. The service restarts and applies the database migrations; live calls are cut: pick a quiet time.
  3. Check the health in the portal (Diagnostics page).

Before any migration, the PBX takes a snapshot of its own database in /var/backups/centrex-v3 (the last three are kept). It is not a full backup: neither the FusionPBX tables, nor the keyring, nor the files are in it.

In active/passive: the passive first, then centrex bascule ceder on the active (the promoted passive migrates the database), then the former active.

Going back to an earlier version

sudo apt install --allow-downgrades centrex-v3=<version>

The package of the target version first brings the database back to its schema, using the binary still installed; if this fails, the installed version is kept and restarts. Going back destroys the data of the undone migrations (the snapshot keeps it): make a full backup first. In active/passive, go back on the active.

Settings after an update

/etc/centrex-v3/centrex.env is never rewritten by an update, and no question is asked. A new setting, always optional, appears commented out in the template /usr/share/centrex-v3/centrex.env: compare it with your settings after an update.