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.

The Survivable Communication Manager (CM) is configured on the System Manager (SMGR) as a Managed Element. A Managed Element is an entity that can be managed by SMGR, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. A Survivable 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 can be deployed on an S8300D server or on an external server such as Dell R620/R630 or HP DL360 G8/G9.  To configure a Survivable CM as a Managed Element on SMGR, you need to specify its name, type, IP address, login credentials, and security settings 5 6

Application Enablement Services (AES) communicates with Avaya Aura® Communication Manager (CM) using SIP, which is a protocol for initiating and managing multimedia sessions, such as voice, video, or instant messaging. AES is a server that provides APIs and interfaces for developing and integrating CTI applications with CM and other Avaya Aura® Platform components. AES supports various APIs and interfaces, such as TSAPI, JTAPI, DMCC, Web Services, and ASAI. AES uses SIP to communicate with CM for various purposes, such as registering endpoints, sending and receiving SIP messages, controlling calls, and capturing media. AES also uses SIP to communicate with other Avaya Aura® Platform components, such as Session Manager (SM), System Manager (SMGR), Presence Services (PS), or Breeze Platform.

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

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

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 users 3 4

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

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

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.