Skip to main content

Backup and restore of the telephony

Navin Enterprise is the source of truth of the telephony configuration: a publication rebuilds the managed files of Asterisk and the tables of Kamailio from its tables. The service backups keep what cannot be rebuilt.

What the Manager backs up​

ServiceBackupContent
asteriskasterisk-filesconfiguration directory (system files and *_navin.conf files), astdb database, keys and voicemail spool of the first node; the recordings are not in it, Navin Enterprise moved them to SeaweedFS
kamailiokamailio-htablesJSON export through JSONRPC of the tables tenant_domains, did_routes, trunk_hosts and tenant_limits of the first instance; the transient ipban table is not kept
rtpengine, livekit-sip, livekit-egress, livekit-ingress, livekit-agentsnoneservices without state of their own: their configuration comes from the descriptor and the bindings

The backups are run and scheduled from the Backup and DR page of the Manager console, as for the other services.

Data of Navin Enterprise​

  • PostgreSQL (schema eai): telephony tenants, pools, trunks, numbers, extensions, rules, IVRs and their versions, queues, agents, published versions, call sessions and events, index of the recordings, quotas. These data follow the existing PostgreSQL backup.
  • SeaweedFS (bucket navin-telephony): encrypted recordings, voicemail messages, IVR prompts, conference and AI agent recordings. They follow the existing replication and backups of SeaweedFS.
  • Vault: SIP, AMI, ARI, JSONRPC and WebRTC secrets, in the backup of the existing vault.

Restore order​

  1. Restore PostgreSQL, the vault and SeaweedFS (existing procedures).
  2. Restore or reinstall asterisk through the Manager, then restore its asterisk-files backup.
  3. Restore or reinstall kamailio; its kamailio-htables backup writes the tables back through htable.sets and htable.seti.
  4. Reinstall the LiveKit services and the workers through the Manager.
  5. In the portal, Publication: publish the pool, or POST /v1/telephony/pbx-pools/{id}/reconcile, so that the engines carry the published version again.

Verification​

  • The publication preview shows no difference with the published version.
  • The test calls of the scenario matrix (docs/en/guides/telephony/scenarios.md) succeed.
  • The restored recordings play through a signed URL.