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. 

Derniers articles

Voir tous

Connecting to OpenAI Realtime API

This document details the beta version of the Vodia PBX that connects to the OpenAI realtime API, enabling users to interact with a chatbot via telephone. The backend JavaScript code facilitates the connection, handling audio input and output, and the WebSocket connection to the OpenAI API. The setup requires a Vodia PBX version 69.5.3 or higher, an API key, and a license with an IVR node. The demo can be accessed by editing the ivrnode.js template and creating an IVR node in the tenant. The system supports various VoIP devices and offers good voice quality. Future improvements include voice activity detection and the ability to take actions based on OpenAI responses.

November 26, 2024

How Vodia Helps Hotels Not Disturb Their Guests

Vodia’s cloud PBX system enhances the Do-Not-Disturb (DND) function for hotels, allowing guests to manage their privacy through buttons in the room or on the phone. The system syncs with PMS for seamless functionality, enabling hotel operators to manually override DND when guests struggle to disable it. For critical situations, like room service follow-ups, the system allows specific extensions to bypass DND, ensuring guests are reachable when needed. VIP guest management features, guest-to-guest call restrictions and automatic resets upon checkout ensure privacy, security, and convenience, improving the guest experience while maintaining operational efficiency.

October 22, 2024

WLAN and VoIP: What You Need to Know

As businesses increasingly adopt Wireless Local Area Networks (WLAN), understanding its impact on Voice over IP (VoIP) is essential. While WLAN offers flexibility and mobility, it can lead to call quality issues due to packet loss and bursts during access point switching. To combat these challenges, organizations can utilize robust codecs like OPUS which are designed to handle packet loss effectively and employ Session Border Controllers (SBCs) to enhance jitter buffers. By incorporating these solutions, companies can ensure a more reliable VoIP experience that meets the demands of modern workplaces, allowing seamless communication without interruptions.

October 10, 2024