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.

Tech

Failover capabilities are essential for ensuring uninterrupted service in PBX installations, especially with the growing use of high-bandwidth wireless connections like 4G. PBX systems traditionally use LAN-based IP addresses, but dynamically switching to a public IP address during failover has posed challenges. To address this, we've introduced a new feature - the PBX periodically probes a specified URL to detect its public IP address and adjusts the routing table accordingly. This feature simplifies the process, eliminating the need for complex scripts and allowing systems to automatically switch to the correct IP during failover, ensuring continuous operation. The feature will be available in version 5.2.5.

Editorial

The recent case of phone call fraud highlights the growing risk of PBX systems being compromised, with hackers using them to dial expensive numbers. This situation often arises when the PBX is used as a "least cost router" to route calls through expensive destinations. Even without external voice traffic, however, bots on local networks can exploit PBX systems by accessing the TAPI feature and dialing numbers directly from a computer. To mitigate risks, it's crucial to ensure strong security measures, like checking for viruses, using secure passwords, and verifying the fraud detection features offered by service providers. It's also important to restrict expensive number calls via the PBX dial plan and ensure TAPI licenses are carefully managed.

Tech

In the past, pbxnsip offered a module connecting the PBX to property management systems (PMS), enabling features like billing international calls and notifying the front desk about room status updates. This functionality was based on the Universal Hospitality Language Layer (UHLL) protocol, which also supported non-telephony tasks within hotels. While this module was useful, it required additional software and added complexity. For the next release (5.2.5 or 5.3), we’ve integrated UHLL directly into the PBX code, simplifying the setup. Those interested in trying out the new features can email us for access to a beta build.

Announcement

Today, two of the most critical components of any hospitality property are its phone system (PBX) and the Property Management System (PMS). Both the PBX and PMS are going through a rapid modernization trend in the hospitality industry with most of the hotels migrating from traditional TDM based systems to their more modern IP based kin. Traditional PBXs are being replaced by IP based PBXs to benefit from the advantages the new VoIP technology. Traditional Property Management Systems (PMS) are also being replaced by more modern IP based systems that can seamlessly integrate with other IP based systems and services.

Tech

In version 5.2.3, we improved the email client to better handle multi-tenant environments. Previously, email problems could affect all domains if one email server went down, causing delays in outgoing messages. We redesigned the client to be multi-tenant while preserving the reliability of the previous setup. However, issues arose with the TLS context when multiple emails were sent in quick succession. This required a patch to resolve the problem. If you upgraded to 5.2.3 before June 28, we recommend repeating the upgrade to ensure the latest email fixes are applied for faster, more reliable email performance.

Tech

The concept of the "Internet of Things" (IoT) can often be clouded by vague terms, and the promise of IPv6 enabling the "Internet of Everything" seemed like a great solution at first. While the idea of assigning every object its own IP address sounds compelling, the reality is simpler and more practical solutions are often more effective. In terms of IoT, telephone numbers, especially in the form of extensions, offer a well-understood, universal addressing system that could be used to control devices like shutters, lights or doors, all via a PBX. Ultimately, a mix of different technologies will likely coexist, enabling seamless interaction across various devices and systems.

Editorial

In version 5.2.3 we made significant updates to the email client, addressing issues with Linux systems and multi-tenant environments. The email client initially used a single loop, which caused issues with stability and multi-tenant functionality - a problem with one email server affected all domains. The solution was to switch to a multi-threaded client, but this introduced its own challenges, especially with the STARTTLS command during the switch between unencrypted and encrypted traffic. After a second build to fix these issues, the email client is now more reliable, with fast, independent email delivery for each tenant. If you upgraded before June 28, we recommend reapplying the upgrade to ensure all the fixes are in place.