Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →If a LiveKit SIP trunk appears to disappear after a container recreate or host reboot, first identify what is actually missing: a stored trunk record, the self-hosted SIP server container, or call connectivity. Those are separate layers with different fixes. A container restart does not, by itself, establish that a stored trunk was deleted.
First identify what “SIP trunk” means in the error
LiveKit uses SIP in two distinct ways that can look like the same problem during troubleshooting:
- Self-hosted SIP server: a separately deployed service or container that handles telephony. LiveKit’s self-hosted SIP guide shows the SIP service running alongside LiveKit and connected to Redis.
- Stored trunk: an inbound or outbound configuration object managed through LiveKit’s SIP APIs. This record is not the SIP server process. See the SIP documentation and outbound trunk guide.
Capture the exact error and decide whether it identifies a trunk ID or says the SIP service is absent, stopped, or not ready. If the error is twirp error unknown: object cannot be found, LiveKit’s SIP troubleshooting guide says: “Trunk ID references a trunk that doesn’t exist or is inaccessible.” That points first to the referenced object or access to it—not automatically to a container failure.
If a stored trunk ID cannot be found
Check the trunk in the same LiveKit environment
For an outbound trunk, query the SIP API using ListSIPOutboundTrunk and compare the returned IDs with the ID your application is using. Confirm the request targets the intended LiveKit project or deployment; an ID from one environment will not establish that a matching object exists in another. The API is documented in the SIP API reference.
#1 Best Overall
- The phone only works with VoIP
- 2 dual-color line keys (with 2 SIP accounts and up to 2 call appearances), 3 XML programmable context-sensitive soft keys, 3-way conference
- HD wideband audio, superb full-duplex hands-free speakerphone with advanced acoustic echo cancellation and excellent double-talk performance.
- Large phonebook (up to 500 contacts) and call history - up to 200 records
- Automated provisioning using TR-069 or encrypted XML configuration file, SRTP and TLS for advanced security protection, 802.1x for media access control
For inbound calls, check the inbound trunk and the associated dispatch rule. LiveKit’s incoming-call guide describes both parts of the flow. The documented Phone Numbers feature is an exception to creating an inbound trunk.
Verify the ID and API permission
- Confirm that the exact trunk ID is current and was created in the project or deployment receiving the failing request.
- Check that the trunk exists and is accessible to the request’s credentials. LiveKit’s SIP API documentation says SIP API requests require SIP admin permission unless an endpoint specifies otherwise.
- Confirm how the call was configured. A stored trunk ID and inline per-call trunk configuration are different approaches; an application expecting a stored object should not assume an inline configuration created one.
Do not infer from the timing of a reboot or container recreate that the stored trunk was deleted. The error and API lookup can establish whether the object is present and reachable, but the timing alone does not identify a cause.
Rank #2
- Dual-Band Wi-Fi 6: Enjoy seamless wireless connectivity with the latest Wi-Fi 6 technology, providing faster speeds and improved coverage.
- Cordless Convenience: This cordless phone offers the freedom to move around while on a call, without being tethered to a base station.
- Large Color Display: The
- 4-inch color LCD screen provides a clear and vibrant interface for easy navigation and call management.
- Intuitive Controls: The phone features a user-friendly keypad and navigation buttons for effortless operation.
If the self-hosted SIP server container is missing
When the SIP process itself is absent or not starting, troubleshoot the deployment rather than the trunk ID. LiveKit’s sample Compose setup runs a separate SIP service connected to LiveKit and Redis; your own orchestration and persistence choices may differ.
- Inspect desired state. In Docker Compose, an orchestrator, or your host service manager, check whether the SIP service is still defined and configured to start. A recreated container may not return if it is no longer part of the active deployment configuration.
- Check startup behavior and logs. Review the service’s restart policy or orchestrator status, then inspect logs around startup for configuration, connection, or credential errors.
- Validate mounted configuration. Confirm the SIP service can read its configuration and that the configured LiveKit WebSocket URL, API credentials, and Redis address are correct for this deployment.
- Check the host’s service manager if applicable. LiveKit’s VM deployment guide documents one setup using configuration under
/opt/livekitand alivekit-dockersystemd service. These paths apply to that documented setup, not necessarily to every installation.
If the container is running but calls still fail, move on to network reachability. A missing API record and an unreachable SIP or media port are different problems.
Rank #3
- 5V/2A Power Supply Included - PoE support
- 4.3″ 480 x 272-pixel color display with backlight - Adjustable LCD screen
- Built-in Bluetooth 4.2
- Built-in dual-band 2.4G/5G Wi-Fi (802.11a/b/g/n/ac)
- USB 2.0 port for USB recording, wired/wireless USB headsets, and EXP50
If the service is running but calls still fail
For the documented self-hosted SIP setup, LiveKit identifies signaling on port 5060 and RTP media on ports 10000–20000 by default. Verify the values in your actual configuration and confirm that the relevant ports are reachable through host firewalls and network policy. LiveKit’s ports and firewall guide provides additional context.
These are call-connectivity checks. A firewall problem can prevent signaling or media traffic, but the documentation does not identify it as a cause of a stored trunk object disappearing from the SIP API.
Rank #4
- Supports 4 SIP accounts and 4 multi-purpose line keys
- Swappable faceplate to allow for easy logo customization
- GRP2612W includes built-in dual-band Wi-Fi support. Ethernet cord must be disconnected to enable Wi-Fi capability
- HD audio supporting all major codecs, including wideband codecs G.722 and Opus Up to 16 digital BLF Keys
- Enterprise-level protection including secure boot, dual firmware images, and encrypted data storage
Cloud and self-hosted deployments have different recovery paths
| What is missing? | Where to investigate | First useful check |
|---|---|---|
| Stored trunk record | SIP API in the intended LiveKit project or deployment | Query the relevant trunk, verify its ID, and confirm API permission. |
| Self-hosted SIP server | Your container or host orchestration | Check desired state, startup status, mounted configuration, and logs. |
| Call signaling or media | Configured network path and firewall | Verify actual signaling and RTP port settings and reachability. |
| Managed LiveKit Cloud telephony service | Cloud project configuration and SIP API state | Check the stored object and request context; do not apply self-hosted container recovery steps to a managed service. |
LiveKit describes SIP as a separately deployed service for self-hosted telephony, while Cloud provides telephony as a managed offering in its self-hosting overview. Establish which deployment model you use before following host-specific steps.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to include when escalating the issue
If the cause remains unclear, provide enough detail to distinguish the missing layer without exposing secrets:
Quick Recap
Best Value
- Mid-level phone, ideal for professionals and managers with moderate call load
- Ergonomic design with adjustable display
- Built-in Bluetooth, Wi-Fi
- Whether the deployment is LiveKit Cloud or self-hosted, and whether it uses Compose, Helm, systemd, or another orchestrator.
- What was recreated or rebooted, and whether the SIP service is currently present and healthy.
- The exact error text and whether it names an inbound or outbound trunk ID.
- Whether the trunk is stored or configured inline, and how it was created.
- Sanitized relevant configuration and logs around service startup or API lookup. Remove API secrets and other credentials.
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.
