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

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026