Configuring an endpoint for Busy Indicator and call forwarding on behalf of another user station

Last Updated : Oct 21, 2019 |
Prolog information
Metadata
Keywords:
A system administrator can use this procedure to configure Busy Indicator and enable a user station to Call Forward All Calls (CFW) on behalf of another user station.
Note:
  • CS 1000 and the station firmware of CS 1000 stations have fixed button numbers, which are presented as context-sensitive soft keys, for certain features, such as the call-fwd button that is used to manage call forwarding on behalf of another user extension. Device Adapter maintains this end user experience. As a result, System Manager maintains this user experience by providing programming capabilities for these buttons.
    Therefore, in System Manager, some buttons, such as the call-fwd soft key on button number 19 for endpoints with soft keys, are reserved for configuring call-fwd for the user’s endpoint, that is, the secretary’s phone. The secretary can use this button to forward the inbound calls that are received on the secretary’s phone to another user extension. Ensure that you do not specify an extension number in the Extension field that corresponds to this call-fwd button. For more information, see Forward button for call forwarding all calls does not appear on the UNIStim or M3900 series digital desk phone.
    You can configure one or more of the remaining feature buttons as Forward buttons to enable CFW on behalf of another user extension, that is, the boss’s phone. You must specify the extension number of the boss in the Extension field that corresponds to this call-fwd button. A secretary can use this Forward button to manage CFW on behalf of the boss’s extension.
  • If you are configuring the call-fwd button for a digital or UNIStim endpoint to allow a user to call forward all calls on behalf of another extension, Avaya recommends that you do not use the CS1k-1col and CS1k-2col template types. If you use these template types and if the user does not use the optional display module that was available for purchase with these endpoints, the user cannot view the information that is being entered. Even with the display, the user might have to use paper labels to label the buttons on the endpoint to indicate the CFW destination on behalf of another extension.
  • Call forwarding on behalf of another extension feature is not supported on 2001 and 3901 endpoints.
The user who is managing call forwarding on behalf of another extension is generally an administrative support person such as a receptionist, secretary, office administrator, or any person who provides support to the other parties.
This user might want to manage Call Forward All Calls on behalf of more than one user extension. In this scenario, an administrator must configure a separate call-fwd button for each extension that the user wants to manage.
Before you begin
Before configuring a user station to allow the user station to activate CFW on behalf of another user extension, an administrator must verify the Call Forward status of the user extension for which CFW is to be activated. For more information, see Verifying the Call Forward All Calls status of an extension by using the Avaya Breeze platform CLI.
  1. Log on to System Manager by using administrative credentials.
  2. On the System Manager web console, navigate to ElementsCommunication ManagerEndpoints.
  3. Click Manage Endpoints.
  4. On the Endpoints page, select the secretary’s endpoint for which you want to configure Busy Indicator and CFW for another user extension, and then click Edit.
  5. Depending on the endpoint type, click the Feature Buttons or Button Modules pages tab.
    ADDITIONAL INFORMATION:
    Note:
    This assigns the feature to a programmable feature key and not to a reserved soft key.
  6. On the Edit Endpoint page, click the Button Assignment tab.
  7. Do the following to configure the Busy Indicator button:
    1. In the Button Label field corresponding to the button number that you want to configure as Busy Indicator, type a name for the Busy Indicator button label. For example, BI.
      ADDITIONAL INFORMATION:
      This label appears on the endpoint along with the destination number.
      The default label is BusyFwd on the secretary’s phone.
      Note:
      Avaya recommends that you use the default label. If you use a label other than the default label and if an endpoint uses a language other than English, Device Adapter cannot translate the label to the other language.
    2. In the corresponding Button Feature field, click busy-ind.
    3. In the TAC/Ext field, type the extension number of the boss.
    ADDITIONAL INFORMATION:
    Note:
    If the ProVision tool is used to configure the Busy Indicator button, you can skip this step. However, verify the button label and the status of the monitored extension.
  8. Do the following to configure a Forward button that the secretary can use to manage CFW on behalf of the boss’s phone:
    1. In the Button Label field corresponding to the button number that you want to configure as a Forward button, type a name for the Forward button.
      ADDITIONAL INFORMATION:
      The Forward button appears with this name on the secretary’s phone.
      Because the secretary might be managing CFW on behalf of two or more extensions, Avaya recommends that you provide a button name that the secretary can easily identify. For example, the name of the party on behalf of whom the secretary would be managing CFW.
    2. In the corresponding Button Feature field, click call-fwd.
    3. In the corresponding Extension field, type the extension number of the boss.
    ADDITIONAL INFORMATION:
    Note:
    This step is manual because ProVision cannot distinguish between extensions that require only monitoring and extensions that require CFW in addition to monitoring.
  9. Click Commit.