Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 

ImportanceNotes
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:

  • 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

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:

  • from any state => idle
  • from any state => ringing
  • from any state => busy

Must Have

Fully implemented for idle, ringing, busy

3D8XX_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

Fully implemented
4D8XX_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

5D8XX_BLF-XML_FR-1-1-1

The PFK LED behaviour and colour shall be according to this table

stateidleringingbusy
LED behaviouroffblinkingon
LED colour-redred


Must Have

Fully implemented

6D8XX_BLF-XML_FR-1-1-2

The PFK label shall be composed of 3 areas:

Label area

Screenshot

(A) icon area

(B) name area

(C) state area


Must Have

Fully implemented

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

The label icon area (A) shall contain the following distinguishable graphical symbol, representing the state

BusyImage Removedwhite symbolized red symbolized red symbolized
stateStateidleringingbusyGraphics
IdleImage Removed
RingingImage Removed
Descriptionperson with a handsetperson with a handset plus an arrow (pointing towards the handset)person with a handset and 2 sound waves (heading away from the handset)
Graphical symbol
IdleImage Added
RingingImage Added
BusyImage Added
Colourwhiteredred


Must Have

Fully implemented

8D8XX_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

stateidleringingbusy
rolesMonitored partyCalling party > monitored partyCalling party <> monitored party
nametext101 or Alex102 > 101 or
Alice > Alex
102 <> 101 or
Alice <> Alex
text colourwhitewhitewhite


Must Have

Partly implemented

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

state
"idle" =>
idle
state "
ringing
" => ringing
state "busy" =>

Suggestion:

state
busy

Must Have

text
idleringingbusy
label stateidleringingbusy
colourwhitewhitewhite


Must Have

Fully implemented

User interaction and design

User interaction
Requirement referenceProtocol referenceDesign reference
UASUACStateUASUACUASUACFigmaScreenshot
does nothingdoes nothingIdleBLF-XML-02-SRV_IDLEBLF-XML-UA-02-02

Figma requirement (702 "idle")

lifts up the receiverdoes nothingBusyBLF-XML-SRV-02-02


Code Block
languagexml
titleNOTIFY
linenumberstrue
collapsetrue
NOTIFY sip:100@192.168.245.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.245.251:36875;branch=z9hG4bK-1hme5acn2zd8;rport
Route: <sip:siproxd@192.168.245.1:5060;lr>
From: <sip:101@192.168.245.1>;tag=k14lafa6rw
To: <sip:100@192.168.245.1>;tag=ln0uxj71y5
Call-ID: c762ff638733-fp153x4v9gra
CSeq: 13 NOTIFY
Max-Forwards: 70
User-Agent: snomD865/8.10.1.202301282023
Contact: "B" <sip:101@192.168.245.251:36875;line=qvtqfzps>;reg-id=1
Event: dialog
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 227

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="12" state="full" entity="sip:101@192.168.245.1"><dialog id="f4bc7284a6be6f1d1765ec8dea13a860" ><state>trying</state></dialog></dialog-info>













































































Questions

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

...