...
- Use case#1: A secretary's phone shall display the call status of the boss's line, allowing the secretary to know whether the boss is on a phone call or not. This will enable the secretary to make the decision to put the new caller on hold or let them through to the boss.
- Use case#2: Call centers and customer support groups have also a need for BLF: it enables employees to see if their colleagues are free to take a support call or if their supervisor is on another line and unable to help another customer.
- Use case#3: BLF is needed by teams working on a specific project: supervisors can monitor team members' extensions and vice versa so all team members are aware of each other's current status.
Requirements
# | Title / Requirement numbertitle | Functionality User story / functionality | Importance | Notes | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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:
| 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:
| Must Have | Fully implemented for idle, ringing, busy | |||||||||||||||||||||
3 | D8XX_BLF-XML_FR-3 | The 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 | |||||||||||||||||||||
4 | D8XX_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 | |||||||||||||||||||||
5 | D8XX_BLF-XML_FR-1-1-1 | The PFK LED behaviour and colour shall be according to this table
| Must Have | Fully implemented | |||||||||||||||||||||
6 | D8XX_BLF-XML_FR-1-1-2 | The PFK label shall be composed of 3 areas:
| Must Have | Fully implemented | |||||||||||||||||||||
7 | D8XX_BLF-XML_FR-1-1-2-1 | The label icon area (A) shall contain the following distinguishable graphical symbol, representing the state
| Must Have | Fully implemented | |||||||||||||||||||||
8 | D8XX_BLF-XML_FR-1-1-2-2 | The label name area (B) shall contain the following text representing the display name or number (configurable) of the monitored / calling party
| Must Have | Partly implemented | |||||||||||||||||||||
9 | D8XX_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)
Suggestion: state |
| Must Have |
label state | idle | ringing | busy
| Must Have | Fully implemented |
User interaction and design
User interaction | Requirement reference | Protocol reference | Design reference | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
UAS | UAC | State | UAS | UAC | UAS | UAC | Figma | Screenshot | |||||||||||
does nothing | does nothing | Idle | BLF-XML-02-SRV_IDLE | BLF-XML-UA-02-02 | Figma requirement (702 "idle") | ||||||||||||||
lifts up the receiver | does nothing | Busy | BLF-XML-SRV-02-02 |
| |||||||||||||||
Questions
Below is a list of questions to be addressed as a result of this requirements document:
...