Free Avaya 71301X Practice Exam with Questions & Answers | Set: 2

When registering as a Remote Worker via the Avaya Session Border Controller for Enterprise (ASBCE), you should configure the ASBCE External (Public) Interface IP address allocated for Remote Workers in the Server List of the Avaya one-X® Communicator. The ASBCE External (Public) Interface is the interface that connects the ASBCE server to the public Internet and allows communication with external entities, such as Remote Workers or SIP service providers. The ASBCE server acts as a proxy for the Remote Workers and handles the SIP registration and call signaling with the Avaya Aura® Session Manager (SM). Therefore, you need to specify the ASBCE External (Public) Interface IP address as the SIP server address in the Avaya one-X® Communicator settings

The Avaya Session Border Controller for Enterprise (ASBCE) requires licenses to support different types of services, such as SIP Trunking or Remote Worker. The ASBCE licenses are based on the number of concurrent sessions that are handled by the ASBCE server. There are two types of licenses: standard services licenses and advanced services licenses. A standard services license is required for each SIP Trunking session, which is a session between the ASBCE server and a SIP service provider. An advanced services license is required for each Remote Worker session, which is a session between the ASBCE server and a remote endpoint, such as an IP phone or a softphone. Therefore, if the customer plans to have 50 SIP Trunks and100 Remote Workers supported by the ASBCE, they will need 50 standard services licenses and 100 advanced services licenses.

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

In some deployments, you can enable a feature called “Stream Users Over Transport Link” in the Signaling Interface used for the Avaya Aura® Session Manager (SM) on the Avaya Session Border Controller for Enterprise (ASBCB). This feature allows reusing the same TCP connection to SM for all SIP messages related to Remote Workers registered with SM through ASBCB. A Signaling Interface is a configuration object that defines how ASBCB handles SIP signaling with other entities, such as endpoints or servers. A Signaling Interface can include parameters such as source and destination IP addresses, ports, protocols, encryption modes, authentication modes, and timers. The “Stream Users Over Transport Link” parameter is an option that can be enabled or disabled in the Advanced tab of the Signaling Interface configuration screen. When this option is enabled, ASBCB will use the same TCP connection to SM for all SIP messages related to the same Remote Worker. This can reduce the number of TCP connections and improve the performance and scalability of ASBCB and SM.

The CLI tool that is used to trace messages in real-time as they pass through the Avaya Session Border Controller for Enterprise (ASBCE) is tracesbc. The tracesbc tool is a CLI tool that runs on the SBC component of the ASBCE server and captures and displays SIP messages and media statistics for calls that traverse the ASBCE server. You can use various filters and options to specify which calls or messages you want to trace. For example, you can filter by source or destination IP address, port, protocol, or call ID. You can also specify how long you want to run the trace and how many messages you want to display. The tracesbc tool can help you troubleshoot and diagnose issues with SIP registration and call setup.

When creating a SIP Entity for Avaya Breeze® hosting the Avaya Aura® Presence Services, you need to enter the IP address or FQDN of the Avaya Breeze® server Security Module (SM100) in the field labeled IP Address. The 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 Presence Services snap-in to communicate with other SIP entities in the network, such as Session Manager or Communication Manager

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 configuring a Topology Hiding Profile associated with a Session Manager in a typical Avaya Session Border Controller for Enterprise (ASBCE) deployment, you should overwrite the following three SIP headers with a SIP domain: From, Refer-To, and To. A Topology Hiding Profile is a configuration object that masks the FQDN or IP address portion of SIP headers to hide the internal topology of the network. For example, SBCE@avaya.com can become SBCE@135.122.18.7, or just the opposite. The From header indicates the identity of the originator of a SIP request or response. The Refer-To header indicates the identity of the recipient of a REFER request, which is used to transfer calls or sessions. The To header indicates the identity of the intended recipient of a SIP request or response. These headers should be overwritten with a SIP domain to prevent exposing internal FQDNs or IP addresses to external entities

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

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