Investigating and resolving AESV-SES alarms

This article will show you how to review AESV-SES alarms received from Communication Manager.


Below are some useful Communication Manager commands to use when reviewing the AESV-SES alarms

status aesvcs link
status aes cti
list cti


The Avaya AES server is a separate server that communicates with Avaya Communication Manager via a CTI link. The AES allows 3rd party adjusts to perform call recording and call control on Communication Manager but through the AES.

A link is maintained between the AES and Communication Manager in order to allow the 3rd party adjuncts to work. If this link goes down and we receive AESV-SES alarms that may mean one or more 3rd party applications are no longer working for the customer.


Alarms for the alarm type AESV-SES will be reported as AESV-SES X where X represents the number of the administered ID which is also the assigned Server ID found in the ip-services form. If there are CDR links also administered then AES server IDs will be on page 4, otherwise, they will be on page 3.


Resolving AESV-SES Alarms

These types of alarms are often caused by interruption of network connectivity and usually recover without intervention when connectivity is restored. For the occasions where the AES link does not recover after connectivity is restored, we can busy and release the corresponding cti link, and if that does not work we can disable and re-enable the AES services as shown in the video below. Please use the busy and release command at your own risk because running the command will take the CTI link out of service and potentially any 3rd party application using the application!!

Was this article helpful?
Thank you!