Announcement

Version 5.0.1 is Out

Published on:

December 11, 2012

This article discusses the release of version 5.0.1 of the snom ONE PBX, highlighting fixes and improvements made following the 5.0.0 release. Users who installed version 5.0.0 can now easily upgrade through the web interface by inputting a simple XML link. One of the major issues with 5.0.0 was a JavaScript error preventing administrators from changing PINs for extensions, especially when Microsoft Lync was not enabled. This article also addresses the template error for fax messages, which had been left empty in the build process. Additionally, improvements were made to the Microsoft Lync presence update, with a more efficient DNS lookup for easier setup. Although snom ONE is working on integrating Office 365 Lync presence features, this will probably be included in the upcoming version 5.1.

Nobody wants to install a version that has a lot of zeros at the end. So we didn't lose time coming up with version 5.0.1. For those who installed version 5.0.0, it's an excellent opportunity to try the upgrade via the web interface. No matter what OS you're using, you can just put the http://snomone.com/downloads/snomONE/version-5.0.1.xml link into the software upgrade field in the PBX, let it work, then schedule a reboot.

After we released 5.0.0, we soon found out if you don’t have the Microsoft Lync enabled the administrator can't change the PIN for extensions. This was caused by a JavaScript error on the browser, but because there was no notification it could drive admins crazy if they tried over and over again to change the PIN and never got to their mailboxes. That PINs are not encrypted on the file system (a feature introduced in 4.5) wasn’t making life easier, either — all you could see was some spaghetti in the XML on the file system.

Another problem was the template for the FAX message was actually empty - it was simply forgotten in the build process. For those who had problems getting fax to mail working, yes, this explains it.

We also had the opportunity to get more exposure with another feature, the Microsoft Lync presence update. While it was possible to get it working in 5.0.0, we made a small but important change to the DNS lookup procedure. Microsoft Lync wants to see _sip._tls prefixes as well, and if they are present it makes the setup a lot easier. We have made a page, http://wiki.snomone.com/index.php?title=How_to_use_lynchosted.com - you can see in this example how to set it up.

We have started to use Office 365 internally, and you can imagine we also planned to publish our extension presence state into the cloud. We had to find out that Lync in 365 works slightly differently, however, than Lync on customer premises. We will have to add some more code into the PBX to make it possible to use the 365 presence features. It's more than a small patch, and it might be version 5.1 that will make it possible to use Office 365 Lync with snomONE. Don't worry, we're reminded of this feature every day while we're working.

Apart from that, the feedback from customers who upgraded to 5 was generally good. Most complaints were about the hectic changes in the license model (which is understandable), but it seems the product itself - and even the activation process - is in good shape. We have a few smaller things in the pipeline for 5.0.2, and some changes for 4.5. I expect the next minor release in a few weeks. Those who like to stay "up to the latest" are welcome to upgrade their systems.

Latest Articles

View All

Keycloak OpenID Connect Integration for the Vodia PBX

Vodia’s PBX now integrates with Keycloak OpenID Connect, providing secure single sign-on for users so they can access all connected applications without repeated authentication. Logging out from one application automatically logs the user out of all connected systems, simplifying user management and improving security. Keycloak, a Cloud Native Computing Foundation project, supports standard protocols including OpenID Connect, OAuth 2.0, and SAML, offering enterprise-grade identity and access management. To ensure proper integration, Keycloak user emails must match the corresponding PBX extension emails. Complete guidance is available in the Vodia Keycloak integration guide.

September 12, 2025

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency.

September 8, 2025

Why Fax Still Matters in 2025 and How Vodia Makes It Easy

Although many consider fax outdated, it continues to play a crucial role in sectors where compliance, confidentiality, and legal proof of delivery are non-negotiable. Healthcare providers rely on fax to meet HIPAA requirements, while industries such as finance, law, and real estate depend on it for contracts and documents that require signatures or legally verifiable transmission. Unlike email, fax offers confirmation reports that serve as proof of receipt, along with time-stamped records that hold up in legal proceedings. With Vodia’s PBX, digital fax becomes faster, easier, and more accessible than ever before, enabling users to drag and drop documents, monitor transmission progress, and receive immediate confirmations.

September 5, 2025