Integrating Prometheus with Vodia PBX enables effective monitoring of your phone system’s performance. Start by creating an API account on Vodia PBX to grant access to Prometheus, followed by the installation of Prometheus on DigitalOcean. Update the prometheus.yml file to include your PBX as a target by configuring the DNS, username, and password. Explore the Vodia API for available system stats, such as CPU usage and memory. Finally, create custom stat panels in Prometheus to visualize and track these key performance metrics in real time.
Prometheus is an open-source monitoring and alerting toolkit that is part of the Cloud Native Computing Foundation. By integrating it with Vodia PBX, you can effectively monitor and manage your phone system's performance. Here’s how to get started:
Step 1: Create an API Account on Vodia PBX
To allow Prometheus to access Vodia PBX data, you need to create an API account. Follow these steps:
Log in to Vodia PBX as an Administrator:
Navigate to the system level where you can manage user accounts.
Create a New User Account for API Access:
Go to the Administrator section.
Create a new account with the following details:
Account: Choose a user name.
API Access: Enable API access.
Type: Set the account type to Regular.
Password: Set a strong, secret password.
Save the Configuration:
Save the user account configuration.
Keep the username and password handy, as you will need them for Prometheus to access Vodia PBX data.
Once your server is set up, you can access the Prometheus user interface by going to http://your_server_ip:9090/
Setting up the .yml file
By default, Prometheus is set up to monitor itself and Node Exporter. To monitor more systems, you need to update the configuration file located at: /etc/prometheus/prometheus.yml
3 things need to be changed in the Prometheus .yml file config file
targets: ['123.vodia.com'] Here is where you will set the target - in this case it will be your PBX DNS name
username: 'prometheus'
password: 'prometheus'
Note: Do not remove the ' ' and [ ] in the config file leave it as is and change the value
Once you have edited the config file, you can modify the prometheus.yml using nano or any edit you desire by copy-pasting the config or simply creating a new .yml file and renaming the old file.
Restart the service by sudo systemctl restart prometheus
Check the Prometheus and click on System Stats - this will show all of the available APIs for Prometheus, and you will see an Example Response. Click on "view more" and it should look like this:
I have bolded all of the stats you can use as an examples, there's no need to copy the whole thing
# pbxctrl 69.3.2.beta
# HELP system_cpu_srv_max Peak usage of the CPU # TYPE system_cpu_srv_max gauge system_cpu_srv_max 0 1719852690061
# HELP system_cpu_srv_avg Average Load # TYPE system_cpu_srv_avg gauge system_cpu_srv_avg 0 1719852690061
# HELP system_cpu_ctrl_max Peak usage of the CPU # TYPE system_cpu_ctrl_max gauge system_cpu_ctrl_max 25 1719852690061
# HELP system_cpu_ctrl_avg Peak usage of the CPU # TYPE system_cpu_ctrl_avg gauge system_cpu_ctrl_avg 2 1719852690061
# HELP system_memory_all Total # TYPE system_memory_all gauge system_memory_all 172928 1719852690061
Creating a stat panel on Prometheus
Click "add panel" and enter the Vodia API cmd - in this case system_cpu_srv_max, then press execute: you can create many panels to monitor the PBX.
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.