Tech

Configuring your Twilio Trunk With Vodia PBX

Published on:

October 3, 2019

To configure your Twilio trunk with the Vodia PBX, start by logging into Twilio and creating a trunk under Elastic SIP Trunking, where you set the termination SIP URI and localized options based on your location. Establish an authentication IP access control list by adding your Vodia PBX IP address, then create a credential list with your username and password, then create an origination SIP URI pointing to your PBX. After purchasing a Twilio number for inbound calls, complete the trunk setup in Vodia by entering all relevant SIP details and configurations; this ensures accurate registration and routing settings to facilitate efficient calling operations.

Log in to your Twilio account to start.

Termination URI

  1. Under Elastic SIP trunking, create a trunk name under general to name your trunk.
  2. Next is Termination, create a termination SIP URI,
  3. Name the Termination SIP URI (for example, (mycompany).pstn.twilio.com); this SIP URI will be used for the outbound proxy of the trunk.

Twilio also has localized Termination URI. You can use this based on your location, so with your newly-created SIP URI you can also use mycompany .pstn.us1.twilio.com, etc.

  • {example}.pstn.us1.twilio.com (North America Virginia)
  • {example}.pstn.us2.twilio.com (North America Oregon)
  • {example}.pstn.ie1.twilio.com (Europe Ireland)
  • {example}.pstn.de1.twilio.com (Europe Frankfurt)
  • {example}.pstn.sg1.twilio.com (Asia Pacific Singapore)
  • {example}.pstn.jp1.twilio.com (Asia Pacific Tokyo)
  • {example}.pstn.br1.twilio.com (South America São Paulo)
  • {example}.pstn.au1.twilio.com (Asia Pacific Sydney)

Authentication IP access control List

Authentication is used to authenticate the termination SIP URI IP address or FQDN

  • Click on the +button, friendly name: My business name
  • Add an IP address range: Your PBX IP address
  • Friendly name: VodiaPBX and save

Credential list is used authenticate the user and password of the SIP URI

  • Friendly name: mycompany.com
  • User name: The user who will be passed when authenticating the SIP request
  • Password: The password used by the user to the authenticate the SIP request

Origination

Here you will create the origination URI.

  • Origination SIP URI: sip.mypbxbuisnessname.com can also be an IP address.

This will be used to send traffic to the PBX, so if you don’t have a FQDN you can always use your external IP address:

  • Click on the Plus button and create the (Origination SIP URI) could be IP address or FQDN

Number

Purchase a number from Twilio to get inbound and CID working.

Once you have purchased your number you can point the number to your SIP trunk.

Creating the Twilio Trunk in Vodia PBX

General

  • Name your Trunk or choose the pre-configure Twilio trunk
  • Type (SIP Gateway)
  • Direction (inbound and outbound)
Vodia_trunk

Registration

  • Account: User name created in the credential list
  • Domain:  SIP URI created in the Termination URI (mycompany).pstn.twilio.com
  • Username: User name created in the credential list
  • Password:  Password created in the credential list
  • Proxy address: SIP URI created in the Termination URI (mycompany).pstn.twilio.com
  • Explicitly list address for inbound traffic 54.172.60.3  172.18.21.17  54.172.60.3 (Optional)

Routing Redirection

  • You can choose to send calls to the Request URI or to a specific extension

Number/ Call Identification

  • Trunk ANI: Add your Twilio Number
  • SIP Caller -ID presentation (Custom headers)
  • Request-URI Value: Let the system decide
  • From  Value: Other <sip:{trunk-ani}@{domain};user=phone>
  • To Value: Same as the Request-URI
  • P-Asstered Identity Value: Don’t use header
  • P-Preferred Identity Value: Don’t use header
  • Remote-Party-ID value: Based on the incoming call
  • Privacy Indication value: RFC3325
  • Rewrite global numbers value “Use + symbol at the beginning
Trunk_ID

Latest Articles

View All

Skills-Based Routing in V70: Match Calls to the Right Agent

Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.

April 7, 2026

Snapshots in V70: Capture and Restore Your PBX with Confidence

PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.

March 31, 2026

Configuring Emergency Alerts and Notifications with V70 of the Vodia PBX

V70 introduces emergency alerts and notifications designed to ensure critical events are not missed and responses happen immediately. Alerts can be triggered directly by users, delivered across multiple channels including phones, email, mobile apps, and SMS, and can automatically initiate calls to predefined numbers. Administrators have full control over how alerts are configured, enabling consistent, reliable handling of incidents across real-world, multi-tenant environments.

March 26, 2026