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.

Derniers articles

Voir tous

Building Intelligent Voice Response Systems with Vodia's JavaScript IVR

JavaScript IVR transforms the way businesses handle incoming calls by enabling fully customizable, intelligent phone menu systems. Unlike static IVR setups with limited, pre-defined options, JavaScript IVR allows you to create dynamic call flows that adapt in real time based on caller input, business data, or even external API integrations. This means you can route calls more efficiently, automate complex processes, and offer highly personalized experiences to your customers. Whether you want to check customer records before transferring a call, adjust menu options based on time of day, or integrate with CRM systems for instant data access, JavaScript IVR gives you the flexibility and control to make it happen - all while improving efficiency and enhancing caller satisfaction.

August 11, 2025

Get The Support You Need Easily Through The Vodia Help Center On Jira

Vodia support is now easier to access through the Vodia Help Center on Jira, giving partners and customers a centralized platform to submit technical support tickets, ask sales or licensing questions, and suggest new features. With a valid license key, users can open detailed requests and track their status in one place. The portal also brings together Vodia documentation, the PBX API, and the Vodia forum, making it the go-to resource for everything Vodia. Whether you're troubleshooting, planning an upgrade, or just need guidance, the Help Center is designed to streamline your experience and connect you with the right support faster.

August 7, 2025

Vodia Attends ChannelCon 2025 in Nashville

At ChannelCon 2025 in Nashville, Vodia Sales Engineer Eric Altman engaged with MSPs and IT professionals to explore how AI is shaping the future of managed services. He emphasized that ChannelCon remains a valuable space for building strong vendor-partner relationships, especially as AI continues to dominate industry conversations. Altman noted how Vodia is helping MSPs unlock greater flexibility by combining powerful PBX features with AI-driven capabilities like dynamic call analytics, customized call flows, and automated performance reporting. He also highlighted Vodia’s recent launch of prepaid cloud instances on AWS, DigitalOcean, and Microsoft Azure, designed to streamline deployment for MSPs without infrastructure or licensing delays.

August 5, 2025