Considerations for Transfer

Last Updated : Oct 07, 2020 |

This section provides information about how the Transfer feature behaves in certain circumstances. Use this information to ensure that you receive the maximum benefits of Transfer under all conditions. The following considerations apply to Transfer:

  • You can administer transferred trunk calls to receive either music or silence if the first part of the transfer places the call on hold.

  • Multiappearance telephones must have an idle appearance to transfer a call.

  • Single-line telephone users momentarily flash the switch hook or press the Recall button, dial the required extension, and disconnect. Multiappearance telephone users press the Transfer button, dial the required extension, and press the Transfer button again.

  • If, on the Feature-Related System Parameters screen, the Transfer Upon Hang-up field is set to y, users can transfer a call by pressing the Transfer button, dial the required extension, and then disconnect. Users can disconnect while the required extension is ringing or after the party has picked up. The user also can still press the Transfer button a second time to complete the transfer process.

  • If, on the Feature-Related System Parameters screen, the Abort Transfer field is set to y, users press the Transfer button, dial the required extension, and then disconnect or select any non-idle call appearance. The user must press the Transfer button again to complete the process (see Note). If the user selects an idle call appearance, the transfer is still active.

    Note:

    If both, the Abort Transfer and the Transfer Upon Hang-Up fields, are y and you press the Transfer button and then dial the complete transfer-to number, hanging up the telephone transfers the call.

  • Users of Digital Communications Protocol (DCP), hybrid, and wireless telephones can transfer a call that is on hold without removing the call from hold. If only one call is on hold, no active call appearances exist, and call appearance is available for the transfer, the user can transfer the call simply by pressing the Transfer button. Communication Manager assumes that the transfer is for the call on hold, and the transfer feature works as usual.

    If more than one call is on hold, the user must make a call active to transfer it. If the user presses the Transfer button with two or more calls on hold, Communication Manager ignores the transfer attempt since it will not know which call the user wants to transfer. If there are calls on hold and an active call, pressing the Transfer button will start the transfer process for the active call.

  • Communication Manager can be administered to display a confirmation message to users upon successful call transfers. The confirmation message is visible to users with DCP, Hybrid, wireless (except for 9601), or Integrated Services Digital Network-Basic Rate Interface (ISDN-BRI) display telephones. These telephones, except for the hybrids, can display the confirmation message in English, Spanish, French, Italian, or a language that you define. Hybrid telephones can display the message in English only.

  • You can administer the system to return a transferred call to the originator if the transferred-to party does not answer within a set time limit. To do this, enter a value in the Station Call Transfer Recall Timer field on the Feature-Related System Parameters screen. For any transfer if SIP Endpoint Managed Transfer feature is applied then the station recall will not start. For information on how to administer the SIP Endpoint Managed Transfer feature, see Administering Avaya Aura® Communication Manager.

The following consideration is for Outgoing Trunk to Outgoing Trunk Transfer (OTTOTT):

  • OTTOTT is not intended for use in DCS networks, since DCS Trunk Turnaround provides comparable capabilities much more safely. However, use of OTTOTT with DCS is not prohibited, and might be useful when one or more of the trunks goes off the DCS network.

The following considerations are for Trunk to Trunk Transfer:

  • Trunk-to-Trunk Transfer is particularly useful when a caller outside the system calls a user or attendant and requests a transfer to another outside number. For example, a worker, away on business, can call in and have the call transferred elsewhere.

  • Transferred trunk calls can be administered to receive either music or silence.

  • Some CO trunks do not signal the PBX when the CO user disconnects from a call. The system ensures that incoming CO trunks without Disconnect Supervision are not transferred to outgoing trunks or to other incoming CO trunks without Disconnect Supervision.

  • An attendant-assisted call connecting an outgoing trunk or incoming trunk without Disconnect Supervision to an outgoing trunk must be held on the console. The attendant cannot release the call. The attendant can, however, use the Forced Release button and disconnect all parties associated with the call.

  • If a user has connected two outgoing trunks or an outgoing call and an incoming call without Disconnect Supervision, the user must remain on the call. Otherwise, the call is dropped. An incoming trunk with Disconnect Supervision can be connected to an outgoing trunk without the user remaining on the call. An incoming trunk can also be connected to another incoming trunk without the user remaining on the call if one of the incoming trunks has Disconnect Supervision.