Tech

Disable pickup on a BLF

Published on:

October 12, 2018

In Vodia PBX version 60.3, users can now customize call pickup LED behavior by adding "no" to the pattern syntax, preventing the LED from blinking. This feature is useful in scenarios where specific permissions are required, such as limiting call pickup on a manager's phone to selected extensions. The enhancement ensures flexibility without sacrificing backward compatibility, providing a more user-friendly experience.

It’s usually quite useful to be able to pick up calls by pressing a fast-blinking LED on your VoIP phone. This has become a standard feature on most IP-PBXs today, and practically all VoIP phones support it. 

There are, however, some situations wherein you don’t want to press the LED - sometimes the LED should just come on without blinking, so the user can see the extension or resource is busy. This can be a problem of permission, when users shouldn’t be able to pick up calls, e.g., on a manager’s phone only certain, predetermined extensions should be able to retrieve that call. 

A blinking LED actually "promises" pressing the LED will pick up an incoming call. This wasn’t always the case with the Vodia PBX; it could happen the LED was blinking, but the user might press the button and find it wasn’t possible to pick up the call. This didn’t result in a good user experience, so we decided to correct it. 

In every account we had the field, "permissions to monitor this account" (pretty much from the beginning), and this was a flexible way to define who could see the status on the resource. This list could exclusively show extensions or use simple patterns to define the permissions.

The problem was the LED was either dark or lighted - what we needed was a mode between these two states that would just enable on/off status. We discussed adding another field to define this, but it turned out a simple extension of the pattern syntax was easier.

Beginning with version 60.3, the PBX would look for a flag, “no” (for no pickup) behind the pattern. This way it would be easy to mix the permissions, e.g., the pattern "44 55:np 5*" would mean extension 44 can see anything, extension 55 would only see on/off status and other extensions beginning with 5 would see everything. The pattern is backward compatible with previous versions, so there’s no worry about behavior in upgrades. 

Latest Articles

View All

Podcast | Why Hotel Room Phones Still Matter in the Age of AI

Hospitality is undergoing a major shift as AI and cloud telephony reshape guest interactions. In this podcast, Christian Stredicke discusses which changes genuinely improve hotel operations and guest experience, why room phones still matter, and how modern PBXs can balance automation with the human touch that defines real hospitality. He also examines on-prem versus cloud deployments, renovation timing, emergency calling, and the ways the right system can reduce costs while raising service quality.

December 10, 2025

Seamless Compatibility: Htek and Vodia Announce Joint Webinar

Vodia and Htek are hosting a joint webinar to showcase the seamless compatibility between the Vodia PBX and Htek’s full IP phone lineup, including the UCV(Pro) smart video series and UC900 business phones. Eric Altman and Hector Hao will present key insights on product capabilities, cost-effective deployment, industry use cases, and provisioning workflows, with Stephen Yu joining for live Q&A. Attendees will learn how the combined Vodia Htek solution delivers a powerful, scalable communications experience for education, hospitality, and other sectors.

December 9, 2025

FCC Revises Cybersecurity Requirements for Telecommunications Companies

The FCC has reversed its January 2025 cybersecurity ruling for telecom providers, eliminating the proposed national standards and annual certification requirements under CALEA. The change reduces formal compliance obligations, but it does not lessen the risks facing carriers as cyberattacks grow more frequent and more sophisticated. The reversal underscores how essential it is for service providers to rely on platforms built with strong inherent protections.

November 27, 2025