Skip to main content

Upgrading the Call Telemetry Appliance

Upgrading takes one command over SSH. Pick your path:

Can your appliance reach the internet?Do this
YesFollow the online upgrade below.
No — air-gapped or restricted networkUse Call Telemetry Appliance Manager to build an offline bundle on a connected workstation and apply it to the appliance.

Online Upgrade​

Three Steps

1

SSH into the appliance

Management SSH runs on port 2222. Port 22 is SFTP for CDR delivery only.

ssh calltelemetry@your-server -p 2222
2

Run the upgrade

Copy the command for the channel you want. Each pins the exact current tip from the release markers.

Upgrade to Stable 0.8.6.27

Production channel — exact current Stable tip

sudo curl https://get.calltelemetry.com | sudo sh -s -- update 0.8.6.27
Upgrade to Beta 0.8.7.499

Next-release channel — exact current Beta tip

sudo curl https://get.calltelemetry.com | sudo sh -s -- update 0.8.7.499
3

Verify

Log in to the web UI and confirm the new version number is running.

If Something Goes Wrong

Rollback

Revert to the previous version after a failed upgrade

sudo curl https://get.calltelemetry.com | sudo sh -s -- rollback
Migration Status

Check database migration progress

sudo curl https://get.calltelemetry.com | sudo sh -s -- migration_status
Run Migrations Manually

Retry a stuck database migration

sudo curl https://get.calltelemetry.com | sudo sh -s -- migration_run
View Logs

Stream application logs for debugging

sudo docker logs calltelemetry-web -f
Create Backup

Back up the database — run this before upgrading if you want a restore point

sudo curl https://get.calltelemetry.com | sudo sh -s -- backup
Firewall Requirements

The upgrade downloads over outbound HTTPS from get.calltelemetry.com and Docker Hub. See Appliance Firewall Requirements for the hosts to allow.

Need Help?​

Email support@calltelemetry.com.

For database operations, system maintenance, and the full command set, see the CLI Reference Guide.

Kubernetes​

Kubernetes deployments upgrade through Helm, not the appliance script. See the Kubernetes Deployment Guide.