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

The Avaya Session Border Controller for Enterprise (ASBCE) provides an integrated (local) WebLM server that can be used to install and manage licenses for the ASBCE server. The local WebLM server is only supported in a single-server hardware-based deployment, which is a deployment where the ASBCE server runs on a dedicated hardware appliance, such as an Avaya SBCe 1U or 2U server. In this deployment, the local WebLM server runs on the same hardware appliance as the ASBCE server and can be accessed using the ASBCE web interface or CLI. The local WebLM server can store up to 10 license files and can handle up to 5000 concurrent sessions.

Before you can begin configuring SIP Trunking, the status that all the Avaya Session Border Controller for Enterprise (ASBCE) components / devices should show on the Device Management screen is Ready. The Device Management screen is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The Device Management screen displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Ready. The Ready status means that the component / device is fully operational and ready to handle traffic. Therefore, before configuring SIP Trunking, you should make sure that all the ASBCE components / devices have a Ready status on the Device Management screen.

The Avaya Breeze® cluster type determines the functionality and features of the Avaya Breeze® platform. There are four cluster types: General Purpose, IM_Presence, Core Platform, and Presence Services. The Core Platform cluster type is required to install the Avaya Aura® Presence Services snap-in, as it provides the basic services and components for the Avaya Breeze® platform, such as security, clustering, management, and routing. The other cluster types are either deprecated or not compatible with the Presence Services snap-in.

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

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, the other 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

After installing a new Avaya Session Border Controller for Enterprise (ASBC6) component / device using the EMS GUI, you click on the Install link on the EMS Device Management page. After briefly displaying the Provisioned status, the final status that the ASBCE component / device should display is Running. The EMS Device Management page is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The EMS Device Management page displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Running. The Running status means that the component / device is fully operational and ready to handle traffic. Therefore, after installing a new ASBCE component / device using the EMS GUI, you should wait until it displays a Running status on the EMS Device Management page.

A Server Interworking Profile is a type of a Configuration Profile in the Avaya Session Border Controller for Enterprise (ASBCE) that allows setting Timers, URI Manipulation and Header Manipulation, and can be linked to a SIP Server Profile. A Configuration Profile is a configuration object that defines how the ASBCE server handles different aspects of SIP signaling and media processing. A Server Interworking Profile is a Configuration Profile that defines how the ASBCE server interworks with different types of SIP servers, such as Communication Manager, Session Manager, or third-party servers. A Server Interworking Profile can include parameters such as Timers, which specify the timeout values for various SIP transactions; URI Manipulation, which specifies how to modify the user part or domain part of SIP URIs; and Header Manipulation, which specifies how to add, delete, or modify SIP headers. A Server Interworking Profile can be linked to a SIP Server Profile, which is another Configuration Profile that defines the identity and characteristics of a SIP server that communicates with the ASBCE server.

To associate the Avaya Call Park and Page snap-in to an Avaya Workplace Client, you need to perform the following key configuration steps:

Add a Service Profile: A Service Profile is a set of parameters that defines the features and capabilities of a user or device in System Manager. You need to create a Service Profile for the Call Park and Page snap-in, under Users > User Management > Service Profiles. In the Service Profile, you need to specify the name, type, domain, and SIP Entity of the Call Park and Page snap-in.  You also need to enable the Call Park feature and configure the Call Park activation and deactivation feature codes 1

Configure a Call Park activation and deactivation feature code: A feature code is a numeric sequence that activates or deactivates a specific feature on Communication Manager. You need to configure a Call Park activation and deactivation feature code on Communication Manager, using the change feature-access-codes command.  The Call Park activation feature code allows a user to park a call on a specified extension, while the Call Park deactivation feature code allows a user to retrieve a parked call from any extension 2

To allow communications between the Avaya Aura® Device Services (AADS) and the Avaya Aura® Web Gateway (AAWG), you need to perform the following configuration steps:

Configure the AAWG FQDN as a Trusted Host on the AADS: A Trusted Host is an entity that is allowed to communicate with the AADS server using HTTPS or REST APIs. You need to configure the Fully Qualified Domain Name (FQDN) of the AAWG server as a Trusted Host on the AADS server, using the System Manager web interface.  This allows the AAWG server to access the AADS server for device management and configuration purposes 3

Configure the AADS FQDN as a Trusted Host on the AAWG: Similarly, you need to configure the FQDN of the AADS server as a Trusted Host on the AAWG server, using the app configure command line utility.  This allows the AADS server to send dynamic configuration parameters and certificates to the AAWG server for WebRTC call signaling and media processing 4

