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.

Tech

In version 5.2.3 we've enhanced the localization process for both the web interface and emails. Instead of relying on Excel tables for translations, we now allow partners worldwide to make localized edits directly in the interface, ensuring the translations are contextually accurate. We've moved all text prompts to the cloud for a single, unified translation source. This shift eliminates issues from mixing local content with server data. While some translation inconsistencies, like Russian text appearing in Turkish, have arisen, we encourage users to report such issues to help us improve and fill gaps as new features are added.

Announcement

Vodia Networks Inc a leading provider of PBX and contact center software, announced today a strategic partnership that will enable Vodia to offer advanced call reporting and analytics functionality for its IP-PBX solution in cooperation with nordic Telecom (NTC). The partnership aims to bring Nordic Telecom’s rich value-added Call reporting solution as an add-on to Vodia’s advanced IP-PBX platform, which will enable businesses and service providers to perform detailed analysis of their call traffic ultimately leading to an improved customer service and steady sales growth.

Tech

For two years, a vulnerability in certain OpenSSL versions allowed attackers to intercept encrypted traffic, potentially exposing sensitive information like private server keys. This vulnerability, known as Heartbleed, caused a global security crisis. Despite OpenSSL’s open-source nature permitting scrutiny, the bug remained undetected, and there were rumors some may have exploited it (rather than reporting it). Early on, Vodia focused on security, opting for a custom TLS implementation to avoid issues like OpenSSL's memory fragmentation. This decision not only helped sidestep vulnerabilities like Heartbleed, but it also shielded the PBX from widespread exploits, as attackers lack access to the source code.

Announcement

Vodia Networks Inc announced today the availability of its Vodia® mini PBX appliance through “IP Phone Warehouse”. Vodia® mini PBX brings the highly successful Vodia® PBX software to a compact low-power/high-performance appliance, and delivers A-Grade business telephony features such as Auto receptionist, Automatic call distribution, Video, SMS notifications and mobility, ensuring a higher productivity for your business and a significant reduction in the overall TCO. Further value-add features such as Fax-to-email, Click-to-call, Address book synchronization, Call recording, CRM integration and Microsoft® Lync presence, allow the Vodia® mini to provide SMBs with functionality that has so far been only seen on larger UC solutions.

Tech

In 5.2.2 we’re addressing a common challenge for SIP phones in LANs that need an outbound proxy based on their location. To provide the required quality of service, devices like Edgewater VoIP routers, or even simpler routers, route SIP traffic separately from other office data. To offer more flexibility, we’ve introduced a pattern-based list for specifying outbound proxies. This allows you to define specific IP addresses, ports, and transport types for different networks. For example, if a tenant has two offices with different network setups, the domain setting allows administrators to configure outbound proxies for each office using patterns like "1.2.3.4/32/10.0.0.2" or "10.43.0.0/24/edge43.company.com:5061/tls".