Objective
This article shows you how to add an origination URI to an Elastic SIP Trunk, so Twilio knows where to route inbound calls into your communications infrastructure.
Product
Elastic SIP Trunking
Environment
Twilio Console
User Account Permission/Role(s) Required
Your role must include permission to read SIP trunks to open the page, and permission to update SIP trunks to add an origination URI.
Procedure
- In the Twilio Console, select Communications in the left sidebar.
- Select Voice, then Elastic SIP Trunking.
- On the SIP trunks tab, select the trunk you want to configure, then open the Origination tab.
- In the Origination URIs section, select Add origination URI.
- In the Add origination URI panel, complete the fields:
-
Origination SIP URI — the SIP address Twilio routes inbound calls to. It must start with
sip:and can be up to 255 characters. - Friendly name — optional label, up to 64 characters.
- Priority — relative importance, 0–65535. The lowest number is the most important. Defaults to 10.
- Weight — relative share of load for URIs of equal priority, 1–65535. Defaults to 10.
- Enabled — select Route calls to this URI.
- Select Add.
- An Origination URL added. confirmation appears and the URI is listed in the table with its Origination SIP URI, Priority, Weight and Enabled state.
Additional Information
- The origination SIP URI is required; priority and weight are pre-filled with 10 so you can accept the defaults.
- If the trunk has no URIs yet, the section shows This trunk has no origination URIs and prompts you to add one to route inbound calls from Twilio to your communications infrastructure.
- Select Cancel to close the panel without adding a URI.
This content was generated by AI and reviewed, edited, and verified by a human.