71301X Dumps with Practice Exam Questions Answers

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.

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.

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

To connect one Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM), you need two Public and two Private IP addresses. An Internet Friendly (Edge) Gateway is a device that provides secure and reliable connectivity between endpoints on different networks, such as the public internet and a private enterprise network. An Internet Friendly (Edge) Gateway can be implemented using an Avaya Session Border Controller for Enterprise (ASBCE) in distributed mode, where the ASBCE consists of two components: a Signaling Border Element (SBE) and a Data Border Element (DBE). The SBE handles SIP signaling and call control, while the DBE handles media packets and signaling pinholes. To connect one Internet Friendly (Edge) Gateway to CM, you need these IP addresses:

• A Public IP address for the SBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the SBE using SIP over TLS.
• A Private IP address for the SBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the SBE using SIP over TCP or UDP.
• A Public IP address for the DBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the DBE using RTP or RTCP.
• A Private IP address for the DBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the DBE using H.248.