We recently upgraded the Avata JTAPI SDK from 6.2.0.54 to version 8.1.0.0.0.9 and upgraded our communication manager from CM 6 to CM 8.

On the earlier version we would only occasionally receive a TsapiPlatformException Could not meet post-conditions of connect(). like only 1% of the time (when we have thousands of calls being initiated via the JTAPI call.connect


However on CM 8 with version 8.1.0.0.0.9 every call to connect times out with the 15 second default timeout and TsapiPlatformException Could not meet post-conditions of connect(). When I placed a debug in TSCall connectFinish is consistently only shows a connection from the calling device. Never a connection for the called party.

log.info("TSCall.connect: about to wait for 2 connections for callID " + this.callID);
synchronized(this.connections) {
if (this.connections.size() < 2) {
this.setConnection_wait_limit(2);
if (!this.waitForConnections("connect", 2, newCall) && this.state != 34) {
device.removeFromCallsWaitingForConnectPostConditions(this);
this.provider.createDevice(destAddress).removeFromCallsWaitingForConnectPostConditions(this);
log.info("failed to get 2 connections for call ID " + this.callID);
throw new TsapiPlatformException(4, 0, "Could not meet post-conditions of connect()");
}
}

from the SDK TSCall.class above it is not getting the 2nd connection within 15 minutes.

Any thoughts, help on a resolution would be greatly appreciated.
Thanks

Gary,

This is really not something that can be worked through the forum.
Is this strictly a production problem or are you able to reproduce it in a lab setting?
Are you able to provide log files from AE Services for the operations you are invoking and the responses from AE Services (specifically TSAPI logs and JTAPI client side logs)?


If you can provide log files, please open a DevConnect Technical Support ticket for this issue "Support & Forums" -> "Technical Support"