LiveKit documents APIs for listing and creating SIP trunks, but the cited documentation does not describe a one-command backup or restore feature. You can build a repeatable recovery process by exporting inbound and outbound trunk records, versioning the returned JSON, and recreating each record with its matching create operation. Keep credentials and provider-side settings in their own secure records: a trunk-list response is not established as a complete credential backup.
What this backup covers—and what it does not
This workflow is for stored SIP trunk objects managed through LiveKit Cloud’s SIP APIs. LiveKit describes those APIs as tools to manage SIP trunks, dispatch rules, and SIP participants in its SIP API documentation. Listing and recreating trunk records can preserve their LiveKit-side settings, but it does not necessarily capture the full telephony connection.
As an Amazon Associate I earn from qualifying purchases.
- Separate provider configuration: A SIP provider may have its own trunk, origination URI, authentication, and number-association settings. LiveKit’s SIP trunk setup guide describes configuring an external provider, associating a number, and directing it to a LiveKit SIP endpoint. The Twilio integration guide documents provider-side origination and outbound authentication separately.
- Credentials: LiveKit’s API models include authentication fields such as
auth_usernameandauth_password, but the cited documentation does not say whether list responses return or redact password values. Do not treat exported JSON as a complete secrets backup. - Deployment context: LiveKit Cloud trunk objects and self-hosted SIP server YAML configuration are distinct contexts in the documentation. This API workflow is not a substitute for backing up self-hosted deployment configuration; follow your infrastructure process for that environment. See the SIP server guide.
Before you export
Identify the exact LiveKit project and environment you intend to protect. LiveKit CLI project references include a project URL, API key, API secret, and name, and the CLI documentation covers authentication and project linking. Use an appropriately restricted credential with SIP admin permission for API operations, and avoid pointing recovery commands at a different project by mistake.
Decide where to keep the exported files, who can access them, and how secrets will be stored separately. Use your organization’s approved secret manager or equivalent secure system for trunk credentials and provider-side secrets.
#1 Best Overall
- Single Port Connectivity: Supports 1 SIP profile through a single FXS port and a single 10/100Mbps port
- Advanced Security Features: TLS and SRTP security encryption technology to protect calls and accounts
- Flexible Provisioning Options: Automated provisioning options include TR-069 and XML config files
- Multi-Party Conferencing: Supports 3-way voice conferencing for enhanced communication capabilities
- Reliable Failover Protection: Failover SIP server automatically switches to secondary server if main server loses connection
Export the inbound and outbound trunk records
LiveKit documents ListSIPInboundTrunk and trunk creation methods in the SIP API reference. For outbound trunks, the outbound trunk guide describes ListSIPOutboundTrunk for querying trunk parameters and CreateSIPOutboundTrunk for creating stored records. The API is available at /twirp/livekit.SIP/<MethodName>, accepts POST requests with JSON bodies, and uses signed access tokens; consult the API reference and your SDK or CLI version for the exact request and response shape.
- Authenticate to the intended project. Use a signed token with SIP admin permission and verify the project URL and identity before making requests.
- List inbound trunks. Call
ListSIPInboundTrunkusing the syntax supported by your SDK, CLI, or direct API client. - List outbound trunks. Call
ListSIPOutboundTrunkusing the same project and authorization context. - Save the unmodified responses. Store the inbound and outbound results as separate JSON files. Record the retrieval time, project/environment identity, and tool or SDK version alongside them, then commit or archive them in your versioned configuration system with access controls.
- Inventory what is outside those responses. Record provider-side settings, number associations, trunk identifiers, and credential references in the systems appropriate to them. Check whether the particular API version returns, omits, or redacts password fields instead of assuming the export includes them.
Inbound and outbound trunks do not share one configuration shape. Inbound settings can include phone numbers, access restrictions or authentication, headers, timeouts, and media configuration. Outbound settings can include provider address, destination country, caller ID numbers, transport, and optional credentials. Preserve the response for each type without trying to convert one into the other.
Rank #2
- Supports 2 SIP profiles through 2 FXS ports and a single 10/100Mbps port
- TLS and SRTP security encryption technology to protect calls and accounts
- Automated provisioning options include TR-069 and XML config files
- LED indicators - POWER, NET, PHONE1, PHONE2 Supports 3-way voice conferencing Failover SIP server automatically switches to secondary server if main server loses connection
- Supports T.38 Fax for creating Fax-over-IP
Restore trunks from a saved export
Restoration is an operator-built use of the documented create methods, not a documented atomic restore operation. The cited pages do not promise that a sequence of creates recreates a point-in-time snapshot, or prescribe a rollback procedure. Restore deliberately, with the target project and provider configuration confirmed first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Confirm the target. Check the LiveKit project and environment against the backup metadata. Confirm that provider-side trunks, origination settings, and number associations are available or have been restored through their own process.
- Resolve secrets separately. Retrieve credentials from the approved secret store. Populate or supply them according to the matching API schema and SDK version; do not depend on passwords being present in the list output.
- Recreate inbound records. Use the documented inbound trunk create operation for each saved inbound configuration, reviewing phone numbers, authentication or access restrictions, headers, timeout, and media fields before submission.
- Recreate outbound records. Use
CreateSIPOutboundTrunkfor each saved outbound configuration. Check the provider address, destination country, caller ID numbers, transport, and required credentials against the intended environment. - Inspect and validate. List the trunks again and compare the resulting records with the saved settings. Then validate inbound and outbound calls using your deployment’s normal checks, including provider connectivity and number routing.
Exact create-request fields and behavior can vary with the SDK/API version in use. Follow the current API reference for required fields and verify the response after each operation rather than assuming a saved list response can be replayed unchanged.
Rank #3
- Supports 2 SIP profiles and 2 FXS ports
- Strong AES encryption with security certificate per unit
- Supports T.38 Fax for reliable Fax-over-IP
- High performance NAT router
- 3-way voice conferencing per port
Choose an operating method that fits your recovery process
The documented management route for stored trunk records is through LiveKit’s API, SDK, or CLI; the dashboard is also a documented route for configuring LiveKit Cloud. The cited sources do not describe a built-in export/restore feature.
Quick Recap
Best Value
- Seamless Analog-to-VoIP Integration: Supports 2 SIP profiles through 1 FXS port and 1 FXO port, enabling you to connect traditional analog phones and fax machines to modern VoIP networks without replacing existing equipment
- Enhanced Communication Capabilities: 3-way voice conferencing per port allows multiple participants on calls; dual 100Mbps LAN and WAN ports provide flexible network connectivity for small offices and home-based businesses
- Universal Device Compatibility: Works with laptops, personal computers, smartphones, and tablets via 802.11a wireless standard and RJ11 connectivity, making it easy to integrate into existing office infrastructure
Rank #4
- Fanvil SIP Paging Gateway PA2S
- Emergency call button interface, active call
- NVR video recording, standard RJ45 interface
- Recording output, 3.5mm standard audio interface
- Audio line out port, expandable external active speaker
| Method | Useful when | What to account for |
|---|---|---|
| API, SDK, or CLI workflow | You want repeatable, versioned exports and a recovery process that can be reviewed or automated. | Target the right project, handle signed-token permissions, keep secrets separately, and track provider-side configuration outside the trunk record. |
| Cloud dashboard | You configure trunks interactively or need to inspect settings manually. | The cited documentation does not establish a dashboard-based bulk export/restore feature. Maintain an independent record of configuration and external provider settings. |
Practical safeguards
- Store exported JSON and secret material with different access controls; avoid placing plaintext passwords in a broadly accessible repository.
- Keep the project/environment identity, retrieval time, and the relevant SDK or API version with each backup so an operator can select the right record set during recovery.
- Document provider settings and phone-number associations alongside, but separately from, the LiveKit trunk JSON.
- Test the restore steps with the API version and permissions intended for production recovery; the documentation does not guarantee that a list response is directly reusable as a create request.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
