Jump to: navigation, search

ISCC Transaction Options

cast-type

Default Values:

  • direct-ani
  • direct-callid
  • direct-digits
  • direct-network-callid
  • direct-notoken
  • direct-uui
  • dnis-pool
  • pullback
  • reroute
  • route
  • route-uui

Valid Values:

  • direct-ani
  • direct-callid
  • direct-digits
  • direct-network-callid
  • direct-notoken
  • direct-uui
  • dnis-pool
  • pullback
  • reroute
  • route
  • route-uui

Changes Take Effect: For the next request for the remote service

Specifies—using a space-, comma- or semicolon-separated list—the routing types that can be performed for this T-Server.

The valid values provide for a range of mechanisms that the ISCC feature can support with various T-Servers, in order to pass call data along with calls between locations.

Because switches of different type provide calls with different sets of information parameters, some values might not work with your T-Server. The Multi-Site Support section also provides detailed descriptions of all transaction types.

Warning: For compatibility with the previous T-Server releases, you can use the direct value for this option. This is an alias for direct-callid. Warning: An alias, route-notoken, has been added to the route value.

default-dn

Default Value: No default value
Valid Values: Any DN
Changes Take Effect: For the next request for the remote service.

Specifies the DN to which a call is routed when a Destination DN (AttributeOtherDN) is not specified in the client's request for routing. If neither this option, nor the client's request, contains the destination DN, the client receives a EventError message.

Warning: This option is used only for requests with route types route, route-uui, direct-callid, direct-network-callid, direct-uui, direct-notoken, direct-digits, and direct-ani.

direct-digits-key

Default Value: CDT_Track_Num
Valid Values: Any valid key name of a key-value pair from the UserData attribute.
Changes Take Effect: For the next request for the remote service.

Specifies the name of a key from the UserData attribute that contains a string of digits that are used as matching criteria for remote service requests with the direct-digits routing type.

Warning: For compatibility with the previous T-Server releases, this configuration option has an alias value of cdt-udata-key.

dn-for-unexpected-calls

Default Value: No default value
Valid Values: Any DN
Changes Take Effect: Immediately

Specifies a default DN for unexpected calls arriving on an External Routing Point.

network-request-timeout

Default Value: 20 sec
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next network request.

For a premise T-Server, this option specifies the time interval that the premise T-Server waits for a response, after relaying a TNetwork<...> request to the Network T-Server. For a Network T-Server, this option specifies the time interval that the Network T-Server waits for a response from an SCP (Service Control Point), after initiating the processing of the request by the SCP.

When the allowed time expires, the T-Server cancels further processing of the request and generates a EventError message.

register-attempts

Default Value: 5
Valid Values: Any positive integer
Changes Take Effect: For the next registration

Specifies the number of attempts that T-Server makes to register a dedicated External Routing Point.

register-tout

Default Value: 2 seconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next registration.

Specifies the time interval after which T-Server attempts to register a dedicated External Routing Point. Counting starts when the attempt to register a Routing Point fails.


request-tout

Default Value: 20 seconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next request for remote service.

Specifies the time interval that a T-Server at the origination location waits for a notification of routing service availability from the destination location. Counting starts when the T-Server sends a request for remote service to the destination site.

resource-allocation-mode

Default Value: circular
Valid Values:

home

T-Server takes an alphabetized (or numerically sequential) list of configured DNs and reserves the first available DN from the top of the list for each new request. For example, if the first DN is not available, the second DN is allocated for a new request. If the first DN is freed by the time the next request comes, the first DN is allocated for this next request.

circular

T-Server takes the same list of configured DNs, but reserves a subsequent DN for each subsequent request. For example, when the first request comes, T-Server allocates the first DN; when the second request comes, T-Server allocates the second DN; and so on. T-Server does not reuse the first DN until reaching the end of the DN list.

Changes Take Effect: Immediately

Specifies the manner in which T-Server allocates resources (that is, DNs of the External Routing Point type and Access Resources with the Resource Type set to dnis) for multi-site transaction requests.

resource-load-maximum

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

Specifies the maximum number of ISCC routing transactions that can be concurrently processed at a single DN of the External Routing Point route type. After a number of outstanding transactions at a particular DN of the External Routing Point type reaches the specified number, T-Server considers the DN not available. Any subsequent request for this DN is queued until the number of outstanding transactions decreases. A value of 0 (zero) means that no limitation is set to the number of concurrent transactions at a single External Routing Point. In addition, the 0 value enables T-Server to perform load balancing of all incoming requests among all available External Routing Points, in order to minimize the load on each DN.

route-dn

Default Value: No default value
Valid Values: Any DN
Changes Take Effect: Immediately

Specifies the DN that serves as a Routing Point for the route transaction type in the multiple-to-one access mode.

timeout

Default Value: 60 seconds
Valid Values: See, Timeout Value Format.
Changes Take Effect: For the next request for remote service.

Specifies the time interval that the destination T-Server waits for a call routed from the origination location. Counting starts when this T-Server notifies the requesting T-Server about routing service availability. The timeout must be long enough to account for possible network delays in call arrival.

use-implicit-access-numbers

Default Value: false
Valid Values: true, false
Changes Take Effect: After T-Server is restarted

Determines whether an External Routing Point in which at least one access number is specified is eligible for use as a resource for calls coming from switches for which an access number is not specified in the External Routing Point. If this option is set to false, the External Routing Point is not eligible for use as a resource for calls coming from such switches. If this option is set to true, an implicit access number for the External Routing Point, composed of the switch access code and the DN number of the External Routing Point, is used.

Warning: If an External Routing Point does not have an access number specified, this option will not affect its use.

This page was last edited on March 26, 2013, at 04:05.
blog comments powered by Disqus