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

The New Vodia Partner Portal and Partner Program

The new Vodia Partner Portal and Partner Program provide a streamlined, self-service way for partners to license, sell, and deploy Vodia PBX solutions more efficiently. Shaped by partner feedback, the portal brings license management, partner levels, pre-qualified leads, marketing resources, and access to professional services into one place. Partner certification unlocks progression beyond onboarding, while a welcome package rewards partners at first login.

February 26, 2026

Continued Growth in the Global VoIP Marketplace

VoIP adoption continues to grow as enterprises and SMBs move away from legacy phone systems toward cloud-based communication that supports remote and hybrid work. Market forecasts show sustained expansion driven by cost efficiency, flexibility, and unified communications, while modern PBX platforms evolve to deliver scalable, reliable voice services with advanced features such as video, integrations, and AI-ready capabilities.

February 25, 2026

Cisco IP Phone Series 6800, 7800 and 8800 with the Vodia PBX

Cisco IP Phone Series 6800, 7800, and 8800 devices running Multiplatform (MPP / 3PCC) firmware can be used with the Vodia PBX in SIP-based environments. Supported models span entry-level, mid-range, and advanced devices commonly deployed in enterprise and service provider scenarios. Cisco-provided MPP firmware is used, with firmware versions and upgrades managed through the PBX after initial onboarding, supporting both on-premises and cloud deployments.

February 19, 2026