In Extoel SIP routing is failing
# ask-aib
billowy-hairdresser-80384
04/06/2026, 6:15 PMIn Extoel SIP routing is failing
✅ 1
t
tall-airline-16756
04/06/2026, 6:15 PMThanks for reaching out, Yethu. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
04/06/2026, 6:16 PMThanks — I’m sorry you’re seeing SIP routing fail in Extoel. I can help, but I need a few details to diagnose it.
Could you provide:
• Exact error messages or log excerpts (redact any secrets)
• Which component shows the failure (gateway, proxy, SBC, Extoel app)
• Time/timezone when it occurred and whether it’s recurring
• Recent config changes (routing rules, auth, DNS, TLS/SRTP)
• SIP transport/protocol in use (UDP/TCP/TLS) and ports
• Example of a failing call’s From/To and the expected route (anonymize identifiers if needed)
• Any network changes or firewall/NAT behavior you’ve observed
If you prefer, paste a short log snippet (SIP traces/INVITE→response) and I’ll point out the likely root cause and next steps.
, with interactive elements
b
billowy-hairdresser-80384
04/06/2026, 6:17 PMbut if I purchase the number from livekit and connect it via my trunl it is working perfectly
sip transport I test with tcp and tls also region pinning was india
t
tall-airline-16756
04/06/2026, 6:18 PMThanks — that’s useful context. Since LiveKit numbers + your Trunl work but Exotel routing fails, let’s narrow the difference.
Could you share the following so I can pinpoint the problem?
• Exotel SIP trunk settings you’re using in LiveKit (SIP URI, auth type, IPs/ports, TLS cert/SNI if used)
• The exact SIP transport you tested with Exotel (TCP or TLS) and which port
• A short SIP trace or log snippet of a failed INVITE→response (redact secrets)
• What response/code do you see from Exotel (e.g., 403, 404, 480, TLS handshake error)
• Are caller ID / From header values identical between the working Trunl setup and the failing Exotel calls?
• Any firewall/NAT differences or allowed IP lists configured for Exotel vs Trunl
• Confirm region pinning is set to ap-south for the Exotel trunk
Quick checks you can do now:
• Verify Exotel’s SIP credentials and transport/port exactly match LiveKit trunk config.
• If using TLS, confirm the certificate and SNI Exotel expects and that LiveKit is sending correct SNI.
• Ensure Exotel allows inbound calls from LiveKit IPs and that any caller-ID passthrough rules aren’t blocking the call.
Send the trunk settings + a short log and I’ll analyze the trace and recommend the precise fix.
Sources: Introducing LiveKit Phone Numbers: zero to ringing in 60 seconds | LiveKit | LiveKit Phone Numbers | Connect voice agents to phone lines | LiveKit | Agents telephony integration | LiveKit Documentation | Understanding TLS in SIP | LiveKit | Building Performant Voice Agents in India | LiveKit, with interactive elements