I am doing something very similar.

In our lab I will be using at test URL, but in production, it will be a different URL.

How do I change the URL later when I deploy?

Thanks,
Bill

OK here is my log after a reboot Is it connected?:
10/09/2013 08:53:42:656 DEBUG - CTIConnectorManager.ProviderMonitor: Exiting
10/09/2013 08:53:42:656 DEBUG - CTI-JTAPI Providers are shut down, CTI Connector is terminating
10/09/2013 08:56:57:853 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
10/09/2013 08:56:57:868 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
10/09/2013 08:56:57:869 DEBUG - CTIConnectorManager.init: AES Connector Version is 06.00.11.02
10/09/2013 08:56:57:869 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
10/09/2013 08:56:57:869 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
10/09/2013 08:56:57:870 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
10/09/2013 08:56:57:870 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
10/09/2013 08:56:57:878 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#S8700#CSTA#NYWSHEAESLAB02
10/09/2013 08:56:58:532 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
10/09/2013 08:56:58:532 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
10/09/2013 08:56:58:532 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 1, give small delay
10/09/2013 08:56:58:632 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
10/09/2013 08:56:58:632 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
10/09/2013 08:56:58:633 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 8
10/09/2013 08:56:58:633 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
10/09/2013 08:56:58:651 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: Unexpected requestPrivileges TSAPI failure: com.avaya.jtapi.tsapi.TsapiPlatformException: requestPrivileges failure: com.avaya.jtapi.tsapi.TsapiPlatformException: ACS Error: 120)
10/09/2013 08:56:58:651 DEBUG - CTIConnectorManager.initProvider: Will retry with a non secure connection.
10/09/2013 08:56:59:443 DEBUG - CTICallObserver.CTICallObserver:added 0675700 observer
10/09/2013 08:56:59:760 DEBUG - CTIConnectorManager.getProviderObserver: received provider in service event
10/09/2013 08:56:59:761 DEBUG - ProviderMonitor: Checking:nywsheaeslab02 for availability
10/09/2013 08:56:59:894 DEBUG - CTICallObserver.CTICallObserver:added 0675701 observer
10/09/2013 08:57:00:042 DEBUG - CTICallObserver.CTICallObserver:added 0675702 observer
10/09/2013 08:57:00:143 DEBUG - CTICallObserver.CTICallObserver:added 0675703 observer

Thanks, Here is the start of the log:
27/07/2013 14:07:45:420 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
27/07/2013 14:07:45:420 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
27/07/2013 14:07:45:421 DEBUG - CTIConnectorManager.init: AES Connector Version is 06.00.11.02
27/07/2013 14:07:45:421 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
27/07/2013 14:07:45:421 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
27/07/2013 14:07:45:422 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
27/07/2013 14:07:45:422 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
27/07/2013 14:07:45:423 DEBUG - No TServer configuration found in application config. Please configure your CTI Connector through the application configuration servlet and restart the CTI Connector
27/07/2013 14:08:41:421 DEBUG - shutting down CTI-JTAPI Providers
27/07/2013 14:08:41:422 DEBUG - CTI-JTAPI Providers are shut down, CTI Connector is terminating
27/07/2013 14:08:51:946 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
27/07/2013 14:08:51:946 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
27/07/2013 14:08:51:947 DEBUG - CTIConnectorManager.init: AES Connector Version is 06.00.11.02
27/07/2013 14:08:51:947 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
27/07/2013 14:08:51:947 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
27/07/2013 14:08:51:947 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
27/07/2013 14:08:51:947 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
27/07/2013 14:08:51:948 DEBUG - No TServer configuration found in application config. Please configure your CTI Connector through the application configuration servlet and restart the CTI Connector
27/07/2013 14:10:22:831 ERROR - No observer on extension:0675700
27/07/2013 14:53:50:107 DEBUG - shutting down CTI-JTAPI Providers
27/07/2013 14:53:50:107 DEBUG - CTI-JTAPI Providers are shut down, CTI Connector is terminating
27/07/2013 14:56:12:227 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
27/07/2013 14:56:12:227 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
27/07/2013 14:56:12:228 DEBUG - CTIConnectorManager.init: AES Connector Version is 06.00.11.02
27/07/2013 14:56:12:228 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
27/07/2013 14:56:12:228 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
27/07/2013 14:56:12:229 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
27/07/2013 14:56:12:229 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
27/07/2013 14:56:12:230 DEBUG - No TServer configuration found in application config. Please configure your CTI Connector through the application configuration servlet and restart the CTI Connector

We are ttying to use the AESConnector version:06.00.11.02. In the tracelog, we get the following error messages every 10 seconds, where nywsheaeslab02 is the name of our AES server.

09/09/2013 15:38:20:905 DEBUG - ProviderMonitor: Checking:nywsheaeslab02 for availability
09/09/2013 15:38:20:905 DEBUG - ProviderMonitor:nywsheaeslab02 is null in our list, attempt to reget
09/09/2013 15:38:20:989 DEBUG - ProviderMonitor:nywsheaeslab02 is not available

Don't know what we are missing here. Any ideas?

Here is the contents of our tsapi.pro:
debugLevel=4
trustStoreLocation=/opt/tomcat/webapps/aesconnector/WEB-INF/lib/avayaprca.jks
trustStorePassword=password
10.55.215.33=450
altTraceFile=tsapi_trace.txt

Any help would be greatly appreciated.
Bill Carson

Where can I download the TTY/TDD localization package? Is there any documentation on how to use it?

Thanks,
Bill