Tech

Configuring your US SIP Trunk Provider Skyetel with Vodia

Published on:

January 12, 2022

Skyetel is an innovative SIP trunk provider that seamlessly integrates with the Vodia PBX system, enhancing your communication capabilities. With features like multi-tenant billing, SMS functionality, and endpoint health checks, Skyetel is designed to meet the needs of modern businesses. When paired with Vodia, users can easily manage their communication needs, ensuring robust connectivity and flexibility. Setting up a Skyetel number with Vodia allows for efficient call routing and management, empowering businesses to streamline their operations and improve customer interactions. Experience a smoother communication flow and maximize your operational efficiency with the powerful combination of Skyetel and Vodia.

Skyetel is a granular SIP trunk provider that offers many features, including: multi-tenant billing for the Vodia multi-tenant PBX, SMS features, DIDs, Endpoint health checks and more. Here’s how to set up the Skyetel SIP trunk with the Vodia phone system. 

Skyetel endpoint

The endpoint is where we will create an endpoint to the Skyetel network and the Vodia PBX routable IP address. Log in to your Skyetel account and navigate to the Endpoint group under “Endpoints.” 

Endpoint Groups

Click on add Endpoint Group and enter the following: 

  • Name: Name of the customer
  • Priority:  1 
  • IP address: External IP address of the Vodia PBX 
  • Port: 5060 
  • Protocol: TCP or UDP 
  • Description: Customer location or customer info 

Add the endpoint. 

Skyetel SIP Trunk - Add Endpoint group

Tenant

Skyetel also has a feature called “tenants," where you can set up your customer's billing information - this also includes the account ID, which is used to bill your tenant separately. Since Vodia is a multi-tenant phone system, it's also possible to use the same name under the account ID; in this case, it's best to use the FQDN created on the Vodia PBX. To learn how please visit create add URL: https://blog.vodia.com/skyetel_sip_trunk_vodia

For the tenant information enter the following: 

  • Name: John Smith
  • Phone Number: 7815556698
  • Billing Emails: js@vodia.com
  • Contact Name: John Smith
  • Contact Phone number: 7815556698
  • Account ID jscompany.pbx.com 
Skyetel SIP Trunk - Add Tenant

Purchasing a Skyetel Number

Next, you'll need to purchase a number for the Vodia PBX system. Navigate to Phone ---> Buy Phone Numbers 

  • Category Local
  • Quantity 1
  • Phone Number: tick of the phone number box
  • Area Code: Choose your area code and press search 
  • MOU "Minutes of use" (enter your estimate for number of minutes the number will use) 
Skyetel SIP Trunk - Buy Phone Number

Assign Number 

To make and receive calls, you will need to assign it to a tenant on the Vodia PBX. Once the number has been purchased, click on the cog; you will see the number with a red dot - this indicates the number isn’t peered to the tenant. 

  • Phone number: Phone number 
  • SIP Format: Choose how many digits you want coming into the Vodia PBX phone system 
  • Call Routing :Choose Endpoint Group 
  • Endpoint Group: Choose endpoint c
  • Tenant: Choose the tenant you want to bill 
  • Save the configuration
Skyetel SIP Trunk - Edit Phone Number

Setting up the Skyetel on the Vodia phone system 

Now that the account is set up on the Skyetel SIP trunk provider, we can set up the Vodia PBX to use the account. 

Navigate to SIP trunk on your domain PBX and choose the Skyetel template to add your customer's DID, then press create. The template has everything set up for you, so there’s no need to change any settings. 

Also, the Vodia dial plan has already been created automatically, so you can make test calls. 

Skyetel SIP Trunk -  Create Service Provider on Vodia

Sending the inbound call to an account 

Navigate to your new Skyetel SIP trunk and choose where you want to send the call. Here are some of the choices:

  • Default
  • Send calls to destination in the Request -URI
  • Send all calls to a specific account
  • Send to 10-digit DID
  • Match extension after prefix 
  • Use a list of expression 

For this tutorial, we are using default. The Vodia phone system will match the DID assigned to the extension and send the call to the user. Visit https://doc.vodia.com/docs/did-management for more information about DID management. 

Skyetel SIP Trunk - Routing/Redirection on Vodia

Latest Articles

View All

Jitsi Video Conferencing in V70: A Controlled Approach to Privacy

Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.

April 21, 2026

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