71301X Avaya Aura Communication Applications Implement Certified Exam Questions and Answers

To access the TSAPI Test from the Application Enablement Services (AES) menu, you need to select Utilities. The TSAPI Test is a basic application for making a call using TSAPI, which is a high-level API for CTI applications based on CSTA I standard. TSAPI allows access to the third party call control capabilities of CM through AES. The TSAPI Test application can be used to verify that the TSAPI client is correctly installed and working on AES. If the TSAPI Test application fails to make the call, an error message is provided to aid in troubleshooting the cause of the failure. To access the TSAPI Test from the AES menu, you need to follow these steps:

• Log in to the web interface of AES using your username and password.
• Click on Utilities on the left side menu.
• Click on TSAPI Test under Utilities.
• Enter the parameters for making a call, such as device name, destination number, user ID, and password.
• Click on Make Call.

The Avaya Session Border Controller for Enterprise (ASBCE) certificate management is a feature that allows you to install, manage, and renew certificates for the ASBCE server. Certificates are used to authenticate and encrypt the communication between the ASBCE server and other entities, such as endpoints, servers, or service providers. The following statements about the ASBCE certificate management are true:

• It allows using a default server certificate for up to one year after the installation: The ASBCE server comes with a default self-signed server certificate that can be used for testing or demonstration purposes. The default server certificate is valid for one year from the date of installation. After one year, the default server certificate expires and needs to be replaced with a valid certificate from a trusted Certificate Authority (CA).
• It supports both the Root and Intermediate Certificate Authority (CA) certificates: The ASBCE server supports installing both the Root and Intermediate CA certificates, which are used to verify the identity and trustworthiness of other certificates. A Root CA certificate is a certificate that is issued by a trusted authority and is self-signed. An Intermediate CA certificate is a certificate that is issued by a Root CA or another Intermediate CA and is used to sign other certificates. The ASBCE server can store up to 10 Root CA certificates and up to 10 Intermediate CA certificates.

In some deployments, you can enable a feature called “Stream Users Over Transport Link” in the Signaling Interface used for the Avaya Aura® Session Manager (SM) on the Avaya Session Border Controller for Enterprise (ASBCB). This feature allows reusing the same TCP connection to SM for all SIP messages related to Remote Workers registered with SM through ASBCB. A Signaling Interface is a configuration object that defines how ASBCB handles SIP signaling with other entities, such as endpoints or servers. A Signaling Interface can include parameters such as source and destination IP addresses, ports, protocols, encryption modes, authentication modes, and timers. The “Stream Users Over Transport Link” parameter is an option that can be enabled or disabled in the Advanced tab of the Signaling Interface configuration screen. When this option is enabled, ASBCB will use the same TCP connection to SM for all SIP messages related to the same Remote Worker. This can reduce the number of TCP connections and improve the performance and scalability of ASBCB and SM.

A Survivable Communication Manager (CM) is a Communication Manager instance that provides local call processing and trunking capabilities for remote sites or branches in case of a WAN outage or loss of connectivity with the core servers. A Survivable CM monitors thestatus of the main CM by sending and receiving heartbeat messages at regular intervals. A heartbeat message is a SIP OPTIONS request that tests the availability of the main CM. If the Survivable CM does not receive a response to its heartbeat message within a specified timeout period, it assumes that the main CM is down and triggers a failover process. During the failover process, the Survivable CM accepts IP phone registration requests from the local endpoints and puts the configured IP trunks in a working condition, allowing the remote site or branch to continue making and receiving calls

The Server ID is a numeric value that identifies each Communication Manager server in the network. The Server ID is used for licensing, administration, and synchronization purposes. Every CM server in the network needs to be assigned a unique Server ID, including servers in a duplex pair. A duplex pair is a configuration where two CM servers are connected by a dedicated link and act as a single logical entity, providing high availability and redundancy for call processing. The Server ID of each CM server in a duplex pair must be an even/odd pair (N, N+1), where N is an even number. For example, if one server in a duplex pair has Server ID 2, theother server must have Server ID 3. The Server ID can be configured during the installation or post-installation of Communication Manager, using the set server-id command

The statement that is true about the Application Enablement Services (AES) certificate management is that AES is shipped with a default certificate which is valid for one year, and a customer-provided server identity certificate must be installed before the default certificate expires. A server identity certificate is a file that contains information about the identity and public key of a server, such as AES. A server identity certificate is used to authenticate the server to other entities that communicate with it using HTTPS or SIP over TLS. A server identity certificate is signed by a Certificate Authority (CA), which is an entity that issues and verifies certificates. AES uses certificates for various purposes, such as securing web access, enabling HTTPS-based APIs, encrypting SIP signaling, and supporting mutual authentication with endpoints or servers. AES comes with a default self-signed certificate that can be used for testing or demonstration purposes. The default certificate is valid for one year from the date of installation. After one year, the default certificate expires and needs to be replaced with a valid customer-provided certificate from a trusted CA. To install a customer-provided certificate on AES, you need to use tools such as OpenSSL or Keytool to generate a Certificate Signing Request (CSR), submit it to a CA, obtain a signed certificate from the CA, and upload it to AES using the web interface or CLI.

