Vodia’s new SMS Management feature centralizes all customer SMS provider connections under SIP Trunks for each tenant. It allows you to easily add supported providers and manage SMS numbers with custom settings like name, number, provider and message routing. Policies can be created for opt-in/opt-out messaging, welcome messages, message retention and conversation management with keywords. Additionally, menu selections offer customizable options for customers, such as providing information or directing them to URLs. This enhances SMS management by streamlining provider setup and message handling for better customer interaction.
Under Numbers, you can specify the SMS number for the user to check the values below:
Name: Name with customer or group name
Number: Add the SMS DID
Policy: If no policy has been created, choose "none"
Provider: Choose your provider
URL prefix: This prefix can be unique for each number: set the prefix you want in the provider portal and use that prefix when you assign the SMS number
Source: Souce can come to the assigned extension
Destination: Destination messages can be sent to any other extension or to the same extension
Policies
You can create policies for your SMS messages: check below for what each policy can be used
Names Policy: Name the Policy
Opt-in or opt-out: Choose what kind of policy this will be "opt-in or out"
Welcome message: Write a welcome message for the customer
Resend welcome message after: choose the number of days for the duration of the message
Keyword for stopping conversation: Choose a keyword - for example "Stop"
Keyword for resuming conversation: Create a message if the user would like to continue
Duration for keeping messages: Choose the number of days Vodia will keep the messages
Allow only text messages: Turn on or off to only allow texting
Menu selection
In this section, you can create a set of destinations for the customer under the first box with a name for the menu, which can be anything, and then the message box. Themessage box can contain information about a product - you can include a URL for the customer to explore and provide a list of actions from which they can choose.
Cisco IP Phone Series 6800, 7800, and 8800 devices running Multiplatform (MPP / 3PCC) firmware can be used with the Vodia PBX in SIP-based environments. Supported models span entry-level, mid-range, and advanced devices commonly deployed in enterprise and service provider scenarios. Cisco-provided MPP firmware is used, with firmware versions and upgrades managed through the PBX after initial onboarding, supporting both on-premises and cloud deployments.
Music on Hold plays an important role in how callers experience wait times and perceive service quality. With Vodia PBX Version 70, we’ve enhanced Music on Hold to deliver neutral, calming, high-quality audio that reassures callers while they wait. These improvements, combined with flexible streaming options, emergency messaging, and full support for cloud and on-premises multi-tenant environments, help businesses reduce dropped calls and create a more positive caller experience before an agent ever answers.
Organizations often start with an open source PBX for flexibility, but as systems move from initial setup to daily operations, the real cost becomes management, maintenance, and long-term reliability. This article explores the difference between building a PBX stack from frameworks and running a commercial, integrated PBX platform, focusing on operational complexity, security responsibility, upgrades, and ongoing maintenance. It explains how a purpose-built PBX shifts the burden from continuous engineering to stable operation, helping teams prioritize clarity, control, and scalability as requirements grow.
.svg)
