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

Compare with Current View Page History

« Previous Version 5 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.

Assumptions

  • 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.
  • 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

#TitleFunctional ImportanceNotes
1

BLF-XML-01-00

On D8xx, any PFK (physical or virtual programmable function key) can be assigned to the function BLF.
  • In technical terms this means, that each PFK becomes a subscriber of state changes of the assigned SIP extension
2BLF-XML-01-01The 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).
3BLF-XML-01-02If 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.
4
On D8xx, during an active subscription, state changes of the monitored SIP extension shall be visualized on both, PFK LED and PFK icon & label.
5
In case the notifier being an IP-PBX or another Snom phone: Idle state => PFK LED off, PFK label & icon "idle"
6
In case the notifier being an IP-PBX or another Snom phone: Ringing state => PFK LED blinking fast (colour?), PFK label & icon "ringing"
7
In case the notifier being an IP-PBX or another Snom phone: Busy state => PFK LED on (colour?), PFK label & icon "on a call"
8
In case the notifier being an IP-PBX: Hold state => PFK LED blinking slow (colour?), PFK label & icon "on hold"
9
In case the notifier being an IP-PBX: DND state => PFK LED on (colour?), PFK label & icon "DND on"

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • No labels