Pass the Avaya ACIS-7130 71301X Questions and answers with ValidTests

Avaya Session Border Controller for Enterprise (ASBCE) can be deployed on the Kernel-based Virtual Machine (KVM) infrastructure. KVM is a virtualization technology that allows multiple operating systems to run on a single physical machine. To deploy ASBCE on KVM, you need to use a template file that contains the ASBCE software image and configuration parameters. The template file type to be used for KVM deployment is QCOW2, which stands for QEMU Copy-On-Write version 2. QCOW2 is a file format for disk images that can be used by QEMU, which is an open source emulator and virtualizer that can run KVM virtual machines. QCOW2 files support features such as compression, encryption, snapshots, and backing files

If the customer requires High Availability (HA) for the Avaya Session Border Controller for Enterprise (ASBCE), the minimum number of servers or virtual machines that are required is 2. High Availability (HA) is a feature that provides redundancy and fault tolerance for the ASBCE server by deploying two ASBCE servers in a pair, either in the same location or geographically dispersed. The two ASBCE servers act as a single logical entity and share a common configuration and license. One ASBCE server is designated as the active server and handles all traffic, while the other ASBCE server is designated as the standby server and monitors the status of the active server. If the active server fails or becomes unreachable, the standby server takes over and becomes the new active server, ensuring continuity ofservice. The two ASBCE servers synchronize their configuration and state information using a dedicated HA link between them

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.

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

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

An Avaya Workplace client learns about a Survivability Server assigned in its User Profile from the Avaya Aura® Device Services (AADS) via the Dynamic Configuration. TheDynamic Configuration is a set of parameters that are sent by the AADS to the Avaya Workplace client during login or registration. The Dynamic Configuration contains information such as the SIP domain, SIP proxy, SIP registrar, and Survivability Server for the Avaya Workplace client. The Survivability Server is an Avaya Aura® Communication Manager instance that provides call processing and voice mail access for the Avaya Workplace client in case of a network failure or loss of connectivity with the core servers34

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

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

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 settings56