Integrating WhatsApp with Vodia PBX: A Step-by-Step Guide for Seamless VoIP Communication
Published on:
November 30, 2023
Integrating WhatsApp with the Vodia PBX allows for enhanced communication capabilities in the VoIP landscape. To begin, set up a WhatsApp Business account through Meta for Developers. After this, log in to the Vodia PBX dashboard and navigate to "Settings," then "Messaging" and, finally, "Notifications." In this section, configure your WhatsApp settings by entering your Phone Number ID as the username, generating a random application token for webhook verification, and using the access token as your application secret. Ensure you specify the callback URL for incoming messages and set your WhatsApp Business number as the default ANI for SMS.
In the dynamic world of VoIP, leveraging popular messaging platforms like WhatsApp can enhance communication capabilities. In this guide, we'll walk you through the process of integrating WhatsApp with the Vodia PBX to ensre smooth and efficient messaging experience.
Step 1: Create a WhatsApp Business Account on Meta for Developers. To kick off the integration process, visit the Meta for Developers website and set up a new WhatsApp Business account. This account will serve as the bridge between the Vodia PBX and the WhatsApp messaging platform.
Step 2: Vodia PBX Configuration. As the administrator, log in to your Vodia PBX dashboard and navigate to "Settings" -> "Messaging" -> "Notifications." In this section, focus on configuring the settings related to text messaging.
Text Messaging Settings:
Select WhatsApp as the service provider for integration.
Use your "Phone number ID" from the WhatsApp API Setup page as your username or account (e.g., 122495046068001304).
Generate a random application token for Webhooks verification (e.g., HNeoioRB)
Utilize the "Access token" from the WhatsApp API Setup page as the application secret.
Whatsup cross reference settings:
Your username or account will be your “Phone number ID” from the WhatsApp API Setup page. For example: 122495046068001304
The application token is a random string that ensures Webhooks verification token. For example: HNeoioRB
The application secret is “Access token” from the WhatsApp API Setup page. For example: lwALrDPVlxwkBOyLxamDcS5Uw87ihzQ6NyZAQQgXR34CagPI7u7HE41TUc3gPXXy0SZBt4vRWF8ziZAvvb8essA2x4eEYPfphZC7FZBWTji6Dcl2AnaO2XC5729ZCxSoZACpgJtpJVuIvxy0ENgnmVTIXiZBJ…
Address for pulling MMS content: http://your.pbx.com
Default ANI for sending SMS messages: Your WhatsApp Business phone number.
WhatsApp Webhook callback URL
Configure the Webhooks settings on the Meta for developers platform.
Webhooks Settings:
Callback URL: https://your.pbx.com/recvsms
Verify token:
Callback URL: https://your.pbx.com/recvsms
Verify token: Use the application token from the PBX.
Vodia Sales Engineer Eric Altman will attend HITEC North America 2026 in San Antonio, Texas, where he will discuss V70, the latest version of the Vodia PBX, and its applications for the hospitality industry. Vodia will showcase its AI-driven communications capabilities, hospitality-focused PBX features, integrations with leading property management systems and hotel phones, and solutions designed to help hotels improve guest experiences, streamline operations, and support modern communication requirements.
Modern business communication rarely happens within a single office or PBX environment. With V70 of the Vodia PBX, organizations and service providers can now share presence information between tenants and across separate PBX systems. External Presence Sharing extends BLF visibility beyond a single deployment, helping distributed teams maintain awareness of user availability across locations, departments, and communication environments while supporting more connected and flexible business communications.
V70.2 introduces more flexible licensing for multi-tenant PBX deployments by allowing service providers to assign prepaid licenses directly to tenants within a postpaid environment. Once assigned, the tenant uses the prepaid license independently, and the underlying postpaid license no longer counts that tenant. This gives MSPs and hosted PBX providers more flexibility in how they structure customer licensing while continuing to operate tenants on shared infrastructure, reducing operating costs and simplifying large-scale multi-tenant deployments.
.svg)
