Tech

Text Messages

Published on:

August 26, 2013

The Vodia PBX has supported email notifications since the beginning, helping administrators and users stay informed about important events. In version 5.1.1 we introduced text messaging (SMS), initially for administrators, to enhance real-time notifications. The PBX uses HTTP-based messaging, which is simpler to set up and troubleshoot compared to SMPP. Multi-tenant environments benefit from domain-level configuration, allowing customers to manage their own SMS services. The system also includes retry mechanisms to improve reliability. Once it's stable, this feature will be extended to user events, further improving communication efficiency within the PBX.

The PBX supported email notifications practically from day one. Many administrators and users are using this powerful feature to stay up-do-date with events that are important to them, like server restarts or voicemail messages.

In version 5.1.1 a new way to inform administrators and users has silently crept in: good old text messaging has been added to the PBX. First only for administrators, this new feature is testing out how productivity can be increased by sending short messages to the administrator's cell phone. Once this has stabilized, we are ready to also offer the feature for user events.

Text messaging has its own little protocol for sending those messages. The short message peer to peer (SMPP) protocol is used for blasting out lots of messages, but this protocol only has practical relevance for mass text messaging with high volume. Most text messaging providers offer a HTTP-based interface as well, which simply uses a GET request with URL-encoded parameters to get the job done in a very simple way. We decided to start with HTTP first, as it's easy to set up and troubleshoot. The PBX sends only occasional messages, so HTTP is completely sufficient for the job. The URL can be defined at system and domain level; if defined on the domain level, only the domain administrators get notified. This is useful in multi-tenant environments wherein the customer has to set up and pay for the text messaging.

For example, for clickatell the following URL can be used: http://api.clickatell.com/http/sendmsg?api_id=3431425&user=vodia1234&password=tHhDHdduasJAShds&from=13434534345&mo=1&to={to-e164}&text={text}. The variable parts in the URL are encoded between curly brackets and contain the text and the destination. Other parameters, like the password, can be hard-coded there and are transparent to the PBX.

To increase the reliability of the sending process, we have also made small changes to the HTTP client subsystem. If the delivery fails, it reschedules the request again and tries again later (up to three times).

Derniers articles

Voir tous

Using service flags in V70 of the Vodia PBX

V70 of the Vodia PBX introduces flexible service flags that help organizations automate call routing, scheduling, queue management, announcements, and communication workflows throughout the day. Service flags can be configured manually or automatically to control how calls are handled during business hours, after hours, holidays, or special events. They can also be chained together for more advanced routing logic and integrated with external calendars such as Google Calendar to support dynamic scheduling and operational flexibility across business environments.

May 12, 2026

Keycloak OpenID Connect Integration for the Vodia PBX

Vodia’s PBX now integrates with Keycloak OpenID Connect, providing secure single sign-on for users so they can access all connected applications without repeated authentication. Logging out from one application automatically logs the user out of all connected systems, simplifying user management and improving security. Keycloak, a Cloud Native Computing Foundation project, supports standard protocols including OpenID Connect, OAuth 2.0, and SAML, offering enterprise-grade identity and access management. To ensure proper integration, Keycloak user emails must match the corresponding PBX extension emails. Complete guidance is available in the Vodia Keycloak integration guide, with additional details in the Keycloak official documentation.

September 12, 2025

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency and reduce operational costs.

September 8, 2025