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

Vodia Version 70.2 - Run Multiple Licenses on the Same Virtual Machine

V70.2 introduces more flexible licensing for multi-tenant PBX deployments by allowing service providers to assign prepaid licenses directly to tenants within a postpaid environment. Once assigned, the tenant uses the prepaid license independently, and the underlying postpaid license no longer counts that tenant. This gives MSPs and hosted PBX providers more flexibility in how they structure customer licensing while continuing to operate tenants on shared infrastructure, reducing operating costs and simplifying large-scale multi-tenant deployments.

May 26, 2026

Austrian MSP my Tweak Telekom GmbH Completes Two Vodia PBX Installations

Austrian MSP my Tweak Telekom completed two Vodia PBX deployments in Vienna, helping Pension Suzanne modernize its hotel communications and enabling New Business Verlag GmbH to upgrade from a legacy on-premise phone system to a hosted cloud PBX. The projects demonstrate how businesses can modernize legacy telephony infrastructure, improve operational flexibility, preserve existing hardware investments, and deliver better communication experiences with cloud-based unified communications.

May 21, 2026

Vodia PBX V70 Webinar: Admin Interface, Analytics, AI, and Multi-Tenant Performance - Recording Now Available

Watch the Vodia PBX V70 webinar on demand and explore the latest improvements in the Vodia PBX, including the redesigned admin interface, built-in PBX analytics, AI voice agents, automation, and scalable multi-tenant performance. The session also covers snapshots, centralized provisioning, emergency alerts, skills-based routing, and integrations with Jitsi Meet and WhatsApp Business in real-world deployment environments.

May 19, 2026