Objective
This article shows you how to tell Twilio what should happen to an inbound SIP call arriving on a Bring your own carrier (BYOC) trunk — which application handles it, what happens if that handler fails, and where Twilio sends call status events.
Product
Programmable Voice
Environment
Twilio Console
User Account Permission/Role(s) Required
Your role must include permission to update BYOC trunks. Without it, the Edit configuration action is not shown.
Procedure
- In the Twilio Console, select Communications in the left sidebar.
- Select Voice, then Bring your own carrier.
- On the Trunks tab, select the trunk you want to configure.
- In the Application configuration section, select Edit configuration.
- Under Primary call control configuration, choose a Configure method and fill in the field it reveals:
- Webhook — enter the Webhook URL that handles the incoming SIP call and choose an HTTP method (HTTP GET or HTTP POST).
- TwiML bin — choose a TwiML bin.
- Function — choose a Function.
- Studio — choose a Studio flow.
- Under Fallback call control configuration, choose a Backup method and complete its field the same way. This configuration is used if your primary handler fails.
- Under Status callback, enter a Webhook URL and choose an HTTP method to receive HTTP events for call status changes on this trunk.
- Select Save. The Application configuration section now shows what happens when A call comes in, when the Primary handler fails, and when Call status changes.
Additional Information
- Outside the US1 region, Webhook is the only available configure and backup method. TwiML bin, Function and Studio options appear in US1.
- Webhook URL fields are validated, so enter a complete, well-formed URL.
- Select Cancel to close the panel without saving your changes.
This content was generated by AI and reviewed, edited, and verified by a human.