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

Vodia Announces Integration with ElevenLabs Voice AI Platform

A streamlined integration connects the Vodia PBX with the ElevenLabs Voice AI Platform using a lightweight IVR JavaScript script and native SIP REFER for call transfers. Audio and call control are handled entirely through standard SIP signaling, while all conversational logic, prompts, voice selection, and routing rules are configured in the ElevenLabs dashboard. This approach removes the need for webhooks or WebSocket connections and keeps the PBX side intentionally minimal, making the deployment clean and production-ready.

January 22, 2026

Why Multi-Tenant Still Matters for MSPs

Multi-tenant architecture allows MSPs to manage multiple customers efficiently on a single, secure PBX while maintaining strict tenant isolation. By sharing infrastructure, MSPs can reduce operational costs, apply updates and security patches centrally, scale customers on demand, and onboard faster without increasing complexity. As cloud and SaaS models continue to dominate, a well-designed multi-tenant phone system provides the control, flexibility, and reliability MSPs need to support growth, evolving requirements, and modern communications workloads.

January 19, 2026

Start 2026 with a cloud PBX built for real-world deployments

A flexible, cloud-neutral PBX built for real-world deployments in 2026, Vodia supports MSPs, enterprises, and service providers with an open, SIP-compliant platform designed for scale. With Vodia PBX version 70 arriving in Q1 2026, the platform brings multi-tenant hosting, reuse of existing IP phones through centralized provisioning, built-in WebRTC softphones, transparent licensing, and partner-driven support, giving organizations full control over modern business telephony without lock-in or hidden costs.

January 13, 2026