Configure the AADS FQDN, Client interface port and Server-to-server interface port on the AAWG: You also need to configure the FQDN, Client interface port and Server-to-server interface port of the AADS server on the AAWG server, using the app configure command line utility. These parameters are used by the AAWG server to establish secure connections with the AADS server for device management and configuration purposes.  The default Client interface port is 9443, while the default Server-to-server interface port is 8443 4

The tracePS CLI tool is a command-line interface tool that allows you to capture and analyze XMPP traffic between Avaya Aura® Presence Services and other XMPP servers or clients. You can use this tool to troubleshoot issues related to presence, instant messaging, federation, or integration with third-party applications.  You can also use this tool to generate reports on XMPP traffic statistics, such as message count, message size, message type, and message direction 1

To enable downloading the Personal Profile Manager (PPM) data to an Advanced SIP Telephone (AST), you need to configure two configuration screens in the Avaya Session Border Controller for Enterprise (ASBCE): Reverse Proxy and File Transfer. PPM is a feature that allows ASTs to download configuration data from an Avaya Aura® Device Services (AADS) server or an HTTP server in the enterprise network. The configuration data includes settings such as firmware versions, network parameters, feature options, and user preferences. The ASBCE server acts as a proxy for the ASTs and enables secure access to the internal servers that host the configuration data. To configure this feature in the ASBCE server, you need to use these two configuration screens:

Reverse Proxy: This is a configuration object that enables secure access to internal web servers from external clients. The Reverse Proxy intercepts HTTP or HTTPS requests from external clients and forwards them to the appropriate internal web servers, such as an AADS server or an HTTP server. The Reverse Proxy also returns the responses from the internal web servers to the external clients. You need to configure a Reverse Proxy that maps the external URL of the PPM data to the internal URL of the PPM data on the AADS server or HTTP server.

File Transfer: This is a configuration object that enables secure file transfer between external clients and internal servers using protocols such as FTP or SCP. The File Transfer intercepts file transfer requests from external clients and forwards them to the appropriate internal servers, such as an AADS server or an HTTP server. The File Transfer also returns the files from the internal servers to the external clients. You need to configure a File Transfer that specifies parameters such as source and destination IP addresses, ports, protocols, usernames, passwords, encryption modes, and file paths for transferring PPM data files between ASTs and AADS servers or HTTP servers.

The Avaya Aura® Web Gateway (AAWG) requires a license file to operate and provide WebRTC services for endpoints such as Avaya Workplace clients or Avaya Spaces Calling extension users. The license file can be installed on either of these two options:

The WebLM server embedded in System Manager (SMGR): This is a web-based licensing application that is integrated with SMGR and can manage licenses for multiple Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform.  You can install an AAWG license file on this WebLM server using SMGR web interface, under Elements > Licensing > Licenses 5

A standalone WebLM server: This is a web-based licensing application that runs on a separate Linux or Windows server and can manage licenses for multiple Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform.  You can install an AAWG license file on this WebLM server using its web interface, under Licenses > Add License File 6

To allow the Avaya one-X® Communicator to subscribe to the Avaya Aura® Presence Services, you need to enter the Avaya Breeze® server Security Module IP Address or FQDN in the IM and Presence / Server field of the one-X® Communicator. The Security Module (SM100) is a component of the Avaya Breeze® server that provides security and encryption functions for SIP signaling and media. The SM100 IP address or FQDN is used by the one-X® Communicator to communicate with the Presence Services snap-in on the Avaya Breeze® server and receive presence and instant messaging features.

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.

 tracePS is a CLI tool that allows you to capture and analyze XMPP traffic between Avaya Aura® Presence Services and other XMPP servers or clients. You can use this tool to troubleshoot issues related to presence, instant messaging, federation, or integration with third-party applications.  You can also use this tool to generate reports on XMPP traffic statistics, such as message count, message size, message type, and message direction

To connect one Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM), you need two Public and two Private IP addresses. An Internet Friendly (Edge) Gateway is a device that provides secure and reliable connectivity between endpoints on different networks, such as the public internet and a private enterprise network. An Internet Friendly (Edge) Gateway can be implemented using an Avaya Session Border Controller for Enterprise (ASBCE) in distributed mode, where the ASBCE consists of two components: a Signaling Border Element (SBE) and a Data Border Element (DBE). The SBE handles SIP signaling and call control, while the DBE handles media packets and signaling pinholes. To connect one Internet Friendly (Edge) Gateway to CM, you need these IP addresses:

A Public IP address for the SBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the SBE using SIP over TLS.

A Private IP address for the SBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the SBE using SIP over TCP or UDP.

A Public IP address for the DBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the DBE using RTP or RTCP.

A Private IP address for the DBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the DBE using H.248.

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.