72301X practice question 6 of 15

After upgrading Avaya Aura® Application Enablement Services (AES), the customer’s CTI application does not seem to be working. Which two methods can be used to verify AES system status? (Choose two.)

Full set: 95 questions
Answer options
A: Access the TSAPI web interface to monitor AES.
B: Access the AES command line, and run the status aesvcs cti-link command. Correct answer
C: Access the AES web console, and view the services status in the AES menu. Correct answer
D: Access Communication Manager (SAT), and run the statapp command to view AES services status.
E: Using Communication Manager’s System Administration Terminal (SAT), run the status aesvcs ctilink command to see the service state.
Correct Answer:
B. Access the AES command line, and run the status aesvcs cti-link command.; C. Access the AES web console, and view the services status in the AES menu.
Explanation

To verify the system status of Avaya Aura® Application Enablement Services (AES), administrators have two primary methods. The first is through the command-line interface (CLI) on the AES server itself. The command status aesvcs cti-link specifically checks the state of the crucial CTI link between AES and Communication Manager, which is essential for CTI applications. The second method is via the graphical AES Operations, Administration, and Maintenance (OAM) web console. This interface provides a comprehensive "Services Summary" page where the status of all key processes, including the CTI link, TSAPI service, and others, can be easily viewed. Both methods provide direct and authoritative status information from the AES server.

Why Incorrect

A. The term "TSAPI web interface" is incorrect. While the AES web console shows the status of the TSAPI service, it is not a dedicated TSAPI interface for monitoring.
D. The statapp command on Communication Manager (CM) shows the status of applications from CM's perspective, not the detailed internal service status of the AES server itself.
E. The command status aesvcs ctilink is executed on the AES server's command line, not within the Communication Manager System Administration Terminal (SAT).

References

1. Avaya Aura® Application Enablement Services Administration and Maintenance Guide (Release 8.1.3, November 2021)

Reference for B: Page 131, Section: "Maintenance commands", Table: "AE Services maintenance commands". The document lists status aesvcs and specifically mentions cti-link as a valid service to check. It states this command "Displays the status of the specified AE Services service."

Reference for C: Page 41, Section: "Status and Control". This section describes the OAM web interface menus, including "Services Summary," which "displays the status of the AE Services services, such as, License Server, OAM, and Tomcat web server." This is the primary GUI method for status verification.

2. Avaya Aura® Communication Manager Maintenance Commands (Release 8.1.3, November 2021)

Reference for D & E: This document details the commands available on the Communication Manager SAT. A search confirms that status aesvcs ctilink is not a valid CM command. It describes the status aesvcs link command (page 185) which checks the link from CM's perspective, but this is different from the command in option E and the broader system status check required. The status application (statapp) command is also detailed, confirming it provides a high-level connection status, not the internal AES service state.

Scroll to Top