Target release1.0
Epic

Document status
Document owner
Designer
Developers
QA


Goals

Background and strategic fit

BLF is a valuable feature for Snom customers, like enterprises who are looking to assist in connecting their customers to a live, available person as well as save business phone use time. Overall, it enables businesses to streamline their communication and better serve customers. BLF aka Extension monitoring has been utilized in numerous ways by businesses using Snom phone systems with multiple extensions. The current implementation appears to be kind of duplicated, but with a few little differences and erroneous behaviour.

Assumptions

Requirements

#

Title / Requirement number

User story / functionality 

ImportanceNotes
1

D8XX_BLF-XML_FR-1-UAC

On D8xx IP phones, any PFK (programmable function key - physical or virtual) can be assigned to a function, which allows monitoring state changes of the configured SIP extension on another IP phone. This function shall be called "BLF-XML". The following state changes shall be visualized:

  • monitored SIP extension is in idle mode => idle
  • monitored SIP extension receives an incoming call => ringing
  • monitored SIP extension dials or accepts an incoming call => busy

Must Have

This means, that the D8xx phone acts as a User Agent Client and the IP phone of the monitored extension as a User Agent Server (UAS).

2

D8XX_BLF-XML_FR-1-UAS

On Snom IP phones, any SIP extension having an active subscription of its state changes, shall sent a notification SIP message (NOTIFY) to the UAC, at least when one of the following state changes occur:

  • from any state => idle
  • from any state => ringing
  • from any state => busy

Must Have

Fully implemented for idle, ringing, busy

3D8XX_BLF-XML_FR-2If such SIP extension is configured on other Snom phones in the same SIP domain, BLF shall work transparantly without the need of a B2BUA (IP PBX)

Must Have

Fully implemented
4D8XX_BLF-XML_FR-3The assignment shall be configured either manually via web user interface (WUI) and/or phone user interface (PUI), and automatically via auto-provisioning (HTTP/TFTP setting server), SRAPS, or remote management (TR-069).

Must Have

Fully implemented
5D8XX_BLF-XML_FR-1-1-UAC

On D8xx series, during an active subscription, state changes of the monitored SIP extension shall be visualized on both, PFK LED and PFK label.

Must Have

Fully implemented

6D8XX_BLF-XML_FR-1-1-1-UAC

The PFK LED shall be 

  • state "idle" => off
  • state "ringing" => blinking
  • state "busy" => on

Must Have

Suggestion:

stateidleringingbusy
LEDoffblinkingon
colour-redred


7D8XX_BLF-XML_FR-1-1-2-UAC

The default PFK LED color shall be 

  • red, when state is "ringing" or "busy"

Must Have

The default colour can be overridden by configuration

8D8XX_BLF-XML_FR-1-1-3-UAC

The PFK label shall be composed of 3 areas:

  • (A) icon area
  • (B) name area
  • (C) state area

Must Have

9D8XX_BLF-XML_FR-1-1-3-1-UAC

The icon area (A) shall contain the following symbol, representing the state

  • state "idle" => white symbol of a person with handset
  • state "ringing" => red symbol of a person with handset plus an arrow pointing towards the handset
  • state "busy" => red symbol of a person with handset and 2 waves heading away from the handset

Must Have

Suggestion:

stateidleringingbusy
Icon
Idle
Ringing
Busy


10D8XX_BLF-XML_FR-1-1-3-2-UAC

The name area (B) shall contain the following text representing a display name or number (configurable) in default colour "white" (fix)

  • state "idle" => Monitored party
  • state "ringing" => Calling party > monitored party
  • state "busy" => Calling party <> monitored party

Must Have

Suggestion:

stateidleringingbusy
Name101 or Alex102 > 101 or
Alice > Alex
102 <> 101 or
Alice <> Alex


11D8XX_BLF-XML_FR-1-1-3-3-UAC

The state area (C) shall contain the following text representing the state in default colour "white" (fix)

  • state "idle" => idle
  • state "ringing" => ringing
  • state "busy" => busy

Must Have

Suggestion:

stateidleringingbusy
Stateidleringingbusy


User interaction and design

User interaction
Requirement referenceDesign reference
SRVUAStateSRVUAFigmaScreenshot
does nothingdoes nothingIdleBLF-XML-02-SRV_IDLEBLF-XML-UA-02-02Figma requirement (702 "idle")

lifts up the receiverdoes nothingBusyBLF-XML-SRV-02-02


























































Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
(e.g. How we make users more aware of this feature?)Communicate the decision reached

Not Doing