https://livekit.io logo
Join Slack
Powered by
I used to be able to dial livekit from twilio usin...
# ask-ai
s
I used to be able to dial livekit from twilio using
Copy code
<?xml version="1.0" encoding="UTF-8"?><Response><Dial><Sip>sip:+1959...@5q....sip.livekit.cloud</Sip></Dial><Hangup /></Response>
but from today it doesn't work anymore. I can use the SIP trunk directly though. This is what Twilio says:
Copy code
Request timeout with sip:+1959...
Has something changed?
t
Thanks for reaching out, Marc. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I can see why that suddenly failing would be frustrating. You’re asking why your TwiML Dial to a room-specific SIP URI like 
sip:+1959...@5q....sip.livekit.cloud
now times out while calling the SIP trunk directly still works. Short answer: the direct dialing method using room-specific SIP URIs (e.g., 
...@<room>.sip.livekit.cloud
) is no longer supported. That approach was deprecated as part of LiveKit’s infrastructure/security update. The supported, reliable method is to route calls from Twilio to LiveKit using a configured LiveKit SIP trunk — which is why your SIP trunk calls continue to work. What you can do next • Continue using your Twilio number configured to forward to the LiveKit SIP trunk (this is the recommended solution). • If you want help migrating any TwiML or routing rules to the SIP trunk setup, tell me: ◦ the current TwiML you’re using (you already shared the Dial snippet which helps), ◦ whether you want calls mapped to specific LiveKit rooms, and ◦ any caller ID or SIP headers you need preserved. I can then give concrete steps or sample TwiML/SIP trunk configuration to achieve your desired behavior. If you’d like links or step-by-step guidance for setting up the Twilio → LiveKit SIP trunk route, tell me whether you prefer Twilio Console instructions or example TwiML and I’ll provide that next. Sources: Introducing LiveKit Phone Numbers: zero to ringing in 60 seconds | Accepting calls overview | LiveKit Documentation | Agents telephony integration | LiveKit Documentation
s
when did this happen? can you point to some release?
t
I don't have the answer you're looking for. You could also try asking your question: • in one of the other Slack channels or • to https://deepwiki.com/livekit/livekit_composite which is trained on all LiveKit source code If you find the answer, please post it here to help others!
s
you said the direct dialing method using room-specific SIP URIs (e.g., 
...@<room>.sip.livekit.cloud
) is no longer supported. That approach was deprecated as part of LiveKit’s infrastructure/security update. what update?
?
q
Hi @square-spoon-72769 can you confirm if you are still seeing this issue?
s
no, I don't. But I think you guys fixed something on your end
it was like 1h of 😱 but now it's solved
when editing the trunk I was seeing the password but NOT the username
I tried removing the username&password, or updating it to something else. I feel like it was something in that area
but in the end, I think I did not change anything relevant tbh @quaint-ambulance-32873
q
Thanks for confirming @square-spoon-72769
s
could you explain the issue?
q
We are investigating into this
👍 1
Hi Marc, We acknowledge your issue and we have updated the incident page. We highly recommend using TCP for signaling in case if you are using UDP.
s
How do I know if I'm using UDP?
t
You can check in the PCAP
s
interesting
Copy code
Contact: "+1..." <sip:+1...@172.25.72.214:5060;transport=udp>
and how can I change this? Is there some livekit docs page?
t
Here are relevant docs, 1, 2 UDP can suffer fragmentation with MTU issues and TCP is easier to debug.
s
I use Twilio
Twilio does not support TCP?
t
They should support it, these docs just happened to be on another telephoney provider.
s
yup, I asked the ask-ai bot again
do the answer is adding 
transport=tcp
to the sip URI
✅ 1
but @quaint-ambulance-32873, checking the calls from this morning, I see e.g. for https://cloud.livekit.io/projects/p_5qel53gckvs/telephony/SCL_TLZ3MK2nEs48/inbound
q
This is small frontend bug that we are fixing, I will step back the issue now, please send an email to support for further questiosn
👍 1
2 Views
Open in Slack
PreviousNext
Powered by