ancient-umbrella-90337
07/22/2025, 2:22 AMtall-airline-16756
07/22/2025, 2:22 AMtall-airline-16756
07/22/2025, 2:23 AMauth_username, and auth_password that match your SIP provider’s configuration.
• Check Dispatch Rules: Confirm that you have a dispatch rule associated with the correct trunk and that it matches the called number. Use lk sip dispatch list to review your rules.
• Phone Number Format: Make sure the phone number in your trunk configuration matches the format used by your SIP provider (including the leading + if required).
• IP Address Restrictions: If you have allowed_addresses set, ensure your SIP provider’s IP addresses are included. An empty list allows all IPs.
• SIP Provider Routing: Double-check that your SIP provider is routing calls to the correct LiveKit SIP URI and endpoint.
For diagnostics, you can:
• Run lk sip inbound list to verify your inbound trunk exists and is active
• Run lk sip dispatch list to confirm dispatch rules are present and correct
• Review your SIP provider’s logs for any routing or authentication errors
If you are using PIN-protected rooms, ensure the dispatch rule includes the correct PIN configuration and that callers are prompted to enter the PIN.
Systematically check each of these areas to identify where the workflow is breaking. If you need more targeted troubleshooting, please provide details such as your trunk and dispatch rule configuration, the phone number being called, and any error messages or logs from your SIP provider.
Sources: sip/sip_test.go | Accepting inbound calls | LiveKit Docs | Accepting incoming calls | LiveKit Docs