Skip to main content
  1. In Twilio Elastic SIP Trunking, add an Origination SIP URI in the form sip:<platform-sip-fqdn>;transport=tcp and assign the DID to the trunk.
  2. In the platform, enter the exact +E.164 DID and select Provider source IPs.
  3. Do not use platform inbound digest. Twilio credential lists authenticate customer-to-Twilio termination, not Twilio-to-platform origination.
Allow every Twilio regional signaling CIDR for failover:
Twilio documents UDP/TCP signaling on port 5060 and TLS on 5061. The list above is for signaling; do not substitute Twilio media ranges. For outbound calls, configure the Twilio termination domain and a Twilio credential list separately. A Twilio termination host normally follows <name>.pstn.twilio.com; do not paste an Origination SIP URI into that field.

​
Validate

Call the Twilio DID externally. Confirm a new inbound record, correct assistant routing, and two-way audio. A Twilio call log without a corresponding platform inbound call is not proof of delivery. Sources: LiveKit Twilio guide, Twilio signaling IPs, Twilio Elastic SIP Trunking. Accessed 22 August 2026.