Can't find any information on the tsapi.pro file.

I know it needs editing but neither the DD 5.1 or VP 5.1 manual sets really have anything on it.

Are you needing to setup a secure connection? In the DD Programmers Guide in the "Configuration CTI Settings" there is some discussion on how to do that in the tsapi.pro file.

The only other setting is the IP of the AES. There is a sample entry already in place in your tsapi.pro file, just modify that. If you are only doing a non secure configuration, then you only need to modify the IP and don't need to worry about the trust store.

Searching for tsapi.pro and cticonnector did not find the manual page you referenced.

The page could use some editing.

This is the text I was referring to about a secure connection:

Add the following text to the tsapi.pro file on all of your Application Servers that run cti enabled DD apps:
trustStoreLocation=C:/Program Files/Apache Software Foundation/
Tomcat 5.5/webapps/cticonnector/WEB-INF/lib/avayaprca.jks
trustStorePassword=password

Note: 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.

The below is taken from the CTI runtimeconfig screen.

Can you provide a more comprehensive description of how to determine the service name field value?



Name: A unique name to identify this entry.
The tserver and failover names cannot contain '*'.
Service Name: Identifies the service provider in the format: vendor#switch#type#server.
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.



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 runtimesupport files before connecting to a TServer/AES. Please read Dialog Designer documentation for correct location to place this file.

It's going to depend on your switch and configuration

Below is an example from the DD Dev Guide. The first field is your vendor which in our case is Avaya, then switch id. Type would typically be CSTA or CSTA-S (for secure). Finally, the server is the hostname of your AES. This same hostname is the IP you mapped in your tsapi.pro file.

Service Name Identifies the service provider in the following format:
vendor#switch#type#server
For example:
AVAYA#S8300DD#CSTA#MLDDaes

in the initial tsapi.pro file there is an entry:

xxx.xxx.xxx.xxx=450

I've set the xxx.xxx.xxx.xxx to the IP of the AES. So as an example I now have:

9.22.93.123=450

Question: What does the 450 represent, and do I need to
modify that value?

I've also entered a previous post asking for any documentation that provides more details on the runtimeconfig application (other than the Dev Guide)

Is there by chance any tutorial docs avaialbe ?

I have another question:

The tsapi.pro file has an entry:

alttTaceFile=tsapi_trace.txt
debugLevel=3

Would these setting control the logging of the CTI connector application I've installed on my app server? I only see 4 lines of init banner lines and nothing else. Is there other logs that the CTI connector applcaiton would be writing to?

450 is the port. Leave it as is.

tsapi.pro is a file used by the JTAPI driver. The debug level only affects that driver and has no affect on the CTIC. Set debug level = 0 for most operations. If you need JTAPI logging, set it to 7, but it is a huge file and will eat up alot of space, so only use it when you need it.