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

How to Sell More Business Phone Systems with the Right PBX

Helping a business choose the right phone system starts with understanding its real needs... lower costs, better communication, stronger integrations, support for remote teams and more flexibility. For MSPs, asking the right questions makes it easier to recommend the right features, hardware and deployment model, while Vodia provides the technology, partner support and new Partner Portal needed to build stronger customer relationships, create recurring revenue and grow their communications business.

July 16, 2026

Handle with Care: Avoid These Cloud Migration Missteps

Moving your business phone system to the cloud can improve flexibility, scalability, mobility, and access to modern communication tools, but a successful migration still requires careful planning. From bandwidth and hardware compatibility, disaster recovery, staff readiness, and MSP support, there are several areas businesses need to assess before deployment. Understanding these common risks early can help reduce disruption, avoid unexpected costs, and create a more reliable cloud communication environment.

July 14, 2026

Manually Provisioning a Cisco 3PCC Phone in the Vodia PBX

Vodia now supports provisioning for Cisco 3PCC phones, giving businesses and service providers a clearer way to connect compatible Cisco multiplatform IP phones to the Vodia PBX. Admins can add supported Cisco devices through Vodia Device Management, pair them with extensions, and configure provisioning settings through the phone’s web interface. This expands Vodia’s supported device ecosystem while helping customers continue using trusted Cisco IP phones within their existing business phone system.

July 9, 2026