PreviousNextIndex

Configuring CTI Settings

If the Dialog Designer application uses the Compute Telephony Integration (CTI) connector, the application server must be configured to communicate with the TServer/AES. Configure these settings as described in the table below.

Once a server has been added, the entry is added to the CTI server table, and links are added to configure channel extension mappings or to add a failover server. When clicking map, a new page is displayed to configure TServer extension mappings.

Channels can be mapped one at a time, or a sequence of channels can be mapped using a "1-n" reference. For Interactive Response, channels must map to IR setup. For Voice Portal, channel mappings are arbitrary. (For this release, ignore Observe On Setup option.)

Note:

You will need to restart the CTI Connector for changes to take affect. You will also need to modify tsapi.pro that is included with your runtime support files before connecting to a TServer/AES.     Copy or move the tsapi.pro file from bea\user_projects\domains\ domainname\ lib to WeblogicHome\common\lib. You can then edit tsapi.pro file in this directory as well.

Tip:

A delay could be incurred when the CTI connectors are attempting to establish connections to TServers, which can slow down the Tomcat launch as well. When connectors are not installed, initialization is quicker. If this is problematic, it may help to use "localhost" in the tsapi.pro file instead.

See About CTI Connectors.

Attributes

Description

General Settings

Timeout

Time in ms to wait for a VOX response. Default is 4000.

Trace Verbosity

Amount of debug output. Possible values are:

  • 0-off
  • 3 full

CTI Settings

Name

A unique server name to identify the TServer. Once added, the table list provides a link to configure channel-extension mapping, as well as a failover server (in the event that the primary server goes down).

Channel-extension mapping is the same as the primary for the failover server, so these configurations are not required also for the failover server.

Note: Server name must be unique and the TServer/AES and failover names cannot contain '*'. TServer/AES names cannot be duplicated (even Failover name cannot be the same as TServer/AES).

Service Name

Identifies the service provider in the following format:

vendor#switch#type#server

For example:

AVAYA#S8300DD#CSTA#MLDDAES

Note:

If AES TLINK is set to encrypted, which is supported by AES 4.2 or above, the type needs to be CSTA-S.

For example:

AVAYA#S8300DD#CSTA-S#MLDDAES.

User Name

Username to connect to this tserver/AES.

Password

Unencrypted password to connect to this tserver/AES.

Confirm Password

Confirm password must match password.


To achieve secured connection to AES, you need to set two additional properties in the tsapi.pro file:

Attributes

Value

trustStoreLocation

C:/Program Files/Apache Software Foundation/Tomcat 5.5/webapps/cticonnector/WEB-INF/lib/avayaprca.jks

trustStorePassword

password


The Service Name varies depending on the customer. The trustStoreLocation value may be different depending on the location of avayaprca.jks file on your computer. However, the trustStorePassword value must be password.

PreviousNextIndex

©2009, Avaya Inc. All rights reserved.