SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How do I configure origination settings for an Elastic SIP Trunk?

Objective

This article shows you how to set an Elastic SIP Trunk's disaster recovery URL and apply a header manipulation policy to inbound calls on the trunk.

 

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 save changes.

 

Procedure

  1. In the Twilio Console, select Communications.
  2. Select Elastic SIP Trunking.
  3. On the SIP trunks tab, select the trunk you want to configure, then open the Origination tab.
  4. Under Origination settings, complete the fields:
    1. Disaster recovery URL: Twilio sends inbound calls to this URL when your origination URIs are unreachable. Optional, up to 1024 characters.
    2. Disaster recovery HTTP method: POST or GET.
    3. Header manipulation policy:choose a policy to apply to inbound calls on this trunk, or None. Optional.
  5. Select Save settings.
  6. An Origination settings updated. confirmation appears.

 

Additional Information

  • Choosing None detaches any policy currently applied to the trunk's inbound calls.
  • The policy list is drawn from the SIP header manipulations tab, so create a policy there first if the list is empty.
  • The disaster recovery URL is a safety net, not a substitute for origination URIs. Configure at least one origination URI in the Origination URIs section on the same tab.

 

This content was generated by AI and reviewed, edited, and verified by a human.

Have more questions? Submit a request
Powered by Zendesk