Current Location ：
Busy Lamp Field and Presence: Making Extension State Visible
Busy lamp field is the least glamorous feature on a business phone and one of the most consequential for daily work. When it is accurate, a receptionist knows not to transfer into a call and a colleague knows when to walk over instead of ringing. When it is wrong, people learn to ignore it, and the feature becomes decoration. This article covers how presence is produced, why it goes stale, and how to scope it so that it stays both useful and affordable for the platform.
How the State Gets There
A phone showing a colleague's state does not poll the platform; it subscribes to notifications. Each subscription is a small, persistent relationship that the platform must maintain and update. Ten lamps on one phone means ten subscriptions from that phone, and the platform tracks all of them across the estate. Multiply by several hundred handsets and the subscription count becomes a capacity consideration rather than a detail.
| Consideration | Effect | Practical guidance |
|---|---|---|
| Subscriptions per phone | Platform memory and update load | Cap BLF keys per device to what the role needs |
| Number of watchers per extension | Fan-out of each state change | Restrict watched extensions to team members |
| Update frequency | Signalling traffic on state changes | Accept batching where the platform offers it |
| Device behaviour on reconnect | Burst of resubscriptions after an outage | Check platform limits for restart bursts |
| Cross-site watching | Traffic across wide area links | Keep presence local unless genuinely needed |
Why Presence Goes Stale
Presence reflects what the platform knows, and it knows what devices tell it. A softphone closed without logging out can leave an extension showing available. A handset unplugged mid-call can leave a lamp lit. A forwarded extension may show idle while calls are actually being answered elsewhere. None of these are faults in the strict sense; they are the difference between device registration state and human availability, and users interpret the lamp as the latter.
- Explain the difference between device state and human availability during rollout
- Set registration timeouts that match how devices actually disconnect
- Review forwarding behaviour, which is where state and reality diverge most often
- Avoid using presence as the only input to an automated routing decision
- Provide a manual status option where the platform supports it, and train people to use it
Scope It to the Role
Reception and attendant roles justify wide visibility: the whole point is knowing who is free. A finance team needs its own members and little else. A field team may need only a shared queue indicator. Designing BLF by role keeps subscription counts sane and keeps the displayed information meaningful, which is more valuable than covering every extension in the organisation.
When Presence Should Not Decide
Presence is a guide, not a guarantee. Automatically routing a customer to whoever appears idle can send them to someone in a meeting with a phone on the desk, or to an extension registered on a device nobody is near. For customer-facing routing, use explicit availability: a queue login, a status selection, or a schedule. Presence informs people; it should not silently make promises to callers.
Redstone Approach
Redstone IP handsets and IP-PBX platforms support busy lamp field with configurable key assignments and subscription limits documented per platform model. Our design guidance scopes BLF by role and tests subscription behaviour after a restart, since the burst of resubscriptions is where capacity assumptions are usually tested hardest.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
