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

MEDICA 2026: Why the Future of Healthcare Needs a Voice

What is a telephony vendor doing at the world's largest medical trade fair? After four days at MEDICA 2026 in Düsseldorf, we reflect on a challenge that runs through every hospital, practice and care home: finding time for conversation as administrative demands grow and resources shrink. From AI that supports everyday calls to resilient infrastructure that keeps people connected, we explore how voice communication can help healthcare teams protect that time, improve care and create new opportunities for collaboration.

November 19, 2026

Cloud or on-premises? Rethinking phone system reliability after a Microsoft outage

The latest Microsoft outage raises a familiar question: does every service need to run in the cloud? For business phone systems, reliability depends on the infrastructure, the people managing it and the backup options available. An on-premises PBX can keep local communications running during an internet outage, while distributing systems across locations can help limit the impact of individual failures.

November 17, 2026

A PBX That Lets You Build It Your Way

Every business handles calls differently, and its phone system should support those differences. Vodia PBX gives businesses and service providers the flexibility to shape call flows, configure individual tenants and extensions, and build a branded experience for their customers. Queues, ring groups, schedules, forwarding, and AI agents can work together around each team’s requirements, while the REST API connects the phone system with wider business workflows.

November 11, 2026