Which method can be used to verify the Client and TSAPI services have been administered correctly?

The Avaya Aura® Application Enablement Services (AES) management console provides a specific diagnostic tool for this purpose. The AE Services TSAPI Test, located under the Utilities > Diagnostics menu, is designed to verify the correct administration of the TSAPI service and its communication link with Communication Manager. This utility works by initiating a test call between two specified stations to confirm that the CTI link, TSAPI service, and associated configurations are functioning correctly. This is the officially sanctioned method for directly testing the service's administration from the AES server.

A. Initiating a call from a CTI endpoint is a functional test of the entire solution, not the specific diagnostic tool for administration verification.

B. The TSAPI test is initiated from the Application Enablement Services (AES) server's management interface, not from the Communication Manager (CM) command line.

C. The menu path is incorrect. The TSAPI test utility is located under the Utilities > Diagnostics menu, not a separate "TSAPI web interface."

1. Avaya Aura® Application Enablement Services Administration and Maintenance Guide (Release 8.1.3), Document Number NN43001-613, December 2021.

Page 229, Section: "AE Services TSAPI Test": This section explicitly details the diagnostic tool. It states, "The AE Services TSAPI Test utility allows you to verify that the TSAPI Service is configured correctly and is communicating properly with Communication Manager." It also confirms the navigation path: "From the AE Services management console main menu, select Utilities > Diagnostics > AE Services TSAPI Test."

2. Avaya Aura® Application Enablement Services Overview and Specification (Release 7.1), Document Number NN43001-109, November 2016.

Page 41, Section: "Diagnostics": This document mentions the built-in diagnostic tools available through the AE Services management interface, including the TSAPI Test. It describes its function as a tool to "verify that the TSAPI link is up and that basic call control is working."