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

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

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

An H.248 signaling link connects the Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM) by tunneling H.248 messages using TCP port 2944 and securing them using TLS. H.248 is a protocol that defines how media gateway controllers control media gateways for supporting multimedia streams across different networks, such as IP networks and PSTN networks. An H.248 signaling link is a logical connection between an H.248 controller and an H.248 gateway that allows exchanging H.248 messages for controlling media streams. In an Internet Friendly (Edge) Gateway scenario, CM acts as an H.248 controller and ASBCE DBE acts as an H.248 gateway. To connect an H.248 signaling link between CM and ASBCE DBE, these steps are performed:

CM initiates a TCP connection to ASBCE DBE using port 2944, which is reserved for H.248 over TLS.

CM and ASBCE DBE negotiate TLS parameters and exchange certificates for mutual authentication and encryption.

CM and ASBCE DBE establish a secure TLS session over TCP port 2944.

CM and ASBCE DBE exchange H.248 messages over TLS session for controlling media streams.

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.

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

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.

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

When planning the Avaya Session Border Controller for an Enterprise (ASBCE) deployment, a good practice to adopt is to name interfaces consistently, for example, Al as “Internal” or “Private” for connectivity to the Call Server. The ASBCE server has four network ports that can be configured as logical interfaces with different IP addresses, subnet masks, gateways, and VLAN IDs. The logical interfaces are named Al, A2, Bl, and B2. A good practice is to use a consistent naming convention for the interfaces that reflects their purpose and function. For example, you can name Al as “Internal” or “Private” because it connects the ASBCE server to the internal network and the Call Server. Similarly, you can name Bl as “External” or “Public” because it connects the ASBCE server to the external network and the Internet. This naming convention can help you avoid confusion and errors when configuring the interfaces and assigning them to zones.

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