Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » JTAPI » Can NOT success secure connection with AES   XML
 
Author Message
Kenji



Joined: 22/01/2015 20:09:07
Messages: 78
Offline

Hi Team,

When our Customer performed the "WAS" service restart with AESConnector on VM, it can NOT success secure connection with AES after start up it.
It can be logged-in to AES. Then they are going to change timeout timer to separate cause if AESConnector has.
So, please advise are there any timeout timer related secure connection Authentication?

Here after are AESConnector_trace.log.

29/03/2021 05:07:46:691 DEBUG - ProviderMonitor:AES#2 is not available
29/03/2021 05:07:54:691 DEBUG - ProviderMonitor: Checking:AES#1 for availability
29/03/2021 05:07:57:170 DEBUG - ProviderMonitor: Checking:AES#2 for availability
29/03/2021 05:07:57:170 DEBUG - ProviderMonitor:AES#2 is null in our list, attempt to reget
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#KTAES2#CSTA-S#ACIKTAES02
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 1, give small delay
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 13
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
29/03/2021 05:08:42:541 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: setPrivileges TSAPI failure: com.avaya.jtapi.tsapi.TsapiPlatformException: setPrivileges unexpected exception: com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event)
29/03/2021 05:08:42:541 DEBUG - CTIConnectorManager.initProvider: Will retry with a non secure connection.
29/03/2021 05:08:52:753 ERROR - CTIConnectorManager.initProvider: provider:AES#2 is unavailable reason :com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event
29/03/2021 05:08:52:753 INFO - CTIConnectorManager.ConfigureFromConfigurationFile: Configure failover servers and extensions.
29/03/2021 05:08:52:753 INFO - CTIConnectorManager.ConfigureFromConfigurationFile: Configure failover server provider name - AES#1
29/03/2021 05:08:52:753 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: Provider - AES#1 - already added.
29/03/2021 05:09:00:753 DEBUG - ProviderMonitor: Checking:AES#1 for availability
29/03/2021 05:09:03:215 DEBUG - ProviderMonitor: Checking:AES#2 for availability

Best regards, K.Yamahara
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1736
Online

Third-party applications do not have access to setPrivileges so it is unlikely that anyone on this forum can help you. I suggest you contact the AE Services product house directly for help.

Martin
 
 
Go to: