Tech

Buttons

Published on:

June 10, 2013

Traditional PBX phones featured buttons with LED indicators for various functions, often labeled manually. In the SIP world, vendor-specific implementations and limited standards, like the "dialog" standard for BLF, dictate functionality. While BLF allows LED control, actual button behavior relies on provisioning. Vodia PBX extends button provisioning beyond snom to Polycom and Yealink phones, simplifying setup while maintaining functionality. For Polycom, this even enables park orbits, allowing users to park and retrieve calls easily. Though not identical to legacy PBX experiences, these enhancements significantly improve usability and streamline operations for modern VoIP systems.

In the good old PBX world, most phones had some kind of buttons on the phone that offered numerous features that could help to make the office life as productive as possible. The buttons usually had a LED light associated with them, some even had two colors. Many of them had paper next to it, so that the user could pencil down what the button was actually doing. Buttons were used for shared lines, park orbits, monitoring other PBX extensions, logging in and logging out, message waiting indication, paging; just to name a few.

In the SIP world, there is only very limited support for the features. At the end of the day, there are two ways to go: Vendors do their own thing and implement a protocol both one the server and the client side to make it happen. The market share of such closed systems still makes up the majority of the market. snom ONE is using the “buttons” specification to make features possible between the snom phones and the snom PBX.

The alternative is to use standards. In the SIP world, there is practically only one standard available, called “dialog”. Originally it was intended for something else, but the lack of alternatives made vendors pick the standard to implement the busy lamp field (BLF) functionality. What the standard delivers is essentially a way to turn the LED of a button on and off (buried in a XML text that can easily take up several hundred bytes). What happens when the button is pressed is left to provisioning of the device. This is sad, but a reality that we have to deal with.

We have used the front-end to assign button functionality to the endpoint during the provisioning process from the snom ONE also for Polycom and Yealink phones (in version 5.0.10). Originally designed for the snom phones, we decided to use the same setup process also for other phones. The main difference is that only the BLF modes can be used for non-snom phones; but the assignment can be done on profile and extension level, which makes this very convenient.

For Polycom, it makes even park orbits possible. When the BLF is for a park orbit, ongoing calls can be parked there and other users can retrieve calls from the orbits.

This does not deliver the same experience like with the old PBX. However, it does solve a lot of the practical problems in real life and greatly enhances the experience with Polycom and Yealink phones.

Latest Articles

View All

Webinar | Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6

Join Vodia Networks on April 8 for a live, in-depth webinar on how real-time media streaming is powering the future of voice communication. Discover how Vodia PBX version 69.5.6 enables seamless AI integration, live call transcription using the Whisper API, and secure voice data handling. Hosted by Sales Engineer Eric Altman and VoIP Engineer Hamlet Collado, this session will walk you through real-world use cases, including OpenAI and Google Speech-to-Text integrations, MS Teams support, and new security features. You’ll also get a first look at Vodia’s AI roadmap and have the opportunity to ask your questions during a live Q&A.

March 28, 2025

The Vodia PBX On-Premise Whisper AI Deployment​

Whisper, OpenAI’s Automatic Speech Recognition system, delivers multilingual, noise-tolerant, and technical-language-ready transcription through a streamlined encoder-decoder architecture. With Vodia PBX’s integration, organizations can choose between using OpenAI’s service or hosting Whisper AI locally for complete data sovereignty and control. This on-premise option ensures that sensitive call data stays within your infrastructure while still benefiting from powerful transcription capabilities. To explore deployment options, see our Whisper AI on-premise setup documentation, review a self-hosted integration example, or follow our cloud-based call transcription guide.

March 27, 2025

Vodia at Enterprise Connect 2025: Embracing AI and Advancing Communications

Vodia Sales Engineer Eric Altman attended Enterprise Connect 2025 on March 18 and 19, where he connected with partners and gained insight into the future of enterprise communications. AI was the clear focus of the event, with discussions centered on agentic systems, chatbots, and generative technologies. “It was certainly the main element in the atmosphere,” Eric noted. He also shared his excitement about Vodia PBX version 69.5.6, which includes real-time AI integration with OpenAI and call transcription using the Whisper API. The event confirmed that AI is rapidly becoming a core component of modern communication platforms—and Vodia is well-positioned to lead the way.

March 26, 2025