Avaya 71301X - Avaya Aura Communication Applications Implement Certified Exam

To connect to the Application Enablement Services (AES) web interface, you need to use the correct URL and the default login ID. The AES web interface is a web-based application that allows you to configure and manage the AES server and its features. You can access the AES web interface using any web browser that supports HTTPS. The URL for connecting to the AES web interface is https:// :8443, where is the IP address of the AES server that you want to connect to. The port number 8443 is the default port for HTTPS communication with the AES server. After entering the URL in the web browser, you will see a login screen where you need to enter the login ID and password for accessing the AES web interface. The default login ID for the AES web interface is craft, which is a system administrator account that has full access to all features and functions of the AES server. 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 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 formultiple 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 > Licenses5

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 File6

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

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.

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.

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

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.

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

To allow downloading the 46xxsettings.txt file to a Remote Worker device, you need to configure a Reverse Proxy under DMZ Services in the Avaya Session Border Controller for Enterprise (ASBCE). A Reverse Proxy 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 HTTP server or an Avaya Aura® Device Services (AADS) server. The Reverse Proxy also returns the responses from the internal web servers to the external clients. The 46xxsettings.txt file is a configuration file that contains settings for Avaya IP Deskphones, such as firmware versions, network parameters, and feature options. The 46xxsettings.txt file is usually hosted on an HTTP server or an AADS server in the enterprise network. To allow Remote Worker devices to download this file securely, you need to configure a Reverse Proxy that maps the external URL of the file to the internal URL of the file on the HTTP server or AADS server