You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Target release1.0
Epic

XQI-2015 - Getting issue details... STATUS

Document status
DRAFT
Document owner
Designer
Developers
QA

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 

ImportanceStatusNotes
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

DRAFT

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

IMPLEMENTED

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

IMPLEMENTED

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

IMPLEMENTED

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

IMPLEMENTED

Fully implemented

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

The PFK LED shall be 

  • Off, when state is "idle"
  • Blinking, when state is "ringing"
  • Steadily lit, when when state is "busy"

Must Have

IMPLEMENTED

Fully implemented

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

The default PFK LED color shall be 

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

Must Have

IMPLEMENTED

The default colour can be overridden by configuration

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

The PFK label is composed of 3 areas

  • (A) icon area
    • 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 "talking" => red symbol of a person with handset and 2 waves heading away from the handset
  • (B) name area
  • (C) state area



9D8XX_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:

  • switch off the assigned PFK LED
  • display the label icon "idle", the label name "name" or "number", the state "idle"
Must Have

10D8XX_BLF-XML_SR-2-UAC

If the SRV (IP-PBX or another Snom phone) is in State "Idle", the UA shall

  • switch off the assigned PFK LED
  • display the label icon "idle", the label name "name" or "number", the state "idle"
Must Have

11D8XX_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:

  • switch off the assigned PFK LED
  • display the label icon "idle", the label name "name" or "number", the state "idle"



12D8XX_BLF-XML_SR-4-UASIn case the notifier being an IP-PBX or another Snom phone: Ringing state => PFK LED blinking fast (colour?), PFK label & icon "ringing"Must Have

13D8XX_BLF-XML_SR-5-UASIn 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

14D8XX_BLF-XML_SR-6-UASIn case the notifier being an IP-PBX: Hold state => PFK LED blinking slow (colour?), PFK label & icon "on hold"Must Have

15D8XX_BLF-XML_SR-7-UASIn 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 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

Not Doing

  • No labels