We are having major troubles with AES: in 95% we don't get any response from AES, although we are far beyond load-limits (max 25.000 requests per direction in 30 minutes => below 1.000 per minute).
We are not sure, if it is CM that is not sending events to AES or if AES is not forwarding messages from CM.

However, this worked for months before.
CM 7.0.1.1, AES 7.0.1 SP2.
Any ideas? We didn't change anything that would reflect in those connection.

status aesvcs cti-link shows messages coming in and going out (each below 20.000).

kind regards,
andre

This sounds like a field site problem. If your application has been compliance tested with Devconnect, you can open a Service request with Avaya Client Services and ask them to take a look.

Martin

we have a support contract, but avaya is not able to find the root cause! :-/
they aren't even able to find the component that is causing this. Our customers are very angry, because the error exists for now exactly one week!

Now Avaya is going to force us to upgrade from CM 7.0.1.1 to 7.0.1.2 and from AES 7.0.1SP2 to 7.0.1SP4. But our current versions were running for 9 months without these problems!

After upgrading AES and CM everything is running smooth again.
I assume that it is not up to the upgrade, but due to the fact that CM was rebooted. However, no one really knows... :-/