Jump to: navigation, search

ISCC/COF Options

cof-ci-defer-create

Default Value: 0 (zero)
Valid Values: See, Timeout Value Format.
Changes Take Effect: Immediately

Specifies the time interval that T-Server waits for call data from the switch before generating a negative response for a call data request from a remote T-Server. If T-Server detects the matching call before this timeout expires, it sends the requested data. This option applies only if the cof-feature option is set to true.

cof-ci-defer-delete

Default Value: 0 (zero)
Valid Values: See, Timeout Value Format.
Changes Take Effect: Immediately

Specifies the time interval that T-Server waits before deleting call data that might be overflowed. If set to 0, deletion deferring is disabled. This option applies only if the cof-feature option is set to true.

cof-ci-req-tout

Default Value: 500 milliseconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next COF operation

Specifies the time interval during which T-Server waits for the call data requested with respect to a call originated at another site. After T-Server sends the call data request to remote T-Servers, all events related to this call will be suspended until either the requested call data is received or the specified timeout expires. This option applies only if the cof-feature option is set to true.

cof-ci-wait-all

Default Value: false
Valid Values:

true

T-Server waits for responses from all T-Servers that might have the requested call data before updating the call data with the latest information.

false

T-Server updates the call data with the information received from the first positive response.

Changes Take Effect: Immediately

Specifies whether T-Server, after sending a request for matching call data, waits for responses from other T-Servers before updating the call data (such as CallHistory, ConnID, and UserData) for a potentially overflowed call. The waiting period is specified by the cof-ci-req-tout and cof-rci-tout options. This option applies only if the cof-feature option is set to true.

cof-feature

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables or disables the Inter Server Call Control/Call Overflow (ISCC/COF) feature.

cof-rci-tout

Default Value: 10 seconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next COF operation.

Specifies the time interval that T-Server waits for call data from other T-Servers' transactions. Counting starts when cof-ci-req-tout expires. This option applies only if the cof-feature option is set to true.

default-network-call-id-matching

Default Value: No default value
Valid Values: See the T-Server-Specific Configuration Options section for an option description for your T-Server.
Changes Take Effect: Immediately

When a value for this option is specified, T-Server uses the NetworkCallID attribute for the ISCC/COF call matching. To activate this feature, the cof-feature option must be set to true.

Warning: SIP Server and several T-Servers support the NetworkCallID attribute for the ISCC/COF call matching in a way that requires setting this option to a specific value. For information about the option value that is specific for your T-Server, see the T-Server-Specific Configuration Options section of your T-Server Deployment Guide.

local-node-id

Default Value: 0 (zero)
Valid Values: 0 or any positive integer
Changes Take Effect: Immediately

This option, if enabled, checks all networked calls against the specified NetworkNodeID (the identity of the switch to which the call initially arrived). If the NetworkNodeID is the same as the value of this option, the request for call information is not sent. The default value of 0 (zero) disables the functionality of this option. To establish an appropriate NetworkNodeID, specify a value other than the default. This option applies only if the cof-feature option is set to true.

Warning: This option applies only to T-Server for Nortel Communication Server 2000/2100.

This page was last edited on March 26, 2013, at 04:04.
Comments or questions about this documentation? Contact us for support!