Avaya Updated 71301X Exam Questions and Answers by indigo

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.

When integrating the Application Enablement Services (AES) with the Avaya Aura® Communication Manager (CM), you need to configure a Switch Password in two places: on the “cti-link” screen in CM, and in “Switch Connections” on AES. TheSwitch Password is a password that is used to authenticate the communication between CM and AES. CM and AES use a protocol called Adjunct Switch Application Interface (ASAI) to exchange information and commands related to Computer Telephony Integration (CTI) applications. ASAI requires a Switch Password to establish a secure connection between CM and AES. To configure the Switch Password, you need to use these two screens:

• The “cti-link” screen in CM: This is a screen that allows you to create and manage CTI links, which are logical connections between CM and CTI servers, such as AES. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a name, number, type, and password for each CTI link. The password is the Switch Password that will be used by CM to authenticate AES.
• The “Switch Connections” screen on AES: This is a screen that allows you to create and manage switch connections, which are logical connections between AES and switches, such as CM. You can access this screen using the web interface of AES. On this screen, you need to specify a name, IP address, port, type, and password for each switch connection. The password is the Switch Password that will be used by AES to authenticate CM.

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

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