Hi.
" CTIConnectorManager.setTServerWait: TServer wait time is 4 ... CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0) "
It sounds as the AES/CTI connector is unable to retrieve the configurations from 'ddconfig' for some reason.
- Did you recently upgrade the OD ?
If the answer is YES, did you follow instruction on these docs
https://www.devconnectprogram.com/fileMedia/download/5dd0af54-c2cd-4ab0-9efd-62f131665917 on page 3
https://www.devconnectprogram.com/fileMedia/download/58dcf8ac-9a55-4ada-8bbe-a0e3d114527f on page 31
"After upgrading Orchestration Designer, you must update to connectors or other dependant
libraries on the application server. You must update the connector applications
icconnector.war and aesconnector.war, and run-time support files runtimeSupport platform.zip ."
Any chance to see what happens with a fresh installation of the latest OD 8.1.2 ?
- what are the current releases of the OD, the AES/CTI connector and the AES ?
- You already set "debugLevel"=7 in your 'tsapi.pro' file.
Might you try as follows
a) Take a look at the "tsapi_trace.txt" for the start up attempt. The exact error message should be visible;
b) Set debugLevel back to 0 in your "tsapi.pro" when done.
"tsapi_trace.txt" usually resides in your Tomcat root dir.
In the "tsapi.pro" file, the 'altTraceFile' needs to be configured in order to collect the tsapi tracing
associated with the client libraries such as JTAPI and CTIConnector. There isn't any default
location or name for the trace file, so you have to specify the absolute path (full path).
- Please, double-check on the "tsapi.pro" file if a valid path was configured. I see on your file
altTraceFile=tsapi_trace.txt
Is that correct ? Remember to use the forward slash in the path name for all operating systems.
Example:
altTraceFile=C:/temp/tsapi_trace.txt
For more information on JTAPI tracing reference the JTAPI programmer's guide (
https://download.avaya.com/css/public/documents/100068966)