When registering as a Remote Worker via the Avaya Session Border Controller for Enterprise (ASBCE), you should configure the ASBCE External (Public) Interface IP address allocated for Remote Workers in the Server List of the Avaya one-X® Communicator. The ASBCE External (Public) Interface is the interface that connects the ASBCE server to the public Internet and allows communication with external entities, such as Remote Workers or SIP service providers. The ASBCE server acts as a proxy for the Remote Workers and handles the SIP registration and call signaling with the Avaya Aura® Session Manager (SM). Therefore, you need to specify the ASBCE External (Public) Interface IP address as the SIP server address in the Avaya one-X® Communicator settings

The Avaya Workplace client is an application that provides voice, video, messaging, presence, and collaboration features for users. The Avaya Workplace client uses the XMPP protocol to communicate with the Avaya Aura® Presence Services snap-in on the Avaya Breeze® server. The Presence Services snap-in delivers the presence related messages to the Avaya Workplace client from the Avaya Breeze® Security Module (SM100) interface. The SM100 is a component of the Avaya Breeze® server that provides security and encryption functions for SIP signaling and media. The SM100 interface uses port 5222 for client-to-server XMPP connections.

The steps for deploying the Avaya Presence Services snap-in are as follows:

• Download the Presence Services snap-in software bundle from the Avaya Support website.
• Log in to System Manager and navigate to Elements > Inventory > Manage Elements.
• Select the Breeze® cluster where you want to deploy the Presence Services snap-in and click Edit.
• In the Snap-ins tab, click Add Snap-in and browse to the location where you saved the Presence Services snap-in software bundle.
• Select the Presence Services snap-in file and click Open.
• Click Commit to load the Presence Services snap-in to System Manager.
• Navigate to Elements > Inventory > Cluster Administration.
• Select the Breeze® cluster where you loaded the Presence Services snap-in and click Manage Snap-ins.
• In the Snap-ins tab, select the Presence Services snap-in and click Activate/Upgrade/Downgrade.
• Click OK to load the Presence Services snap-in into the Breeze® cluster

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 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.

When deploying Avaya Aura® Presence Services as a snap-in on a single Avaya Breeze® server, you need to create two SIP Entities for the same Avaya Breeze® server Security Module IP address or FQDN in System Manager. One SIP Entity is used for the Avaya Breeze® platform itself, and the other SIP Entity is used for the Presence Services snap-in. The type of the SIP Entity determines how Session Manager routes SIP messages to the Avaya Breeze® server. The type Avaya Breeze® indicates that the SIP Entity is a generic Avaya Breeze® server that canhost any snap-in. The type Presence Services indicates that the SIP Entity is a specific Avaya Breeze® server that hosts the Presence Services snap-in12

When installing the identity certificate and encryption key files on the Avaya Session Border Controller for Enterprise (ASBCE), you need to follow this rule: The filename of the identity certificate (.pem or .crt file) must be different from the filename of the encryption key (.key file). An identity certificate is a file that contains information about the identity and public key of an entity, such as a server or an endpoint. An encryption key is a file that contains information about the private key of an entity, which is used to encrypt and decrypt data. The identity certificate and encryption key files are obtained from a Certificate Authority (CA) or generated by yourself using tools such as OpenSSL. When installing these files on the ASBCE server, you need to make sure that they have different filenames, otherwise they will overwriteeach other and cause errors. For example, you can name them as sbce-cert.pem and sbce-key.key respectively.

When integrating the Application Enablement Services (AES) with the Avaya Aura® Communication Manager (CM), you need to configure a Switch Password in two places: on the “cti-link” screen in CM, and in “Switch Connections” on AES. TheSwitch Password is a password that is used to authenticate the communication between CM and AES. CM and AES use a protocol called Adjunct Switch Application Interface (ASAI) to exchange information and commands related to Computer Telephony Integration (CTI) applications. ASAI requires a Switch Password to establish a secure connection between CM and AES. To configure the Switch Password, you need to use these two screens:

• The “cti-link” screen in CM: This is a screen that allows you to create and manage CTI links, 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. The password is the Switch Password that will be used by CM to authenticate AES.
• The “Switch Connections” screen on AES: This is a screen that allows you to create and manage switch connections, which are logical connections between AES and switches, such as CM. You can access this screen using the web interface of AES. On this screen, you need to specify a name, IP address, port, type, and password for each switch connection. The password is the Switch Password that will be used by AES to authenticate CM.

Avaya Breeze® is a development platform that enables rapid development for applications targeted to meet a customer’s communications needs. It is used by Avaya, Partner, and third-party developers to create and deploy snap-ins, which are modular software components that provide specific functionality or features. Avaya Breeze® allows application developers to quickly add new capabilities to their Avaya solutions, such as voice, video, messaging, presence, collaboration, and analytics.

When configuring a Reverse Proxy for the Avaya Aura® Web Gateway (AAWG) in the Avaya Session Border Controller for Enterprise (ASBCE), the Server Address field is used to specify the IP address or FQDN and port of the AAWG server. The port used in this field shouldmatch the listen port on the AAWG server that is used for all WebRTC call signalling. The default listen port on the AAWG server is 8444, which is also used by default in the Server Address field of the ASBCE Reverse Proxy configuration. The Reverse Proxy allows external clients to access the AAWG server securely and transparently through the ASBCE

Avaya Aura® Presence Services uses different ports for different purposes. Port 5222 is used by endpoints like Avaya one-X® Communicators, Avaya Equinox®, or Avaya IX™ Workplace to establish client-to-server XMPP connections with the Presence Services snap-in on the Avaya Breeze® server. Port 5269 is used for server-to-server XMPP connections with the third-party XMPP servers, such as Google Talk or Jabber. These ports enable the presence and instant messaging features for the users34