Download Latest 71301X Questions

To connect to the Application Enablement Services (AES) command-line interface (CLI), you need to use a secure shell (SSH) client, such as PuTTY, and thedefault login ID. The AES CLI is a text-based interface that allows you to configure and manage the AES server and its features. You can access the AES CLI using any SSH client that supports SSH version 2. The procedure for connecting to the AES CLI is as follows:

• Launch the SSH client on your administrative workstation.
• Enter the IP address of the AES server that you want to connect to, and specify port 22 for SSH communication.
• Click Connect or Open to initiate the connection.
• The server displays a security alert window the first time you connect. If you see this window, click Yes or Accept to accept the server’s host key.
• The system displays a login prompt. Enter the login ID for accessing the AES CLI. The default login ID for the AES CLI is craft, which is a system administrator account that has full access to all features and functions of the AES server.
• The system displays a password prompt. Enter the password for the craft account. The default password for the craft account is craft. You can change the password or create other user accounts with different access levels using the Security Database feature of the AES web interface.

To integrate Avaya Aura® Communication Manager (CM) with Application Enablement Services (AES), and enable the TSAPI link, you need to perform two configuration steps on CM: Configure IP Services and Create a CTI link. These steps are necessary to establish a connection between CM and AES using ASAI protocol, which is a proprietary protocol that provides access to various CTI features of CM. A TSAPI link is a logical connection between CM and AES that allows TSAPI applications to use ASAI features through AES. To configure IP Services and Create a CTI link on CM, you need to use these screens:

• The “ip-services” screen: This is a screen that allows you to create and manage IP services on CM, such as ASAI-IP or C-LAN. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a service type, node name, local node, local port, remote node, remote port, remote domain name, service state, and service link for each IP service. For integrating with AES, you need to create an ASAI-IP service that points to the node name of an AES server.
• The “cti-link” screen: This is a screen that allows you to create and manage CTI links on CM, which are logical connections between CM and CTI servers, such as AES. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a name, number, type, and password for each CTI link. For integrating with AES, you need to create a CTI link of type ADJ-IP that matches the switch CTI link number on AES.

In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, you can access the tracesbc tool that displays SIP messages in real-time as they pass through the ASBCE from the SBC component/ device command line via SSH session using PuTTY. A Multi-Server/ HA deployment is a deployment where two or more ASBCE servers are deployed in a pair or cluster, providing redundancy and scalability for the ASBCE server. Each ASBCE server consists of two components: the EMS component and the SBC component. The EMS component is responsible for managing and monitoring the ASBCE server, while the SBC component is responsible for processing and routing the SIP traffic. The tracesbc tool is a CLI tool that runs on the SBC component and captures and displays SIP messages and mediastatistics for calls that traverse the ASBCE server. You can use PuTTY, which is a terminal emulator application, to establish an SSH session with the SBC component and run the tracesbc tool from the command line.

To enable IM and Presence for an Avaya Aura® user, you need to edit the Communication Profile of the user in System Manager, under Users > User Management > Manage Users. In the Communication Profile tab, you need to assign an Avaya Presence/IM handle to the user, which is a unique identifier that follows the format username@domain.com. You also need to enable and configure the Presence profile for the user, which specifies the Presence Services snap-in that will provide presence and instant messaging features for the user.