Programming Remote DSS/BLF

Page 1
Introduction

Remote Direct Station Selection/Busy Lamp Field (Remote DSS/BLF) is a feature that
permits a phone to visually monitor (via Key) and access that monitored phone, with
standalone or across clustered 3300-ICP’s and SX2000 Systems.

Conditions

• Remote DSS/BLF works across an MSDN/DPNSS network or via an IP Trunking

network.

• Systems must be clustered and managed by locally installed OPS manager.

• Feature DN must be programmed in Cluster Element Assignment and have same

digit length as the system CEID Digits (see Cluster programming).
• It is recommended that no more than four remote systems carry busy lamp
representations of the same device. Exceeding this recommended limit may cause
BLF performance to deteriorate.

• A device or directory number may not exceed a total of 16 local and remote busy
lamp appearances.

• In a Resilient 3300-ICP clustered environment, a set programmed with resiliency,

on the Backup controller must have the DSS/BLF keys programmed as well.

• In a SX2000 clustered system environment, if a receiving system switches

activity, busy lamp indications are not automatically updated as a result of the
activity switch. Busy lamp indications are updated upon the next call activity by
their respective monitored devices on the broadcasting system(s). If a DSS key is
used prior to call activity by its remote monitored device, the device’s status is
assumed to be idle/no DND and the DSS key acts on this status.

Page 2
Programming
Programming of remote DSS/BLF is done in two steps:
1) In the local PBX (the PBX which hosts the extension that will be
monitored by remote PBX extension), using ESM only:

Enter the DN of the set that will be monitored. (Remote Busy Lamp
Assignment Form) Next, if the monitoring set is local to this node, open
the Multiline Set Key Assignment Form, Recall the monitoring extension
number, and assign the Monitored extension number to a Key as a
DSS/BLF Key with a ring type of choice. If the monitoring extension
number is on a Remote PBX, then under the Remote Busy Lamps enter
the extension numbers of the sets on the remote PBX (the PBX which
will host the extension that will Monitor an extension in another PBX).

2) This can be done using OPS Manager Move, Add and Changes or 3300
ESM Multiline Set Key Assignment Form, and Remote Busy Lamp
Assignment should be programmed for the remote PBX also. (see the
example)

Programming example:

IP Trunks or MSDN
Local PBX CEID Remote PBX CEID
111 119

Ext. 5117 on CEID 111 Ext. 4234 Has a Key

Is monitored by remote Ext. programmed as
4234 on CEID PBX Number DSS/BLF with

Extension 5117 in local PBX will be monitored by

extension 4234 on PBX CEID 119.

Page 3
Cluster Element Form

Showing the Feature DN, and same number of digits in the Cluster Elements ID Digits as
Feature DN.

Page 4
Local PBX Programming:

• Open ESM and go to System Configuration/Multiline IP sets

• Open Remote Busy Lamp Assignment form
• Click Add and enter 5117
• Click Add Member and enter 4234

Page 5
Remote PBX Programming:

• Open Ops Manager and go to Configurations then Move, Adds and

Changes Editor
• Go to the Directory number 4234 and click Change User
• Click on Key Assignment
• Choose Line Type DSS/Busy Lamp
• Put the Directory number 5117
• Choose Ring Type
• Click Change

Page 6
Remote PBX (Continued)

• Open ESM and go to System Configuration / Devices / IP Telephones /

Multiline IP sets
• Open Remote Busy Lamp Assignment form
• Click Add, and Add 6504 as a monitored device
• Do NOT add Remote Busy Lamp

Page 7
Maintenance of DSS/BLF:

If DSS/BLF keys are deleted on a Remote PBX but are NOT removed from the
originating PBX a Log for every call on the originator will be produced. A sample of this
log is shown below:

In the above example, the logs generated for DSS/BLF found under Maintenance and
Diagnostics indicate that ext 5117 is broadcasting to PBX with CEID Index number of
119 (found in the Cluster Element Form) has a Remote Busy Lamp Group (RMT Blg)
Exception. The exception is a Count Difference, meaning that the originating PBX states
there should be X number of Keys on PBX 119

But PBX 119 states that there is, only n number of keys.

To resolve this problem, Locate extension 5117 to determine which PBX this Phone is
on, then open the remote busy Lamp form, this form will state all of the remote extension
numbers 5117 is broadcasting to. In the above example the PBX that is complaining is
CEID 119, on that switch check the Remote Busy Lamp form and compare that, with the
originating PBX remote form. You would see that a Key on CEID 119 is missing for

Page 8
extension 5117. Assign extension number to a free key of the listed set from 5117 remote
form or, delete this ext from the remote busy lamp form on the home PBX of 5117.

If busy lamps are correctly programmed, but not functioning as programmed the
following

Command can be used.

Blf refresh ceid xxx where xxx is the CEID number of the destination PBX.

Page 9