Avaya 71301X Exam With Confidence Using Practice Dumps

After running the Install wizard on the Avaya Session Border Controller for Enterprise (ASBCE), you add a Public (External) IP address to the Bl interface. The Bl interface is a logical interface that represents the external network port on the ASBCE server. The Bl interface is used to communicate with external entities, such as SIP service providers or remote workers. If you try to ping the Bl interface IP address from a PC in the same subnet, but it fails, the first step to resolve the problem is to navigate to Network & Flows > Network Management > Interfaces and enable the Bl interface. By default, the Bl interface is disabled after the Install wizard. You need to enable it and assign it to an External Zone, which is a logical grouping of interfaces that defines the security and routing policies for the external network

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

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