Tech

Configuring your Twilio Trunk With Vodia PBX

Published on:

October 8, 2020

How to configure your Twilio trunk with the Vodia phone system.

Log into 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

  1. Authentication is used to authenticate the termination SIP URI IP address or FQDN
  • Click on the  plus 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 that 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 as well.

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 in order 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

On-Premise Persists: Why It Still Matters, and How NEC's Decision to Exit the Market Creates Opportunity

On-premise solutions continue to be vital for many enterprises due to their superior data security and control, essential for industries like finance and healthcare. They offer deep customization, fitting specific needs and legacy systems, and provide reliable performance, especially for latency-sensitive applications. Additionally, while cloud solutions have a pay-as-you-go model, on-premise can be more cost-effective in the long run for predictable workloads. This balance of security, customization, and cost-efficiency ensures on-premise remains a strong option amidst the growing shift to cloud services.

July 19, 2024

Locality networks Case Study: Providing an Industry-Leading Multi-Tenant UC PBX with Advanced Features to Its Customers

Locality Networks, delivers high-speed fiber optic internet and advanced tech solutions to homes and businesses. Seeking to enhance their offerings, they implemented Vodia’s multi-tenant UC PBX, which provides top-tier features like mobile extensions, web clients, texting and CRM integrations. This has enabled them to offer cutting-edge communication tools, enhancing customer productivity and satisfaction. The seamless deployment, robust call center features and excellent support from Vodia and partners have made this transition successful for their diverse clientele.

July 12, 2024

Cove Central TAPP Expands Nationwide

Cove Central Communications announced its nationwide Technology Alliance Partner Program (TAPP) with Vodia in November 2023, aimed at supporting Managed Service Providers (MSPs) in delivering VoIP solutions. Since its launch, TAPP has seen significant interest, with Cove Central now providing VoIP solutions to over 30,000 users through regional MSP partners. The program addresses challenges such as FCC fees, compliance, and E911 configuration, simplifying VoIP deployment for MSPs. Jim Whittaker, Head of Technology, noted a projected revenue increase of 60% or more in 2024 due to TAPP.

July 3, 2024