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. The 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 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 them so 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 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, “dialog”. Originally intended for something else, 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 the provisioning of the device. This is sad, but it's a reality 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 and also for Polycom and Yealink phones (in version 5.0.10). Originally designed for snom phones, we decided to use the same setup process for other phones. The main difference is 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 doesn't deliver the same experience as with the old PBX, but 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

The Vodia PBX and the Infor Hospitality Platform

The certified integration between the Vodia PBX and the Infor Hospitality Platform brings hotel operations and guest communications together. Through support for UHLL and FIAS, the two systems can exchange essential guest and room information, helping hotels automate extension activation at check-in, room resets at check-out, guest moves, calling permissions, call billing, Do Not Disturb settings, housekeeping updates, and wake-up calls. This reduces manual work for hotel staff and keeps telephone services synchronized throughout each guest’s stay.

August 28, 2026

Digital Autonomy and Why MSPs Should Own the Customer Relationship

Digital autonomy gives MSPs control over how customer communications, data and infrastructure are deployed, managed, processed and stored. With Vodia, MSPs can build a flexible, branded communications service across cloud and on-premise environments while retaining control of pricing, service delivery, support and the customer relationship. This independence helps protect long-term account value, reduce reliance on third-party vendors and create more opportunities to expand services over time.

August 26, 2026

The World of Vodia: One Extension, Every Way You Work

Your Vodia extension is no longer tied to a single device or location. Native iOS and Android apps, the browser-based User Portal, PWA support, Vodia Hub and click-to-dial extensions provide different ways to connect with the same Vodia PBX. Make and receive business calls from your smartphone, manage communication from your browser, control calls from the Windows desktop or dial numbers directly from the applications and webpages you already use. Wherever work takes place, Vodia provides an experience designed for the device and workflow at hand.

August 20, 2026