Authentic Avaya Certification Exam 71301X Questions Answers

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.

The statement that is true about the Application Enablement Services (AES) certificate management is that AES is shipped with a default certificate which is valid for one year, and a customer-provided server identity certificate must be installed before the default certificate expires. A server identity certificate is a file that contains information about the identity and public key of a server, such as AES. A server identity certificate is used to authenticate the server to other entities that communicate with it using HTTPS or SIP over TLS. A server identity certificate is signed by a Certificate Authority (CA), which is an entity that issues and verifies certificates. AES uses certificates for various purposes, such as securing web access, enabling HTTPS-based APIs, encrypting SIP signaling, and supporting mutual authentication with endpoints or servers. AES comes with a default self-signed certificate that can be used for testing or demonstration purposes. The default certificate is valid for one year from the date of installation. After one year, the default certificate expires and needs to be replaced with a valid customer-provided certificate from a trusted CA. To install a customer-provided certificate on AES, you need to use tools such as OpenSSL or Keytool to generate a Certificate Signing Request (CSR), submit it to a CA, obtain a signed certificate from the CA, and upload it to AES using the web interface or CLI.

When deploying the Avaya Aura® Presence Services on Avaya Breeze®, you can check the status of the Presence Services snap-in in System Manager, under Elements > Avaya Breeze> Service Management > Services. The status indicates the state of the snap-in on the Avaya Breeze® cluster. The status Active means that the snap-in is running and ready to support Presence and IM. The other statuses are either intermediate or error states that indicate that the snap-in is not fully functional or operational.