extrouter Section

The extrouter section contains the configuration options that are used to support multi-site environments with the Inter Server Call Control (ISCC) feature. The configuration options in this section of the document are grouped with related options that support the same functionality, as follows:

• Event Propagation Options

• GVP Integration Option

• ISCC/COF Options

• ISCC Transaction Options

• Number Translation Option

• Transfer Connect Service Options

For a description of the ways in which T-Server supports multi-site configurations and for an explanation of the configuration possibilities for a multi-site operation, see the Multi-Site Support PDF.

Warning: In a multi-site environment, you must configure the timeout, cast-type, and default-dn options with the same value for both the primary and backup T-Servers. If you do not do this, the value specified for the backup T-Server overrides the value specified for the primary T-Server.

match-call-once

Default Value: true
Valid Values:

true	ISCC does not process (match) an inbound call that has already been processed (matched).
false	Inter Server Call Control (ISCC) processes (attempts to match) a call as many times as it arrives at an ISCC resource or multi-site-transfer target.

Changes Take Effect: Immediately

Specifies how many times ISCC processes an inbound call when it arrives at an ISCC resource. When set to false, ISCC processes (attempts to match) the call even if it has already been processed.

Warning: Genesys does not recommend changing the default value of the match-call-once option to false unless you have specific reasons. Setting this option to false may lead to excessive or inconsistent call data updates.

reconnect-tout

Default Value: 5 seconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: At the next reconnection attempt

Specifies the time interval after which a remote T-Server attempts to connect to this T-Server after an unsuccessful attempt or a lost connection. The number of attempts is unlimited. At startup, T-Server immediately attempts the first connection, without this timeout.

report-connid-changes

Default Value: false
Valid Values:

true	EventPartyChanged is generated.
false	EventPartyChanged is not generated.

Changes Take Effect: Immediately

Specifies whether the destination T-Server generates EventPartyChanged for the incoming call when the resulting ConnID attribute is different from the ConnID attribute of an instance of the same call at the origination location.

use-data-from

Default Value: current
Valid Values:

active	The values of UserData and ConnID attributes are taken from the consultation call.
original	The values of UserData and ConnID attributes are taken from the original call.
active-data-original-call	The value of the UserData attribute is taken from the consultation call and the value of ConnID attribute is taken from the original call.
current	If the value of current is specified, the following occurs: Before the transfer or conference is completed, the UserData and ConnID attributes are taken from the consultation call. After the transfer or conference is completed, EventPartyChanged is generated, and the UserData and ConnID are taken from the original call.

Changes Take Effect: Immediately

Specifies the call from which the values for the UserData and ConnID attributes are taken for a consultation call that is routed or transferred to a remote location.

Warning: For compatibility with the previous T-Server releases, you can use the values consult, main, and consult-user-data for this option. These values are aliases for active, original, and current, respectively.