Configuring Skyetel SMS with the Vodia Phone System
Published on:
August 29, 2022
SMS is cool when you can send SMS and MMS messages directly to customers from your user portal. To configure your Skyetel SMS, log in to your Skyetel portal and navigate to the 3 cog wheels in the right-hand corner (shown below). This will bring you to the API section.
SMS is cool when you can send SMS and MMS messages to customers directly from your user portal. To configure your Skyetel SMS log in to your Skyetel portal and navigate to the 3 cog wheels in the right-hand corner. Shown below, this will bring you to the API section.
Skyetel API Creation
Settings
Chose API Keys and click on "create" and provide note (i.e., "Name").
API Key Created
You will need the SID and the Secret - copy these into your notepad.
Configuring Skyetel number for SMS
Next, we need to configure a number for SMS: navigate "Phone numbers," then local numbers.
Next, click on the number you want to edit ("Cog" wheel), then navigate to SMS & MMS.
Set up the following values:
Forward: Callback URL
URL: https://PBXDNS.com/recvsms
Method: POST
Delivery Confirmation is optional
Vodia Text Messaging Settings
On your Vodia phone system navigate to "Messaging ---> Notification". You will need the following values:
Provider: Skyetel
Username or Account: This will be your SID token
Application secret: This will be your SID Secret
Text messaging-enabled for domains by default "On-Off" optional
URL prefix for receiving messages: recvsms
Address for pulling MMS content: https://pbx.audiomercy.com
Default ANI for sending SMS messages: Skyetel programmed number or can be left and assigned to the user extension SMS ANI
Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.
Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.
The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.
.svg)
