Specifications
Administrator’s Guide for SIP-T46G IP Phone
126
To configure an LDAP key via phone user interface:
1. Press Menu->Call Feature->DSS Keys.
2. Select the desired DSS key.
3. Press or , or the Switch soft key to select Key Event from the Type field.
4. Press or , or the Switch soft key to select LDAP from the Key Event field.
5. (Optional.) Enter the string that will appear on the LCD screen in the Label field.
6. Press the Save soft key to accept the change.
Busy Lamp Field (BLF) is used to monitor a specific user for status changes on the IP
phones. For example, you can configure a BLF key on a supervisor’s phone for
monitoring the status of a user’s phone (busy or idle). When the user makes a call, a
busy indicator on the supervisor’s phone shows that the user’s phone is in use and busy.
Visual Alert and Audio Alert for BLF Pickup
The BLF pickup feature allows supervisor to pick up the incoming call of the monitored
user. The visual alert and audio alert for BLF pickup features allow the supervisor’s
phone to play an alert tone and display a visual prompt (e.g., ―6001<-6002‖, 6001 is the
monitored extension and receives an incoming call from 6002) when the monitored user
receives an incoming call. In addition to BLF key, the visual alert for BLF pickup feature
also enables the supervisor to pick up the incoming call of the monitored user by
pressing the Pickup soft key directly. The directed call pickup code must be configured
in advance. For more information on how to configure the directed call pickup code for
the Pickup soft key, refer to Directed Call Pickup on page 91.
LED Off in Idle
The LED off in idle feature defines two flashing methods for the BLF key LED. The BLF key
LED flashes as below:
Line key LED (configured as BLF key when LED Off in Idle is disabled)
LED Status
Description
Solid green
The monitored user is idle.
Solid red
The monitored user is busy.
The call is parked against the monitored user’s phone
number.
Fast flashing red
The monitored user receives an incoming call.
Off
The monitored user does not exist.