Busy Indicator

Last Updated : Jan 29, 2020 |
Prolog information
Metadata
Keywords:
  • CS 1000 endpoint user experience
    The Busy Forward Status (BFS) feature of CS 1000 is similar to the Busy Indicator feature of Device Adapter, but with some differences.
    BFS provides multi-appearance telephone users and attendants with a visual indicator of the busy or idle status of a phone. This feature is typically used in a boss-secretary scenario.
    For example, phone A is secretary’s phone and phone B is boss’s phone.
    Configure the BFS key on phone A. The format is KEY xx BFS <TN of SET B>. Phone A monitors the state of phone B. Depending on the state of phone B, the BFS key on phone A shows the following status:
    • Dark lamp: Phone B is idle.
    • Lit lamp: Phone B is on a call.
    • Flashing lamp: Phone B is call forwarding all calls to phone A.
    The phone A user can use the BFS key to transfer the call to phone B. While phone A is on a call with some other party, the phone A user can press the BFS key to call phone B, and then press the BFS key again to transfer the call to phone B.
    However, as compared to the Avaya Aura® Busy Indicator (BI) button, the BFS key in CS 1000 has the additional capability to call forward all calls on behalf of another user extension.
    In CS 1000, to call forward all calls from phone B to phone A, the phone A user can press the BFS key that is configured to provide busy status indications for the phone B extension.
    In Avaya Aura®, a system administrator can configure a call-fwd button for phone A. The default label for this button on the phone is Forward. Phone A user can specify the extension number of phone B for this Forward key, and use this Forward key to manage call forward all calls on behalf of phone B.
  • Communication Manager endpoint user experience
    Use the Busy Indicator feature to provide multi-appearance telephone users and attendants with a visual indicator of the busy or the idle status of one of the following system resources:
    • An extension number.
    • A trunk group.
    • A terminating extension group (TEG).
    • A hunt group, either direct department calling (DDC) or uniform call distribution (UCD).
    • Any loudspeaker paging zone, including all zones.
    A SIP phone can support only another extension.
    You can assign extension numbers, trunk group access codes, and loudspeaker paging access codes to a Busy Indicator (BI) button.
    The Busy Indicator button provides an attendant or a user with direct access to the extension number, the trunk group, or the paging zone. The Facility Busy lamp indication for a Vector Directory Number (VDN) is not On when the VDN is being used. You can use the associated button to place a call to a VDN.
    For example, phone A is secretary’s phone and phone B is boss’s phone.
    After an administrator configures the busy-ind button feature for phone A, phone A monitors the state of phone B.
    Depending on the call status of phone B, the BI button lamp on phone A changes to lit or dark. The button function is indication only. User can press the button, but it is ignored by the phone. However, unlike the CS 1000 BFS feature, there is no indication of the forwarded status.
    Instead, Communication Manager provides a Call Forward button to forward calls on behalf of the monitored user extension. For example, if a Call Forward button is configured on phone A on behalf of phone B, the phone A user can use this button to manage Call Forward on behalf of phone B.
    Separate BI and Call Forward buttons allow a user to use the Busy Indicator and Call Forward features separately.
  • Device Adapter endpoint user experience
    BFS equivalent capability of monitoring the busy status of a monitored extension and dialing the monitored extension
    The Busy Indicator feature of Device Adapter is similar to the Busy Forward Status (BFS) feature of CS 1000, but with some variations.
    The Busy Indicator (BI) button is mapped to the BFS key on the secretary’s phone. This button appears as the BusyFwd button on the secretary’s phone. This button provides BFS equivalent capability of monitoring the status of the boss’s extension and transferring calls from the secretary’s phone to the boss’s extension.
    For example, phone A is secretary’s phone and phone B is boss’s phone.
    After an administrator configures the busy-ind button feature for phone A, phone A monitors the state of phone B.
    Depending on the BI status of phone B that Device Adapter receives from Communication Manager, the lamp state on phone A changes to the following:
    • Dark lamp: Phone B is idle.
    • Lit lamp: Phone B is on a call.
    When the phone A user presses the BusyFwd button in a dialing state, Device Adapter dials the BI number of phone B.
    Phone A user can perform the following steps to transfer a call to phone B:
    1. While on the call, press the Transfer button.
    2. Press the BusyFwd button.
    3. Press the Transfer button.
      Device Adapter transfers the call to the BI number of phone B.
    When the phone A user presses the BusyFwd button in an idle state, Device Adapter automatically selects the lowest idle line appearance, and dials the BI number of phone B.
    BFS equivalent capability of managing Call Forward on behalf of another user extension
    In Device Adapter, unlike CS 1000, the BusyFwd button on phone A does not Call Forward All Calls (CFW) of phone B to phone A. Instead, an administrator can configure another call-fwd button for phone A, which the phone A user can use to manage CFW on behalf of phone B.
    Although the ProVision tool can provide the Busy Indicator, including the dial capability associated with BFS, the ProVision tool does not automatically provide the call forward handling.
    In a CS 1000 environment, the BFS key has three roles. Whether all the three roles apply depends on the following contexts:
    • All locations use the ability to monitor the status of the called extension. This allowed departmental administration assistants a mechanism to track the status of the members of the department. This frequently required more than 10 BFS keys.
      In Device Adapter, the Busy Indicator button provides this capability.
    • The ability to use the BFS key to transfer calls to the associated extension or to auto-dial the extension programmed at that key. This capability was used only in a few scenarios, such as, the administrative assistant wanted to transfer a call to a target.
      In Device Adapter, the Busy Indicator button provides this capability.
    • In a subset of cases in CS 1000, the BFS key can also be used to call forward all calls on behalf of the monitored extension. In some cases, an administrative assistant might have to monitor the status of two or more extensions.
      This function is not available with the Busy Indicator button in Device Adapter. However, in Device Adapter, the programmable call-fwd button provides the capability to call forward all calls on behalf of a monitored extension, also referred to as the “CFW controlled” extension. Because this capability is not always used and consumes an extra button, a system administrator must first identity the extensions that an administrative assistant wants to monitor and manually configure the call-fwd buttons only for such extensions. ProVision does not map this button.
For more information, see Busy Indicator in Appendix H: Call processing features and services.