Editorial

As spam and robocalls increasingly disrupt businesses, Vodia Networks offers advanced filtering in its PBX system, including anonymous call detection and, in partnership with TrueCNAM, a spam scoring feature. This integration assigns each incoming call a spam score, allowing companies to block or redirect high-risk calls. Configurable at the domain and user levels, this feature — available in Vodia PBX version 58.4 — provides flexibility for hosted PBX clients to customize call handling and protect productivity.

Announcement

CallCabinet, long trusted for its multiple award-winning compliant call recording solution, Atmos, has teamed up with Vodia, the company that pioneered multi-tenant PBX, with a cloud-based solution for every firm that needs to record calls for training, dispute resolution, regulatory compliance, or security.

Editorial

In hosted PBX environments, Yealink's Zero Touch provisioning simplifies the phone setup process by automating configuration without user intervention. The phone contacts Yealink’s redirection service (with its MAC address), retrieves the provisioning server details and automatically fetches its configuration. This integration has been added to the Vodia PBX, similar to an earlier feature for snom phones. The process ensures secure provisioning by verifying client certificates, enhancing ease of setup. Users can access this feature by obtaining login credentials from Yealink, and the integration is available in Vodia's upcoming version 5.3.1.

Tech

The simple filter on our PBX for the domain name was that we were throwing the baby out with the bathwater. It was simply not possible to define exceptions. That made it practically impossible to use the feature in a real deployment. If the system administrator white-listed IP addresses, traffic from there would still be ignored if the domain name did not match. Adding that back in to the filter solves many of the trunk related problems, as admins can just add the IP addresses for the trunks.

Tech

Thus the move with MongoDB. Although it is latest technology (and maybe just because of that), writing natively into the database was actually relatively simple. MongoDB can deal with very large amounts of data, so the PBX does not have to bother with it. Down the road we might be even able to use the DB for reading as well, e.g. when the user is using the call history from the web interface.

Tech

Once we have the PCAP, finding a problem is becoming almost a pleasure. Because the files are small, and everything is in the same place. It becomes easy to find jitter problems, missing RTP packets and so on. Last week I saw how another external tool took the PCAP idea to the next level. Using an Ethernet switch with port mirroring, all the traffic that hits the PBX also hits the monitoring server, which also sorts the traffic by calls and then puts them into different files. There were nice logs of SIP packets, RTP analysis and other things you want to know about a call.

Tech

Usually every domain needs their own telephone number or numbers that link the world of VoIP with the good old telecom industry. This is done using SIP trunks. While it is possible to share a SIP trunk with several domains, most hosted providers prefer one trunk per domain. But how does the SIP trunk provider know which trunk is being addressed when there is a call coming in?

Announcement

The app called “Vodia Phone”, now available through the Google Play Store, will allow Vodia PBX users to make and receive voice calls over data networks using any Android mobile devices running Android 4.1 or higher. Based on the WebRTC technology, the app will be particularly beneficial for business users who want to use their mobile device to place voice calls over 3G or Wi-Fi through their Vodia PBX system while using their business number. An iOS version is planned for release in a few weeks.

Tech

Installing the Vodia PBX on a Microsoft Azure server provides an easy solution for businesses looking for a cloud PBX. The installation process is similar to that on any Windows operating system, but there are key steps to ensure smooth operation. First, make sure to open all necessary ports, including HTTP (80), HTTPS (443), TFTP (69), NTP (123), and LDAP (2345 for StartTLS, 2346 for TLS). Additionally, for audio traffic, virtual networks require specific endpoints with both public and private ports. The RTP range (e.g., 49900-50000 for 25 calls) must be configured based on how many calls you need. Each call uses four ports, so adjust accordingly for your system.

Editorial

Emergency calls are vital for safety, but misuse of public phones for false alarms can lead to significant costs. To help reduce the impact of these incidents while ensuring quick response in genuine emergencies, PBX systems offer several strategies. One option is to record emergency calls, providing undeniable evidence and discouraging misuse; another involves screening calls through an internal staff member, as at schools or hotels, before they reach the emergency center. This allows staff to assess the situation and direct help more efficiently. For added reliability, calls can be redirected to the emergency center if no one answers, ensuring the call isn’t lost. These methods are effective in various environments with public phones, from schools to warehouses.

Announcement

Vodia Networks, one of the leading providers of IPPBX and Contact center software, announced the much anticipated integrated billing functionality for its Vodia PBX software that will enable service providers to connect their Vodia PBX servers to Freshbooks; a popular cloud based accounting software, and automatically invoice their clients based on usage. This functionality will further allow service providers to track invoices and receive payments from their customers more efficiently through an online payment system.

Editorial

For someone who has struggled with SIP interoperability for the past 15 years, WebRTC has an earthshaking impact. Instead of arguing about SIP headers, UDP and RFC, WebRTC makes it possible for the PBX vendor to write software for clients. The interoperability is essentially JavaScript, which has very little room for interpretation (compared to SIP). This means we can offer all the features of the PBX in the browser, without any interop problems, on practically any platform that's out there. This will ultimately make SIP softphones superfluous.