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
New DevConnect members must have forum permissions in order to post messages.
If the Reply and New Post buttons are not available to you, please request access using a General Support request ticket.
Forum Index » JTAPI » Could not meet post conditions   XML
Author Message

Joined: 19/09/2017 23:48:29
Messages: 21

While dialing outbound call using call.Connect() got message from AES server

"Could not meet post-conditions of connect()"

Whether we don't know either call is connected or not.

Please describe why this exception got from AES.
AES version 8.1.2

Joined: 19/09/2017 23:48:29
Messages: 21

While dialing External number(Mobile Number).

Please help on this above.

Joined: 30/11/2009 05:00:18
Messages: 1791

This is what I suspect is happening:

When the JTAPI client sends the connect request to AE Services, it starts a timer. It expects to receive some indication that the call is making progress within this time. Usually, the far-end network returns a Ringing/Alerting event almost immediately, which is sent back to the JTAPI client and it stops the timer.

Some networks do not send Ringing events, so the first event that the JTAPI Client receives is an Answered/Established event. This will not be generated until the call is answered.

If the call is not answered or the far-end user takes too long to answer, JTAPI Client will timeout and generate this error.

The length of the timer is controlled by the callCompletionTimeout parameter in your TSAPI.PRO file. You can change this to be longer.

There is more information on JTAPI properties in the JTAPI Programmers Guide.

Go to: