Hi Expert,

we receive error event 'Could not meet post-conditions of connect' when make a call via lucent.connect.

2020-02-26 17:11:02,439 [http-nio-7080-exec-5] INFO - b1 - makeCallWithUUI Address 37005 created successfully.

Terminal 37005 created successfully.

[Client.java:3136]
2020-02-26 17:11:02,440 [http-nio-7080-exec-5] INFO - b1 - makeCallWithUUI3 Address 37005 created successfully.

Terminal 37005 created successfully.

Adding a callListener to the terminal.

[Client.java:3167]
2020-02-26 17:11:17,564 [http-nio-7080-exec-5] INFO - b1 - makeCallWithUUI4 Address 37005 created successfully.

Terminal 37005 created successfully.

Adding a callListener to the terminal.

Making call from 37005 to 944133********...

[Client.java:3173]
2020-02-26 17:11:17,564 [http-nio-7080-exec-5] ERROR - b1 - makeCallWithUUI fail,Could not meet post-conditions of connect() [Client.java:3176]

MST and AES log seems normal. application didn't receive alerting event.

Can anyone advise me how to resolve this issue. should I increase callCompletionTimeout?

You can increase the value of callCompletionTimeout and it will delay JTAPI from throwing the exception. However, this may not eliminate all exceptions.

AFAIK, when JTAPI issues a makeCall request to AE Services it starts this timer to protect itself in case the request disappears into a black hole. It expects Communication Manager to respond quickly with something like a Delivered, Network Reached or Failed event. Presumably, if it receives one of these, it cancels the timer and everything continues as normal.

I presume your calls are going out to some other switch via a trunk. Depending on the type and configuration of the trunk, Communication Manager will either rely on the far-end to generate call events (e.g. Alerting or Call Proceeding etc.) or it will generate a Network reached event to indicate to JTAPI and the application that it should not expect further events about the call. The former would usually be the case for ISDN, H.323 and SIP trunks, the latter for Analog trunks.

So, it may be that Communication Manager is expecting the far-end to generate events but the far-end is not generating them. In this case, you may need to investigate why this is happening. It may be a mis-configuration or a policy decision.

Martin

Hi Martin,

Thank you for your response. It is fixed via hotfix now.


The problem mentioned in AES-20840 is a config issue. The functionality required to get expected behavior is already present. We need to enable the config parameter to get the expected results. The config change enables JTAPI module to have multiple requests to CM to get information it needs if it doesn’t get it in 1st attempt.
Below is the correct way to set the property.
System.setProperty("com.avaya.jtapi.tsapi.callConnectSendMultipleCallSnapshotRequests”, ”true”);