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

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

Manually Provisioning a Cisco 3PCC Phone in the Vodia PBX

Vodia now supports provisioning for Cisco 3PCC phones, giving businesses and service providers a clearer way to connect compatible Cisco multiplatform IP phones to the Vodia PBX. Admins can add supported Cisco devices through Vodia Device Management, pair them with extensions, and configure provisioning settings through the phone’s web interface. This expands Vodia’s supported device ecosystem while helping customers continue using trusted Cisco IP phones within their existing business phone system.

July 9, 2026

Vodia Hub brings click-to-call and call control to every Windows workspace

Vodia Hub for Windows brings click to call and desktop call control to Windows, making it easier for users to place, answer, manage, and automate calls from the applications they already use every day. With system wide tel: link handling, inbound call screen pops, queue details, and automation support, Vodia Hub helps connect the Vodia PBX with Outlook, CRMs, browsers, documents, and other Windows tools. Users can keep working without manually copying phone numbers, opening the user portal, or switching between applications just to handle a call.

July 7, 2026