Interactions for Transfer

Last Updated : Oct 30, 2012 |

This section provides information about how the Transfer feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of Transfer in any feature configuration.

Analog Station Recall Operation and Feature Activation

When called parties initiate either analog-telephone recall or feature activation, callers are not put on hold for transfer. Instead, callers are transferred by way of Pull Transfer.

Basic Rate Interface (BRI) telephones

Callers who use BRI Stations reach required parties through the intermediate step of calling a party who calls a final destination. Intermediate parties activate pull transfer to complete transfers. Final called parties go off hook as if a new transfer were originated.

Call Detail Recording (CDR)

The software checks to ensure that calls are correctly recorded with CDR when Pull Transfer is completed.

Digital Station Transfer Operation

When called parties initiate transfer operations, callers are not put on hold for transfer; they are transferred by way of Pull Transfer.

Non-BRI telephones

Callers who use the non-BRI telephones reach required parties through an intermediate step of calling a party who calls a final destination. Each called party activates pull transfer.

DCS Trunk Turnaround

The following interactions are for Outgoing Trunk to Outgoing Trunk Transfer (OTTOTT):

OTTOTT increases the set of cases in which DCS Trunk Turnaround can be accepted. However, use of OTTOTT in combination with a DCS network is strongly discouraged. The following algorithm describes the DCS Trunk Turnaround request process.

  • If any party on the call receives a local-dial, busy, intercept, or reorder tone, deny turnaround. If any remaining party is an answered station or attendant, accept turnaround.

  • If any remaining party is on an incoming trunk, accept turnaround. For the purposes of this check, an outgoing DCS trunk that has been turned around an odd number of times by way of a DCS trunk turnaround is considered an incoming trunk with disconnect supervision. Similarly, an incoming DCS trunk that has been turned around an odd number of times is considered an outgoing trunk.

  • If any remaining party is an outgoing trunk administered for OTTOTT that has received answer supervision, accept turnaround.

  • If any remaining party is an outgoing DCS trunk, forward the turnaround request.

  • If any remaining party is not a DCS trunk, deny turnaround.

Incoming Disconnect Supervision

Outside of the US, incoming disconnect supervision is a switching capability that restricts transfers or conferences for certain incoming trunks. In the U.S., all incoming trunks are assumed to provide disconnect supervision. In some countries, this assumption is invalid. Therefore, you must administer whether or not an incoming trunk provides disconnect supervision for each trunk group.

Personal Central Office Lines (PCOLs)

Transfer of PCOLs is not subject to the normal restrictions that are applied to transfer of other trunks. These transfers are allowed since the PCOL appearance remains on one or more stations as a feature button. System users must be aware that the DROP button cannot be used to disconnect the transferred-to party from the call. Therefore, if an outgoing PCOL is transferred to an outgoing trunk and neither of the trunks can supply a disconnect signal, the two trunks lock up.

Pull Transfer

If station A is talking to station B and station B begins a transfer to station C, only station C can use the Pull Transfer feature to grab the call. Furthermore, if station B uses the Toggle Swap feature to return to station A and station C is now in a soft hold state, station C cannot use the Pull Transfer feature until station B toggles back and has station C in the talk state.

QSIG Global Networking

If either call is over an ISDN-PRI trunk that is administered with Supplementary Service Protocol b (QSIG), the system might display additional call information.

Release-Link Trunks (RLT)

RLTs are used by CAS. An outgoing RLT at a remote branch is used to access an attendant at the main. The attendant at the main can transfer the incoming caller to a station or a trunk at the branch. The RLT is typically used only for a short period of time and is usually idled after the transfer is established.

A station at a branch can transfer an outgoing trunk to the attendant at the main. This transfer could be viewed as an OTTOTT (the attendant is accessed by way of an outgoing RLT). Since administering outgoing disconnect supervision for RLT trunks provides no additional capability, this administration is not provided for RLT trunks.

Restriction

Restrictions on the transferring party can block a transfer or a drop operation even when Outgoing Disconnect Supervision is provided.

Trunk-to-Trunk Transfer

If this feature-related system parameter is set to Restricted, all trunk-to-trunk transfer or release, or drop operations for public trunks (CO, CPE, CAS, DID, DIOD, FX, and WATS) have calls terminated or receive denial. If the parameter is set to None, all trunk-to-trunk transfers (except CAS and DCS) have calls terminated or receive denial.

Hence, you use All to enable OTTOTT operation for these types of trunks. The number of public network trunks allowed on a conference call is administrable. This number defaults to 1, so if OTTOTT is being used to connect two or more public network trunks, you must increase this limit on the Feature-Related System Parameters screen.

Trunks (CO, FX, and WATS)

You cannot have two CO, FX, or WATS trunks in a OTTOTT connection, even if the Disconnect Supervision - Out field is set to y.

Attendant Lockout

The following interactions are for Trunk to Trunk Transfer:

Attendant Lockout does not function on Trunk-to-Trunk Transfer.

Call Vectoring

Station control of Trunk-to-Trunk Transfer does not affect routing of incoming trunks to a vector directory number (VDN) that ultimately routes to a destination off-net.

A route to a number off-switch does not require you to enable trunk-to-trunk transfer.

Tenant Partitioning

Station control of Trunk-to-Trunk Transfer is prohibited between trunks in different tenant partitions if those partitions are restricted.

Night Service

The following interaction is for Emergency Transfer:

If a power failure occurs when the system is in night service, the system automatically returns to night service when power is restored.