Vodia PBX now enables users to schedule reports beyond daily intervals - the PBX now supports weekly, monthly, and quarterly options. Reports can be combined, such as “0:00/week 0:00/month,” to send both weekly and monthly reports at midnight. Caution is necessary, however, when scheduling quarterly reports on busy systems (due to performance concerns). The web interface now offers period selection for reports, such as the current or previous day, week, or month. While this simplifies report generation, large systems should be mindful of potential slowdowns when accessing large amounts of data. The "Try" button continues to generate daily reports.
A common requirement for PBX systems is to generate reports. Many of those reports are generated daily. The Vodia PBX offers such reports for ACD and other accounts at midnight, where “midnight” was a term that could be specified in a field in which the the email address for the report had to appear.
Interestingly, it was already possible to specify more than one time when the report should be generated. We are now building on this possibility and extending it beyond the day.
The old syntax just accepted the time of day (in 24-hour format) when the report should be generated. Because the PBX checks every 15 minutes, it had to be in 15-minute intervals (like 3:45). We have now extended that format to accept either the weekday (“sun”, “mon”, … “sat”) or just “week” for Sunday. It's also possible to use “month” for monthly reports and “quarter” for quarterly reports.
It's also possible to combine those reports. For example, “0:00/week 0:00/month” will send both weekly and monthly reports at midnight.
It should be noted that sending out a quarterly report on very busy systems is not a good idea, as it will cause the PBX to perform a table scan on all CDR records, which can take minutes before that process is completed.
The “Try” button will always generate daily reports.
We have also taken the concept into the web interface. The domain ACD page, where you can see agent activity, now also includes a new button for the selection of the period that should be reported. By default it's the current day, but you can select the previous day, the previous week (assuming the week starts on Sunday), the current month and the previous month.
As with the midnight CDR, you need to be careful when loading the whole month of CDR if you have very busy systems. The system limits the search to the current ACD, but if there are millions of CDR this will keep the system busy for a few seconds.
The login stat below the Agent activity and the call dropout report is always per day. This is something we might address in future versions—one of the main challenges is to display agents that use the login and logout a lot without filling up the whole screen.
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.