Goals
- Align BLF and Extension behavior for PFKs on Snom desk phones by using XML definitions instead
- Improve user experience
- Improve performance
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
- 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 number | User story / functionality | Importance | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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:
| 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:
| Must Have | Fully implemented for idle, ringing, busy | ||||||||
| 3 | D8XX_BLF-XML_FR-2 | If 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 | ||||||||
| 4 | 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 | ||||||||
| 5 | D8XX_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 | ||||||||
| 6 | D8XX_BLF-XML_FR-1-1-1-UAC | The PFK LED shall be
| Must Have | Suggestion:
| ||||||||
| 7 | D8XX_BLF-XML_FR-1-1-2-UAC | The default PFK LED color shall be
| Must Have | The default colour can be overridden by configuration | ||||||||
| 8 | D8XX_BLF-XML_FR-1-1-3-UAC | The PFK label shall be composed of 3 areas:
| Must Have |
| ||||||||
| 9 | D8XX_BLF-XML_FR-1-1-3-1-UAC | The icon area (A) shall contain the following symbol, representing the state
| Must Have | Suggestion:
| ||||||||
| 10 | D8XX_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)
| Must Have | Suggestion:
| ||||||||
| 11 | D8XX_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)
| Must Have | Suggestion:
| ||||||||
| 12 | D8XX_BLF-XML_SR-2-UAS | If the SRV (Snom phone) goes into State "Idle", a NOTIFY message shall be sent to the UA, containing the following information in its XML body:
| Must Have |
| ||||||||
| 13 | D8XX_BLF-XML_SR-2-UAC | If the SRV (IP-PBX or another Snom phone) is in State "Idle", the UA shall
| Must Have | |||||||||
| 14 | D8XX_BLF-XML_SR-3-UAS | If the SRV (Snom phone) goes into State "Line seizing", a NOTIFY message shall be sent to the UA, containing the following information in its XML body:
| ||||||||||
| 15 | D8XX_BLF-XML_SR-4-UAS | In case the notifier being an IP-PBX or another Snom phone: Ringing state => PFK LED blinking fast (colour?), PFK label & icon "ringing" | Must Have | |||||||||
| 16 | D8XX_BLF-XML_SR-5-UAS | In case the notifier being an IP-PBX or another Snom phone: Busy state => PFK LED on (colour?), PFK label & icon "on a call" | Must Have | |||||||||
| 17 | D8XX_BLF-XML_SR-6-UAS | In case the notifier being an IP-PBX: Hold state => PFK LED blinking slow (colour?), PFK label & icon "on hold" | Must Have | |||||||||
| 18 | D8XX_BLF-XML_SR-7-UAS | In case the notifier being an IP-PBX: DND state => PFK LED on (colour?), PFK label & icon "DND on" | Must Have |
User interaction and design
| User interaction | Requirement reference | Design reference | ||||
|---|---|---|---|---|---|---|
| SRV | UA | State | SRV | UA | 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:
| Question | Outcome |
|---|---|