To keep a self-hosted LiveKit SIP deployment recoverable, redeploy the SIP service from saved configuration, keep it connected to the same Redis service as LiveKit, preserve Redis data using storage and backup settings appropriate to your Redis deployment, and keep trunk and dispatch-rule definitions in an external source of truth that you can inspect and restore through the SIP API. A volume mounted into the SIP container does not, by itself, establish that API-managed trunks or rules will persist.
What needs to persist
There are four separate pieces to account for. Treating them as one “SIP container state” is a common reason a deployment appears to recover while calls no longer work.
As an Amazon Associate I earn from qualifying purchases.
- SIP service configuration: the settings used to run the separate SIP service, including its LiveKit connection, Redis endpoint, ports, and logging.
- Redis service and data: SIP communicates with LiveKit through Redis, and the SIP service README says Redis stores SIP session state. The SIP service and LiveKit should use the same Redis service. LiveKit SIP service README
- Trunks and dispatch rules: these are resources managed through LiveKit’s SIP APIs. Keep their desired definitions somewhere outside the container so you can inspect or recreate them. LiveKit SIP APIs
- Host networking: the firewall, routing, and public-address behavior that allow SIP signaling and media traffic to reach the host.
LiveKit’s documentation describes how to configure the SIP service and manage API resources, but does not make an unconditional guarantee that trunk and dispatch-rule definitions survive every combination of container recreation, host reboot, Redis replacement, or Redis data loss. After recovery, check the actual resource state rather than assuming it.
Make the SIP service reproducible
Keep the SIP YAML or environment configuration in deployment configuration or a mounted file, rather than relying on changes made only inside a running container. The self-hosted SIP server guide shows configuration for API credentials, the LiveKit WebSocket URL, Redis address, SIP port, RTP range, external-IP behavior, and logging.
#1 Best Overall
- Dual band router upgrades to 1200 Mbps high speed internet (300mbps for 2.4GHz plus 900Mbps for 5GHz), reducing buffering and ideal for 4K stream
- Full Gigabit Ports - Gigabit Router with 4 Gigabit LAN ports, ideal for any internet plan and allow you to directly connect your wired devices
- Boosted Coverage - Four external antennas equipped with Beamforming technology extend and concentrate the Wi-Fi signals
- MU-MIMO technology - (5GHz band) allows high speeds for multiple devices simultaneously
- Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home
Put credentials in an appropriate secret store; do not commit them in plaintext alongside ordinary deployment settings. When the container is recreated, confirm that the replacement uses the intended configuration, Redis address, credentials, and database selection for your deployment.
Keep Redis data attached and protected
LiveKit’s SIP Docker Compose example declares a named redis_data volume for Redis’s /data directory. If you use that pattern, ensure the same named volume is attached when Redis is recreated and after the host reboots. A new or accidentally different volume is not the original Redis data.
Rank #2
- 【Five Gigabit Ports】1 Gigabit WAN Port plus 2 Gigabit WAN/LAN Ports plus 2 Gigabit LAN Port. Up to 3 WAN ports optimize bandwidth usage through one device.
- 【One USB WAN Port】Mobile broadband via 4G/3G modem is supported for WAN backup by connecting to the USB port. For complete list of compatible 4G/3G modems, please visit TP-Link website.
- 【Abundant Security Features】Advanced firewall policies, DoS defense, IP/MAC/URL filtering, speed test and more security functions protect your network and data.
- 【Highly Secure VPN】Supports up to 20× LAN-to-LAN IPsec, 16× OpenVPN, 16× L2TP, and 16× PPTP VPN connections.
- Security - SPI Firewall, VPN Pass through, FTP/H.323/PPTP/SIP/IPsec ALG, DoS Defence, Ping of Death and Local Management. Standards and Protocols IEEE 802.3, 802.3u, 802.3ab, IEEE 802.3x, IEEE 802.1q
A persistent volume helps retain data across container recreation, but it is not a verified backup. Arrange backup and restore procedures appropriate to the Redis distribution and hosting environment if you need recovery from disk failure, host loss, or accidental data deletion. The SIP documentation does not prescribe one universal Redis backup policy.
Preserve API-managed trunks and dispatch rules
Store the desired inbound or outbound trunk and dispatch-rule definitions outside the SIP container. Use the SIP API, SDK, or CLI available to your deployment to list and manage those resources, and make restoration or reconciliation a controlled part of rebuilding the environment. The API documentation covers resource management; it should not be confused with a guarantee about how every backend-loss scenario is recovered.
Rank #3
- Dual-band Wi-Fi with 5 GHz speeds up to 867 Mbps and 2.4 GHz speeds up to 300 Mbps, delivering 1200 Mbps of total bandwidth¹. Dual-band routers do not support 6 GHz. Performance varies by conditions, distance to devices, and obstacles such as walls.
- Covers up to 1,000 sq. ft. with four external antennas for stable wireless connections and optimal coverage.
- Supports IGMP Proxy/Snooping, Bridge and Tag VLAN to optimize IPTV streaming
- Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home
- Advanced Security with WPA3 - The latest Wi-Fi security protocol, WPA3, brings new capabilities to improve cybersecurity in personal networks
For outbound calling, distinguish a stored trunk from inline outbound configuration. A stored trunk is intended for settings reused across calls; inline configuration is available for call-specific settings. LiveKit describes stored trunks as long-lived configuration objects that it caches and reuses, and recommends reusing them rather than creating a new outbound trunk for every call. LiveKit SIP outbound trunk documentation
| Choice | When it fits | Persistence consideration |
|---|---|---|
| Stored trunk | Use when trunk settings are reused across calls. | Keep its desired definition outside the SIP container and inspect it through the SIP API after recovery. |
| Inline outbound configuration | Use for call-specific outbound settings. | It does not replace preserving service dependencies or checking API-managed resources after recovery. |
Choose a deployment pattern without confusing it with persistence
The SIP service can be run with Docker Compose or as a native binary. Either way, the key distinction is the same: the SIP process has runtime configuration, Redis is a separate dependency with its own data lifecycle, and trunks and dispatch rules are API-managed resources.
Rank #4
- DUAL-BAND WIFI 6 ROUTER: Wi-Fi 6(802.11ax) technology achieves faster speeds, greater capacity and reduced network congestion compared to the previous gen. All WiFi routers require a separate modem. Dual-Band WiFi routers do not support the 6 GHz band.
- AX1800: Enjoy smoother and more stable streaming, gaming, downloading with 1.8 Gbps total bandwidth (up to 1200 Mbps on 5 GHz and up to 574 Mbps on 2.4 GHz). Performance varies by conditions, distance to devices, and obstacles such as walls.
- CONNECT MORE DEVICES: Wi-Fi 6 technology communicates more data to more devices simultaneously using revolutionary OFDMA technology
- EXTENSIVE COVERAGE: Achieve the strong, reliable WiFi coverage with Archer AX1800 as it focuses signal strength to your devices far away using Beamforming technology, 4 high-gain antennas and an advanced front-end module (FEM) chipset
- OUR CYBERSECURITY COMMITMENT: TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
| Pattern | What to declare and restart | What to verify separately |
|---|---|---|
| Docker Compose | Declare the SIP service configuration and container lifecycle in Compose; retain the intended Redis volume attachment if Redis is also managed there. | Check that the same Redis data is in use, API resources are present, and host or cloud firewall rules still expose required traffic. |
| Native SIP binary | Keep the configuration file and process-supervisor settings available for restart after reboot. | Check the external Redis service, API-managed resources, and host or cloud firewall rules independently. |
Neither a Compose restart policy nor a native process supervisor is a substitute for backing up Redis data or retaining the desired trunk and rule definitions.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Check network access after a reboot
For the documented self-hosted setup, LiveKit says SIP signaling port 5060 and the media range 10000–20000 must be accessible from the Internet. Check host and cloud firewall rules, routing, public-address behavior, and UDP reachability as applicable to your deployment. A reboot or infrastructure change can alter an address or firewall attachment even when the containers and their configuration return successfully.
Quick Recap
Best Value
- Next-Gen Gigabit Wi-Fi 6 Speeds: 2402 Mbps on 5 GHz and 574 Mbps on 2.4 GHz bands ensure smoother streaming and faster downloads; support VPN server and VPN client¹
- A More Responsive Experience: Enjoy smooth gaming, video streaming, and live feeds simultaneously. OFDMA makes your Wi-Fi stronger by allowing multiple clients to share one band at the same time, cutting latency and jitter.²
- Expanded Wi-Fi Coverage: 4 high-gain external antennas and Beamforming technology combine to extend strong, reliable, Wi-Fi throughout your home.
- Improved Battery Life: Target Wake Time helps your devices to communicate efficiently while consuming less power.
- Improved Cooling Design: No heat ups, no throttles. A larger heat sink and redefined case design cools the WiFi 6 system and enables your network to stay at top speeds in more versatile environments.
Recovery checklist
- Recreate or restart the SIP service from its saved deployment configuration, including the intended LiveKit URL and Redis connection settings.
- Confirm LiveKit and the SIP service connect to the intended Redis service, with the expected credentials and database selection.
- Confirm Redis is using the expected persistent data location and, when restoring after a failure, restore from the appropriate backup.
- Use the SIP API to list expected trunks and dispatch rules. Reconcile missing resources from the saved desired definitions.
- Check that SIP signaling and media traffic can reach the host on the documented ports for your deployment.
- Place an inbound or outbound test call when appropriate, and investigate API resource state, Redis connectivity, and network reachability separately if it fails.
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.
