Back to Blog
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.

Asad Khan

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
Editorial

Open Source PBX vs Commercial PBX: What You’re Really Managing

Organizations often start with an open source PBX for flexibility, but as systems move from initial setup to daily operations, the real cost becomes management, maintenance, and long-term reliability. This article explores the difference between building a PBX stack from frameworks and running a commercial, integrated PBX platform, focusing on operational complexity, security responsibility, upgrades, and ongoing maintenance. It explains how a purpose-built PBX shifts the burden from continuous engineering to stable operation, helping teams prioritize clarity, control, and scalability as requirements grow.

February 12, 2026
Announcement

The Vodia PBX and Google Gemini

Vodia PBX now integrates Google Gemini with JavaScript IVR and Voice Agents, enabling real-time, AI-driven call handling and intelligent routing. By combining Gemini’s multimodal large language models with Vodia’s programmable IVR framework, organizations can build voice agents that stream audio in real time, make routing decisions through function calls, and handle both basic and attended transfers with AI-assisted screening. This integration allows businesses to automate call flows, reduce hold times, and improve productivity using conversational AI that works directly inside the PBX.

February 4, 2026
Editorial

6 + 1 Phone System Features You Need in 2026

In 2026, a modern phone system must go well beyond basic calling. Core requirements now include built-in AI for smarter call handling and transcription, real-time analytics dashboards for visibility and control, flexible auto attendants to route calls efficiently, seamless Microsoft Teams integration, and robust mobile apps that support hybrid and remote work. Clear separation between business and personal calls protects work-life balance, while reliable white-glove support ensures these capabilities work smoothly in real-world environments as communication needs evolve.

January 30, 2026