How to configure VoIP Innovation SMS with Vodia PBX
Published on:
January 4, 2021
To configure VoIP Innovation SMS with Vodia PBX, start by ensuring you have Vodia version 66.0.7, a VoIP Innovations account, and a purchased DID number. Log in to your VoIP Innovations account, create an SMS-only API app using Apidaze, and set the SMS request URL to your PBX domain. Assign your DID number to this app for SMS functionality. Then, in the Vodia PBX, enable SMS at the domain level and configure the messaging settings by entering the API key, secret and SMS DID. Finally, test the SMS feature using the Vodia Windows App by sending a message to a number formatted as 1XXXXXXXXXX.
Vodia was curious to see how SMS worked with VoIP Innovations’ SMS capabilities. If you have an account, please follow these step-by-step instructions.
Log in to your VoIP Innovations account at backoffice.voipinnovations.com and navigate to “App”. This will bring you to https://admin.apidaze.io/
Log in to your apidaze account with the same credentials you use to log in to your VoIP Innovations account.
Creating your API
Next, we are going to create an API. Click on the App hyperlink to create an API application.
Next click on
to start creating your application:
Name Your App (ex: Vodiasms)
Choose “SMS only”
For SMS request URL into the following: https://enteryourpbxdomain/recvsms
Press the “Create App” button to finalize your application. apidaze will then create an API key and API secret (we will use the Vodia PBX messaging settings).
Assign your number to your SMS App
Next, we will assign a DID to your SMS application. Click on the 3 Dot icon
choose one of your purchased DIDs or an existing one as the SMS number.
You will then get a confirmation. To use the number for SMS, press ok.
Turning on SMS at the Domain Level
By default, this setting is off. To turn on the feature, per domain, just click on the edit button in the domain list window.
Scroll down and choose “to Enable text messaging” to activate it for your domain.
Setting SMS on the Vodia PBX
Next, log in to your Vodia PBX and navigate to the administrator level --> Settings ---> Messaging >Notifications
Provider: Choose VoIP Innovations
Username or account: API key
Application secret: API password
Default ANI for sending SMS messages: Use the assigned SMS DID
Let's test SMS
Now it's time to test the service.
Open up your Vodia Windows App - if you don't have the App, you can download it here. For more info on the Vodia Windows App, visit us here - these two links work if you're an iOS or Android user.
Next, on your Windows App, type the number to which you would like to send an SMS by typing the number in the following format:
1XXXXXXXXXX on your Vodia App browser, then press the SMS chat icon to send the SMS to the recipient.
Vodia Phone 2 turns your Android device into an extension of your Vodia Phone System, making it easier to stay connected wherever you work. Native Android integration lets users make and receive business calls using their office number and identity, even when the app is running in the background. From one mobile app, they can hold, transfer and park calls, access voicemail, messages and contacts, review call history, view extension activity and manage important settings such as Do Not Disturb and call forwarding.
The new Vodia PBX Installer Wizard makes it easier for administrators to deploy Vodia PBX on Windows. It automatically detects the latest supported version, while still letting admins choose a specific V68, V69, or V70 build. The wizard downloads the required files, creates the Windows service, sets up the installation folder, and generates the access details needed to open the PBX. A download-only option is also available for preparing and inspecting the files without completing the installation.
Business communication is no longer tied to a single device. Desk phones remain valuable for employees who manage high call volumes, mobile apps give remote and travelling teams access to business calling wherever they work, and browser calling fits naturally into computer-based workflows. This article looks at the strengths and limitations of each endpoint, explains which roles they suit best and shows why most organizations benefit from building the right mix rather than selecting one option for everyone.