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

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 (UAC) and the IP phone of the monitored extension acts as User Agent Server (UAS).

2

D8XX_BLF-XML_FR-2

On Snom IP phones acting as UAS, 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-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
4D8XX_BLF-XML_FR-1-1

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

5D8XX_BLF-XML_FR-1-1-1

The PFK LED behaviour and colour shall be according to this table

stateidleringingbusy
LED behaviouroffblinkingon
LED colour-redred


Must Have

Fully implemented

6D8XX_BLF-XML_FR-1-1-2

The PFK label shall be composed of 3 areas:

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

Must Have

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

The label 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
label icon
Idle
Ringing
Busy


8D8XX_BLF-XML_FR-1-1-2-2

The label 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
label name101 or Alex102 > 101 or
Alice > Alex
102 <> 101 or
Alice <> Alex


9D8XX_BLF-XML_FR-1-1-2-3

The label 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
label stateidleringingbusy


User interaction and design

User interaction
Requirement referenceDesign reference
UASUACStateUASUACFigmaScreenshot
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