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

Why MSPs Should Own the Customer Relationship in Cloud Communications

Cloud communications can create a valuable recurring revenue opportunity for MSPs, but only when they remain in control of the customer relationship. By managing branding, pricing, service delivery, and support, MSPs can build stronger customer loyalty, protect long-term account value, and expand their offering as customer needs evolve. A white-label approach also gives them the flexibility to package voice, AI, integrations, and managed services under their own brand.

July 22, 2026

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