BLF configuration modes
The following are the two configuration modes for Busy Lamp Field which determine the way of
setting its keys’ location and the list of BLF users:
• If the BLF_LIST_URI parameter value is provided in the
46xxsettings.txt
file or in the
web interface of the Administration menu, the BLF PHONEKEY value does not require any
attribute, for example:
SET PHONEKEY "Key=1;Type=feature;Name=blf"
In this case, only one PHONEKEY record is required which specifies the initial position of the
BLF list. The key label is ignored and therefore should not be provided.
Important:
It is recommended to set BLF PHONEKEY value with the
Forced
flag in this mode.
Note:
This mode is supported in the Broadworks and Asterisk environments.
• If the BLF_LIST_URI parameter value is not provided in the
46xxsettings.txt
file or in
the web interface of the Administration menu, the BLF phone key value must specify a
particular phone extension as
attr1
. In RingCentral environment the BLF phone key value
must specify a particular BLF ID or User ID as
attr1
and phone extension as
attr2
. If you
specify a null as
attr2
, specify phone extension as
attr1
.
Apart from specifying the phone extension, it is also possible to provide the value in the
format, for example:
SET PHONEKEY
"Key=1;Type=feature;Name=blf;[email protected];attr2=88053;Label=1234_BLF"
In this mode, several PHONEKEY records can be provided to specify all monitored users.
Note:
This mode is supported in the 3CX , Asterisk, and RingCentral environments.
Related links
on page 489
Nesting of WML elements
The following table gives an overview of WML elements and shows which elements can be
contained, or nested, within other elements:
1
2
3
4
5
6
7
8
9
wml
card
do
go
postfield
Table continues…
Customizable parameters
April 2020
Installing and Administering Avaya J100 series IP Phones in an Open SIP
environment
494