Author Message
scanete
Joined: Jan 22, 2020
Messages: 16
Offline
Hi Everyone, we have a customer with the error showed in the subject (and other ones).
Below te complete set of messages from AES Connector trace.log, when Tomcat starts. It's running on Windows Server 2012 R2.
Please, help us to know what happens. Thanks!!!!!

24/08/2021 16:04:09:932 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:18:319 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:26:698 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:33:855 DEBUG - CTIConnectorManager.ProviderMonitor: Exiting
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79419 is 1
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent 79419: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent:79419: got Call Observation Ended Event
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79419 is null MRCR: MRCC:
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79419
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79419
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79420 is 1
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent 79420: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent:79420: got Call Observation Ended Event
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79420 is null MRCR: MRCC:
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79420
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79420
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79430 is 1
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent 79430: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent:79430: got Call Observation Ended Event
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79430 is null MRCR: MRCC:
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79430
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79430
24/08/2021 16:04:33:902 DEBUG - shutting down CTI-JTAPI Providers
24/08/2021 16:04:33:917 DEBUG - CTI-JTAPI Providers are shut down, CTI Connector is terminating
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent: got provider shutdown event:112
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent:aes1 is added to list of downed providers
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent: JTAPI Provider is down
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.init: AES Connector Version is 07.23.08.03
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
24/08/2021 16:04:44:392 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#SWLINK1#CSTA#AES1-ETH0
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 0, give small delay
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 13
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
24/08/2021 16:04:45:033 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: requestPrivileges failure: com.avaya.jtapi.tsapi.TsapiPlatformException: ACS Error: 120)
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: Will retry with a non secure connection.
24/08/2021 16:04:45:677 DEBUG - CTICallObserver.CTICallObserver:added 79419 observer
24/08/2021 16:04:45:927 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:45:927 DEBUG - CTIConnectorManager.getProviderObserver: received provider in service event
24/08/2021 16:04:47:333 DEBUG - CTICallObserver.CTICallObserver:added 79420 observer
24/08/2021 16:04:47:427 DEBUG - CTICallObserver.CTICallObserver:added 79430 observer
24/08/2021 16:04:54:599 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:05:03:200 DEBUG - ProviderMonitor: Checking:aes1 for availability
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
The requestPrivilieges API is not supported on a non-secure TLINK. Instead of AVAYA#SWLINK1#CSTA#AES1-ETH0, try specifying the AVAYA#SWLINK1#CSTA-S#AES1-ETH0 TLINK in CTIConnector.

But first, make sure the the TSAPI link on AE Services is configured as Encrypted or Both.

Martin
Go to:   
Mobile view