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

The Avaya Session Border Controller for Enterprise (ASBCE) provides an integrated (local) WebLM server that can be used to install and manage licenses for the ASBCE server. The local WebLM server is only supported in a single-server hardware-based deployment, which is a deployment where the ASBCE server runs on a dedicated hardware appliance, such as an Avaya SBCe 1U or 2U server. In this deployment, the local WebLM server runs on the same hardware appliance as the ASBCE server and can be accessed using the ASBCE web interface or CLI. The local WebLM server can store up to 10 license files and can handle up to 5000 concurrent sessions.

When configuring a Reverse Proxy for the Avaya Aura® Web Gateway (AAWG) in the Avaya Session Border Controller for Enterprise (ASBCE), the Server Address field is used to specify the IP address or FQDN and port of the AAWG server. The port used in this field shouldmatch the listen port on the AAWG server that is used for all WebRTC call signalling. The default listen port on the AAWG server is 8444, which is also used by default in the Server Address field of the ASBCE Reverse Proxy configuration. The Reverse Proxy allows external clients to access the AAWG server securely and transparently through the ASBCE

In the Avaya Session Border Controller for Enterprise (ASBCE), the state of a Network Interface, after the deployment, is Disabled. A Network Interface is a logical interface that represents a physical port on the ASBCE server. A Network Interface can be configured with an IP address, subnet mask, gateway, and VLAN ID. After the deployment of the ASBCE server, the Network Interfaces are in a Disabled state by default. To enable a Network Interface, you need to use the ASBCE web interface or CLI and configure the interface parameters. You also need to assign the interface to a Zone, which is a logical grouping of interfaces that defines the security and routing policies for the ASBCE server

The Avaya Aura® Media Server (AAMS) associated with the Avaya Aura® Web Gateway (AAWG) is used for media processing for calls to or from Avaya Spaces Calling. Avaya Spaces Calling is a softphone that provides calling features to users of Avaya Spaces by leveraging their existing Avaya infrastructure. When a user makes or receives a call using Avaya Spaces Calling, the AAWG handles the WebRTC call signaling and the AAMS handles the media. The AAMS converts the WebRTC media to SIP media and vice versa, and provides services such as announcements, music on hold, conferencing, transcoding, and recording. The AAMS processes the media for the duration of the call, regardless of whether the call is shuffled or not by Communication Manager

When configuring the Avaya Call Park and Page snap-in, the Call Park Extension Group attribute is used to specify the extensions that can be used to park calls. The format of the Call Park Extension Group attribute is as follows:

():,,…

The location ID is a numeric value that identifies the location where the Call Park and Page snap-in is deployed. The number of digits is the number of digits in each extension. The extensions are the actual extensions that can be used to park calls. For example, 3(1):4000,4001,4002 means that the Call Park and Page snap-in is deployed in location 3, each extension has one digit, and the extensions are 4000, 4001, and 40021

To allow the Avaya one-X® Communicator to subscribe to the Avaya Aura® Presence Services, you need to enter the Avaya Breeze® server Security Module IP Address or FQDN in the IM and Presence / Server field of the one-X® Communicator. The Security Module (SM100) is a component of the Avaya Breeze® server that provides security and encryption functions for SIP signaling and media. The SM100 IP address or FQDN is used by the one-X® Communicator to communicate with the Presence Services snap-in on the Avaya Breeze® server and receive presence and instant messaging features.

To access the TSAPI Test from the Application Enablement Services (AES) menu, you need to select Utilities. The TSAPI Test is a basic application for making a call using TSAPI, which is a high-level API for CTI applications based on CSTA I standard. TSAPI allows access to the third party call control capabilities of CM through AES. The TSAPI Test application can be used to verify that the TSAPI client is correctly installed and working on AES. If the TSAPI Test application fails to make the call, an error message is provided to aid in troubleshooting the cause of the failure. To access the TSAPI Test from the AES menu, you need to follow these steps:

Log in to the web interface of AES using your username and password.

Click on Utilities on the left side menu.

Click on TSAPI Test under Utilities.

Enter the parameters for making a call, such as device name, destination number, user ID, and password.

Click on Make Call.

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.

In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, you can access the tracesbc tool that displays SIP messages in real-time as they pass through the ASBCE from the SBC component/ device command line via SSH session using PuTTY. A Multi-Server/ HA deployment is a deployment where two or more ASBCE servers are deployed in a pair or cluster, providing redundancy and scalability for the ASBCE server. Each ASBCE server consists of two components: the EMS component and the SBC component. The EMS component is responsible for managing and monitoring the ASBCE server, while the SBC component is responsible for processing and routing the SIP traffic. The tracesbc tool is a CLI tool that runs on the SBC component and captures and displays SIP messages and mediastatistics for calls that traverse the ASBCE server. You can use PuTTY, which is a terminal emulator application, to establish an SSH session with the SBC component and run the tracesbc tool from the command line.

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