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".

Tech

Hosted PBX offers many advantages over local systems but, when it comes to paging phones in a LAN, multicast remains the most efficient solution. Unfortunately, multicast often doesn't work in hosted PBX environments or in large corporate networks. One workaround is using a unicast stream converted into multicast through a device in the LAN, often with iptables. Another option is to use snom phones or the PA1, which can convert the audio stream into multicast. Alternatively, a local Vodia mini PBX can be set up to register with the hosted PBX, sending calls to a multicast paging group. This method offers more flexibility and useful features like call recording, making it an ideal solution for handling large volumes of paging.

Announcement

Vodia® Networks has once again taken the lead by introducing a VoIP-in-a-Box solution based on open standards that is designed to work seamlessly across all IP handsets, giving users the ultimate freedom in end-device selection. With this new feature, as soon the IP handsets are plugged into the network, Vodia® PBX automatically detects all the phones in your network and lists them on the admin portal. The listed information includes Vendor type, MAC address and IP address of each detected device. The administrator can then simply assign a PBX user to the phone by selecting a user profile from a drop down. The IP handset then automatically reboots and configures itself with the assigned user profile. Configuration information may include customer name, password, email address, telephone number, ring tone, class of service, QoS (Quality of Service), SIP URI, SIP proxy server, call server FQDN (Fully Qualified Domain Name) or IP address, and other parameters.

Tech

ACD statistics have been reworked in version 5.2.0 to provide more detailed insights at the user level, making it easier for agents to track their performance. Users who are part of an ACD can access a link to the wallboard, which now updates in real-time through WebSockets, ensuring immediate visibility of incoming calls. The wallboard shows call statistics, including total and average call durations, hold time, idle time, and per-agent performance. It also displays the history of recent calls. The web-based wallboard is platform-independent, accessible from any device, and supports remote access, making it ideal for home offices and mobile agents.

Tech

Version 5.2.0 introduces a valuable improvement for extensions with multiple alias numbers. Now, when an inbound call is received, the PBX will send the called alias number to the registered device; if the number isn't on the alias list, the primary extension name is used. This change enhances the role of the PBX, so it also serves as a trunk engine. It’s particularly beneficial for SIP trunking providers, who can leverage features like PCAP recording, RTCP-XR for SLA monitoring, and the management of both IPv4 and IPv6 interfaces. Additionally, with improved CDR reporting, billing becomes easier, and the PBX scales efficiently with virtualization support.

Tech

When the first version of pbxnsip introduced RTP encryption, it was a pioneering feature, but it didn’t generate the expected marketing success. Back then, customers were just happy if they could hear each other over VoIP. Over time, we refined our SRTP implementation to address challenges like the rollover counter, optimized transcoding, and avoided one-way audio issues. With growing awareness of security, encryption is now a critical focus, yet many providers still don’t encrypt voice traffic. To bridge this gap, we’ve added the ability to write decrypted PCAP files, making troubleshooting encrypted voice easier. This is available in version 5.1.3.