Avaya Aura Communication Applications Implement Certified

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.

After deploying Avaya Aura Web Gateway (AAWG) in a Virtualized Environment (VE), the next step is to enroll AAWG with System Manager (SMGR) by running the initTM command on the AAWG CLI. The initTM command is used to initialize the trust management between the AAWG server and the SMGR server. This command requires an enrollment password that is configured in the SMGR web interface, under Security > Enrollment Password. The enrollment password has a validity period that can be set by
the administrator. If the enrollment password has expired, the initTM command will fail. Therefore, before running the initTM command, you should verify that the enrollment password is configured and valid

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

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.

Avaya Aura Presence Services does not require a separate license file or an instance license. User licenses are an entitlement as part of the Avaya Aura suite licensing, such as Foundation, Mobility, Team Engagement, or Customer Engagement. The user licenses are consumed based on the number of users who are provisioned for Presence Services in System Manager

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.

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://<AES
Management IP Address>:8443, where <AES Management IP Address> 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.

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.

Before obtaining a server identity certificate from a Certificate Authority (CA) for the installation on the Avaya Session Border Controller for Enterprise (ASBCE), you need to generate a Certificate Signing Request (CSR). A CSR is a file that contains information about the identity and public key of the ASBCE server, as well as a digital signature that proves the ownership of the public key. A CSR is used to request a server identity certificate from a CA, which is an entity that issues and verifies certificates. The CA will check the information in the CSR and issue a server identity certificate that contains the same information and public key, as well as the CA's signature and validity period. The server identity certificate is used to authenticate the ASBCE server to other entities that communicate with it using HTTPS or SIP over TLS. To generate a CSR for the ASBCE server, you can use tools such as OpenSSL or Keytool, or use the ASBCE web interface or CLI.

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