| Target release | 1.0 |
|---|---|
| Epic | |
| Document status | |
| Document owner | |
| Designer | |
| Developers | |
| QA |
|
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.
| # | Title / Requirement number | User story / functionality | Importance | Notes | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | BLF-XML-01-00 | On D8xx series, any PFK (physical or virtual programmable function key) can be assigned to a function, which allows monitoring state changes of that SIP extension. This function shall be called "BLF-XML". The following state changes are requested
| Must Have | This means, that each PFK of the User Agent (UA, here Snom D8xx) becomes a subscriber of state changes of the assigned SIP extension on another Server (SRV) | |||||||||||||||
| 2 | BLF-XML-01-01 | If such SIP extension is configured on other Snom phones in the same SIP domain BLF shall work transparantly without the need of an IP PBX. | Must Have | This means, that any Snom phone, acting as SRV, is capable of sending its state via NOTIFY messages to the UA | |||||||||||||||
| 3 | BLF-XML-01-02 | 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 | Already implemented | |||||||||||||||
| 4 | BLF-XML-02 | On D8xx series, during an active subscription, state changes of the monitored SIP extension shall be visualized on both, PFK LED and PFK label. The PFK label is composed of 3 areas: Label icon, name, and state | Must Have |
| |||||||||||||||
| 5 | BLF-XML-02-SRV_IDLE | 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 | ||||||||||||||||
| 6 | BLF-XML-02-UA_IDLE | If the SRV (IP-PBX or another Snom phone) is in State "Idle", the UA shall
| Must Have | ||||||||||||||||
| 7 | BLF-XML-03-SRV_SEIZ | 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:
| |||||||||||||||||
| 8 | BLF-XML-02-03 | 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 | ||||||||||||||||
| 9 | BLF-XML-02-04 | 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 | ||||||||||||||||
| 10 | BLF-XML-02-05 | In case the notifier being an IP-PBX: Hold state => PFK LED blinking slow (colour?), PFK label & icon "on hold" | Must Have | ||||||||||||||||
| 11 | BLF-XML-02-06 | In case the notifier being an IP-PBX: DND state => PFK LED on (colour?), PFK label & icon "DND on" | Must Have |
| 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 | |||
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |
