Hi i have added a trunk in livekit but outbound calls are not happening how to handle SIP proxy address

Thanks for reaching out, Vishalli. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

i have created using ui and doesn’t seem to register to our platform.

Thanks — that helps. Since you created the trunk in the UI and it’s not registering to your platform, the problem is most likely a registration/connectivity or credential mismatch between LiveKit’s outbound trunk settings and your SIP provider. A few quick clarifying questions so I can give exact steps: 1. Which SIP provider or platform are you trying to register the trunk with? (e.g., Twilio, Broadsoft, an on-prem PBX) 2. In the UI trunk settings, which fields did you fill for the SIP proxy? Please share a redacted screenshot or copy of these fields (hide passwords/keys). I’m specifically looking for: proxy/host, port, transport (UDP/TCP/TLS), username, password, and realm/domain. 3. Do you see any registration or SIP messages in LiveKit logs (for example, SIP REGISTER attempts, 401/403/408 responses, or connection timeouts)? If yes, paste the relevant lines. 4. Can you confirm LiveKit’s host can reach your SIP proxy address and port? (If you can, try a connectivity test from the LiveKit host such as a TCP/TLS check to proxy:port and tell me the result.) 5. Is your SIP platform expecting inbound registrations from a specific IP or with TLS certificates (mutual TLS)? If so, do you have those allowed/installed? Troubleshooting steps you can try now • Verify proxy/port/transport: make sure the proxy host, port, and transport match what your SIP provider requires. Mismatched transport (e.g., TLS required but set to UDP) prevents registration. • Check credentials and realm: incorrect username/password or wrong realm will cause 401/403 responses — look for those in logs. • Test network reachability from LiveKit: confirm DNS resolves the proxy and the port is open (e.g., using a TCP connect or openssl s_client if TLS). • Look for SIP responses in logs: registration failures usually return SIP status codes that point to the cause (401 = auth required, 403 = forbidden, 408 = timeout). • Confirm provider-side settings: ensure your SIP provider is configured to accept registrations from your LiveKit instance (some providers require you to whitelist the client IP or create a credential record on their side). What I’ll do next once you share the items above • Review the redacted UI settings and logs you provide. • Tell you exactly which UI fields to change (and how) to get the trunk to register. • If it’s a network or provider-side block, I’ll give the specific tests and evidence you can share with your SIP provider to resolve it. Send the redacted trunk fields and any registration log lines and I’ll guide the next steps.

image.png

Thanks — that screenshot is helpful. You’ve confirmed the trunk is created in the UI with Address =

<http://tkreg.a4uc.com.au|tkreg.a4uc.com.au>

, Transport = TCP, and direction = Outbound, and it’s not registering to your platform. I’ll help you narrow this down and get it registered. What I’m focusing on: registration/connectivity and credential mismatch between the LiveKit outbound trunk settings and your SIP platform. Please provide these items so I can give exact changes: 1. Which SIP platform/provider is

<http://tkreg.a4uc.com.au|tkreg.a4uc.com.au>

for (example: BroadSoft, an on‑prem PBX, Twilio, etc.)? 2. In the UI’s Optional settings (open that section) — what fields are set for username, password, realm/domain, port, and registration interval? Please paste a redacted copy of those values (hide the password). 3. Do you expect the trunk to REGISTER to the provider (i.e., a SIP REGISTER flow), or is the provider expecting calls via static IP/ACL (no REGISTER)? 4. From the LiveKit host, can you test reachability to

<http://tkreg.a4uc.com.au|tkreg.a4uc.com.au>

on the SIP port? Useful quick checks: ◦ DNS resolution for

<http://tkreg.a4uc.com.au|tkreg.a4uc.com.au>

◦ TCP connect to the expected port (for example

telnet <http://tkreg.a4uc.com.au|tkreg.a4uc.com.au> 5060

or

openssl s_client -connect <http://tkreg.a4uc.com.au:5061|tkreg.a4uc.com.au:5061>

if TLS) Tell me the results or any errors you see. 1. Do you see any registration attempts or SIP responses in LiveKit logs? Look for REGISTER messages or SIP status codes (401, 403, 408, etc.). If yes, paste the relevant log lines (redact secrets). Immediate checks you can run now • Confirm transport: If the provider requires TLS or UDP, using TCP will prevent registration. Verify whether transport should be UDP/TCP/TLS and switch the UI setting accordingly. • Confirm port: Some providers use nonstandard ports (e.g., 5061 for TLS). Make sure the trunk uses the correct port. • Confirm credentials/realm: Wrong username/realm/password causes 401/403 responses. Check the Optional settings for these fields. • Network reachability: Ensure LiveKit can reach the provider host/port (firewall, VPC rules, or NAT may block outbound SIP). A successful TCP/TLS connect proves basic connectivity. If the provider requires registration from a known IP range or mutual TLS: • Make sure your LiveKit host’s public IP is whitelisted with the provider, or • Ensure required client certificates are installed if mutual TLS is needed. What I’ll do once you send the requested info • Review the UI fields and logs you provide and tell you exactly which UI fields to change (transport, port, auth fields). • Interpret any SIP response codes from logs and recommend fixes. • Give network test commands and expected results to prove connectivity or identify blocking points. Send the redacted Optional settings and any log lines or test results and I’ll guide the next precise steps. Sources: Making calls overview | LiveKit Documentation