Consultation Transfer

Nodes and Palette Options > Detailed Palette Option Descriptions > Consultation Transfer

	Consultation Transfer

Type

Form item

Available From

Announce Node

Blind Transfer Node, pre-populated by default

Form Node

Note:

Although the Consultation Transfer item appears on palettes for other nodes, such as the Prompt and Collect node, the Bridged Transfer node, and the Record node, it is not actually available for use in those nodes without destroying their intended functionality. It is intended primarily for use only in the Consultation Transfer Node node.

Purpose

Consultation Transfer is used for transferring a call to another destination without releasing the call from the voice platform until after the call is successfully transferred. If the connection cannot be established to the called person, then the caller is returned back to the speech application which can attempt to handle the call in other ways.

Behavior

A Consultation Transfer is similar to a Blind Transfer except that the outcome of the transfer call setup is known and the caller is not dropped as a result of an unsuccessful transfer attempt. When performing a consultation transfer, the platform monitors the progress of the transfer until the connection is established between caller and the called person.

If the connection cannot be established (For example, no answer, line busy, and so on), the session remains active and returns control to the application. As in the case of a blind transfer, if the connection is established, the interpreter disconnects from the session, connection.disconnect.transfer is thrown, and document interpretation continues normally.

If the connection to the called person is successfully established, then the call is transferred and the application platform releases the call and the speech application ends (the application may execute further to perform logging and resource cleanup and so on, but the caller is no longer connected to the application).

If successful, the application will get a connection.disconnect.transfer event and the VXML session ends; or it continues with session termination operations. If it fails, then the variable item will store the error code and the application can then evaluate the error and perform the appropriate action. See the VXML specification for return codes. Define event types using the Event Type Editor, and use the VXML event handlers to Catch (VXML Events) the event.

Exception errors can be converted into the following return codes:

noauthorization

baddestination

noroute

noresource

protocol.nnn

unsupported.transfer.consultation

unsupported.uri

Properties

Transfer Audio - - Select the prompt to use for the call transfer.

The Transfer Audio prompt must be a transitional audio prompt. This transitional audio prompt is the audio (*.wav) file that is played to callers while the call is being transferred. For more information about transitional audio prompts, see About Transitional Audio Prompts.

Connect Timeout - Maximum number of seconds to allow before the terminal connection is established.

Name - Enter the name you want to assign to the item and the corresponding variable. If you change the name of this item in the Avaya Properties view, Dialog Designer automatically changes the name of the variable as well.

Note:

This name must follow conventions for naming Java components as described in Naming Java Components.

Destination Number - Enter the telephone number to which the system will transfer callers.

Use this when you want to "hard code" the number. For example, if you want to transfer the caller at this point to an operator, you might enter 00, the number to dial for the system operator.

If you use this field, you cannot use the Destination Variable field.

Destination Variable - Select the variable that contains the number to which the system will transfer callers.

Use this when you want to allow for dynamic transfers. In dynamic transfers, for example, callers can specify the telephone number to call, and that number is stored in a variable. In other dynamic transfers, the system obtains the destination telephone number from some other source and stores it in a variable.

If the variable you select here is a complex variable, you must also select a Destination Variable Field.

If you use this field, you cannot use the Destination Number field.

Destination Variable Field - If the selected destination variable (see previous item) is a complex variable, you must select a field from the drop-down list. If the destination variable is a simple variable, this option is inactive.

AAI Data - Enter application-to-application literal data that you want to pass from this application to the receiving end of the call transfer. This option passes the raw data as you enter it in this field.

AAI Variable - Select the variable that contains the application-to-application data you want to pass to the receiving end.

If the variable you select here is a complex variable, you must also select an AAI Variable Field.

AAI Variable Field - If the selected AAI Variable is a complex variable, select the field that contains the application-to-application data you want to pass to the receiving end.

If the AAI Variable is a simple variable, this drop-down list is not populated.

Bind Name to Node - (True/False). When true, the name of the variable item is bound to the name of the node. When the parent node is renamed, the name of the variable item is renamed as well; keeping the name of the variable in sync with the node name.