|
Hello All,
I have a customer that is reporting hang ups on calls that should be blind transfered by AES Connector (v. 06.00.10.02). The AEP server that hosts this is on a Windows machine.
What I could see from AES Connector logs is the error:
19/02/2017 10:16:19:588 DEBUG - ProviderMonitor: Checking:AMSI_FAILOVER for availability
19/02/2017 10:16:19:588 DEBUG - ProviderMonitor:AMSI_FAILOVER is null in our list, attempt to reget
19/02/2017 10:16:19:666 DEBUG - ProviderMonitor:AMSI_FAILOVER is not available
19/02/2017 10:16:19:666 DEBUG - ProviderMonitor: Checking:AMSI_AES for availability
*** 19/02/2017 10:16:30:680 DEBUG - CTICallOperation.makeCall: Exception com.avaya.jtapi.tsapi.TsapiPlatformException: Could not meet post-conditions of connect()
*** 19/02/2017 10:16:30:680 DEBUG - error type is 4 code is 0
19/02/2017 10:16:30:680 DEBUG - CTICallOperation.makeCall 3752: Waiting on mutex
19/02/2017 10:16:34:674 DEBUG - ProviderMonitor: Checking:AMSI_FAILOVER for availability
19/02/2017 10:16:34:674 DEBUG - ProviderMonitor:AMSI_FAILOVER is null in our list, attempt to reget
19/02/2017 10:16:34:783 DEBUG - ProviderMonitor:AMSI_FAILOVER is not available
19/02/2017 10:16:34:783 DEBUG - ProviderMonitor: Checking:AMSI_AES for availability
19/02/2017 10:16:35:953 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension
From AEP perspective the call just times out (15 sec)
At Avaya´s KB I found a note about fixes at AES 6.3.3 at JTAPI session :
The Call.connect() API would sometimes fail with a
n error message "Could not
meet post-conditions of connect()", even though the
call proceeds properly.
When creating secure connections on Windows, the J
TAPI application would
sometimes hang for up to 30 seconds, then fail with
an exception.
Do you have any recomendation for next step on this? The issue does not happen with all calls, but happens with great frequency (+15%).
Best regards,
|
