Prerequisites for call forwarding

Last Updated : Sep 10, 2019 |
Prolog information
Metadata
Keywords:
The ProVision and Nortel Migration Tool provide the path to configure migrating endpoints. The migration operation discards all class-of-service codes. If there is an applicable class-of-service and configuration on the station, the migration tools create the coverage path data and assign it to the endpoint. The class-of-service is not migrated to the features.
To manually configure the service, refer to “Call Forwarding administration” in the Avaya Aura® Communication Manager Feature Description and Implementation guide.
The key aspects are:
  • Call Forward All Calls is a button or FAC related action. Ensure that the stations and FACs are defined correctly.
  • Ensure that the call-fwd button for the user extension is configured properly in System Manager.
    For more information, see Forward button for call forwarding all calls does not appear on the UNIStim or M3900 series digital desk phone.
  • For Call Forward No Answer and Call Forward Busy, ensure that a coverage path exists that matches the desired target. If it does not already exist, create a new coverage path.
  • The station must use the identified coverage path.
  • Analog stations must use the FAC model.
Note:
Communication Manager supports the Call Forward Busy/No Answer button to allow a user to enable or disable the service from the endpoint. This was not supported for the CS 1000 endpoints. To use this service, the administrator must follow the procedures in “Call Forwarding administration” in the Avaya Aura® Communication Manager Feature Description and Implementation guide. This button is not migrated and any use of the button must conform to the Communication Manager handling.