Ciaran
09/14/2026, 4:32 PMAI Evy
09/14/2026, 4:32 PMAI Evy
09/14/2026, 4:32 PMAI Evy
09/14/2026, 4:32 PMsip:sip.retellai.com [(1) ]() [(2) ]() .
If your trunk's origination URI is currently set to a sip.livekit.cloud address, you'll need to update it in Twilio to sip:sip.retellai.com instead [(1) ]() . This handles inbound calls flowing from Twilio into Retell [(2) ]() .
Note that origination and termination are configured separately :
- **Origination (inbound) **: calls from Twilio into Retell — set this to sip:sip.retellai.com [(1) ]() [(2) ]()
- **Termination (outbound) **: calls from Retell out through Twilio — Twilio gives you a termination SIP URI, which you then supply to Retell when importing the number (not something you change on Twilio's side)
So updating the origination URI in your Twilio trunk settings to sip:sip.retellai.com should be the main step here [(1) ]() . Your termination setup and number import into Retell should remain unaffected unless the email specifies otherwise.
If you run into issues after switching, verify that your termination SIP URI doesn't contain extra spaces and that you're using a localized termination URI near your region .AI Evy
09/14/2026, 4:32 PMCiaran
09/14/2026, 4:33 PMAI Evy
09/14/2026, 4:33 PMAI Evy
09/14/2026, 4:33 PMsip:sip.retellai.com for inbound calls [(1) ]() , but it doesn't specify what priority or weight values to use for that trunk origination setting.
I don't have documented information on the correct Priority or Weight numbers for this Twilio configuration field. Since these are Twilio-side trunk settings, I can't confirm specific values from the sources available to me.
Check out these potentially useful sources: [Connect a Twilio number to Retell with elastic SIP trunking]() , [Elastic SIP Trunk Busy Signal]()
Would you like a general answer based on my broader knowledge instead?AI Evy
09/14/2026, 4:33 PMAI Evy
09/14/2026, 4:33 PM