71301X Avaya Aura Communication Applications Implement Certified Exam Question and Answers

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.

Avaya Session Border Controller for Enterprise (ASBCE) can be deployed on the Kernel-based Virtual Machine (KVM) infrastructure. KVM is a virtualization technology that allows multiple operating systems to run on a single physical machine. To deploy ASBCE on KVM, you need to use a template file that contains the ASBCE software image and configuration parameters. The template file type to be used for KVM deployment is QCOW2, which stands for QEMU Copy-On-Write version 2. QCOW2 is a file format for disk images that can be used by QEMU, which is an open source emulator and virtualizer that can run KVM virtual machines. QCOW2 files support features such as compression, encryption, snapshots, and backing files

A Server Interworking Profile is a type of a Configuration Profile in the Avaya Session Border Controller for Enterprise (ASBCE) that allows setting Timers, URI Manipulation and Header Manipulation, and can be linked to a SIP Server Profile. A Configuration Profile is a configuration object that defines how the ASBCE server handles different aspects of SIP signaling and media processing. A Server Interworking Profile is a Configuration Profile that defines how the ASBCE server interworks with different types of SIP servers, such as Communication Manager, Session Manager, or third-party servers. A Server Interworking Profile can include parameters such as Timers, which specify the timeout values for various SIP transactions; URI Manipulation, which specifies how to modify the user part or domain part of SIP URIs; and Header Manipulation, which specifies how to add, delete, or modify SIP headers. A Server Interworking Profile can be linked to a SIP Server Profile, which is another Configuration Profile that defines the identity and characteristics of a SIP server that communicates with the ASBCE server.

A Survivable Communication Manager (CM) is a Communication Manager instance that provides local call processing and trunking capabilities for remote sites or branches in case of a WAN outage or loss of connectivity with the core servers. A Survivable CM monitors thestatus of the main CM by sending and receiving heartbeat messages at regular intervals. A heartbeat message is a SIP OPTIONS request that tests the availability of the main CM. If the Survivable CM does not receive a response to its heartbeat message within a specified timeout period, it assumes that the main CM is down and triggers a failover process. During the failover process, the Survivable CM accepts IP phone registration requests from the local endpoints and puts the configured IP trunks in a working condition, allowing the remote site or branch to continue making and receiving calls

The Avaya Breeze® cluster type determines the functionality and features of the Avaya Breeze® platform. There are four cluster types: General Purpose, IM_Presence, Core Platform, and Presence Services. The Core Platform cluster type is required to install the Avaya Aura® Presence Services snap-in, as it provides the basic services and components for the Avaya Breeze® platform, such as security, clustering, management, and routing. The other cluster types are either deprecated or not compatible with the Presence Services snap-in.

To provide the customized music, prompts, and/or error announcements when using the Avaya Call Park and Page snap-in, you need to use the Avaya Aura® Media Server (MS). The Media Server is an application that provides media processing services for voice and video calls, such as playing announcements, music on hold, conferencing, transcoding, and recording. The Media Server can be integrated with the Call Park and Page snap-in on the Avaya Breeze® platform, using SIP trunks and media resources. You can upload your own audio files to the Media Server and configure them as custom announcements for the Call Park and Page snap-in34

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

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

When installing the identity certificate and encryption key files on the Avaya Session Border Controller for Enterprise (ASBCE), you need to follow this rule: The filename of the identity certificate (.pem or .crt file) must be different from the filename of the encryption key (.key file). An identity certificate is a file that contains information about the identity and public key of an entity, such as a server or an endpoint. An encryption key is a file that contains information about the private key of an entity, which is used to encrypt and decrypt data. The identity certificate and encryption key files are obtained from a Certificate Authority (CA) or generated by yourself using tools such as OpenSSL. When installing these files on the ASBCE server, you need to make sure that they have different filenames, otherwise they will overwriteeach other and cause errors. For example, you can name them as sbce-cert.pem and sbce-key.key respectively.

When configuring a Reverse Proxy for the Avaya Aura® Web Gateway (AAWG) in the Avaya Session Border Controller for Enterprise (ASBCE), the Server Address field is used to specify the IP address or FQDN and port of the AAWG server. The port used in this field shouldmatch the listen port on the AAWG server that is used for all WebRTC call signalling. The default listen port on the AAWG server is 8444, which is also used by default in the Server Address field of the ASBCE Reverse Proxy configuration. The Reverse Proxy allows external clients to access the AAWG server securely and transparently through the ASBCE

To integrate Avaya Aura® Communication Manager (CM) with Application Enablement Services (AES), and enable the TSAPI link, you need to perform two configuration steps on CM: Configure IP Services and Create a CTI link. These steps are necessary to establish a connection between CM and AES using ASAI protocol, which is a proprietary protocol that provides access to various CTI features of CM. A TSAPI link is a logical connection between CM and AES that allows TSAPI applications to use ASAI features through AES. To configure IP Services and Create a CTI link on CM, you need to use these screens:

• The “ip-services” screen: This is a screen that allows you to create and manage IP services on CM, such as ASAI-IP or C-LAN. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a service type, node name, local node, local port, remote node, remote port, remote domain name, service state, and service link for each IP service. For integrating with AES, you need to create an ASAI-IP service that points to the node name of an AES server.
• The “cti-link” screen: This is a screen that allows you to create and manage CTI links on CM, 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. For integrating with AES, you need to create a CTI link of type ADJ-IP that matches the switch CTI link number on AES.

An H.248 signaling link connects the Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM) by tunneling H.248 messages using TCP port 2944 and securing them using TLS. H.248 is a protocol that defines how media gateway controllers control media gateways for supporting multimedia streams across different networks, such as IP networks and PSTN networks. An H.248 signaling link is a logical connection between an H.248 controller and an H.248 gateway that allows exchanging H.248 messages for controlling media streams. In an Internet Friendly (Edge) Gateway scenario, CM acts as an H.248 controller and ASBCE DBE acts as an H.248 gateway. To connect an H.248 signaling link between CM and ASBCE DBE, these steps are performed:

• CM initiates a TCP connection to ASBCE DBE using port 2944, which is reserved for H.248 over TLS.
• CM and ASBCE DBE negotiate TLS parameters and exchange certificates for mutual authentication and encryption.
• CM and ASBCE DBE establish a secure TLS session over TCP port 2944.
• CM and ASBCE DBE exchange H.248 messages over TLS session for controlling media streams.

Application Enablement Services (AES) communicates with Avaya Aura® Communication Manager (CM) using SIP, which is a protocol for initiating and managing multimedia sessions, such as voice, video, or instant messaging. AES is a server that provides APIs and interfaces for developing and integrating CTI applications with CM and other Avaya Aura® Platform components. AES supports various APIs and interfaces, such as TSAPI, JTAPI, DMCC, Web Services, and ASAI. AES uses SIP to communicate with CM for various purposes, such as registering endpoints, sending and receiving SIP messages, controlling calls, and capturing media. AES also uses SIP to communicate with other Avaya Aura® Platform components, such as Session Manager (SM), System Manager (SMGR), Presence Services (PS), or Breeze Platform.

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

The tracePS CLI tool is a command-line interface tool that allows you to capture and analyze XMPP traffic between Avaya Aura® Presence Services and other XMPP servers or clients. You can use this tool to troubleshoot issues related to presence, instant messaging, federation, or integration with third-party applications. You can also use this tool to generate reports on XMPP traffic statistics, such as message count, message size, message type, and message direction1

The steps for deploying the Avaya Presence Services snap-in are as follows:

• Download the Presence Services snap-in software bundle from the Avaya Support website.
• Log in to System Manager and navigate to Elements > Inventory > Manage Elements.
• Select the Breeze® cluster where you want to deploy the Presence Services snap-in and click Edit.
• In the Snap-ins tab, click Add Snap-in and browse to the location where you saved the Presence Services snap-in software bundle.
• Select the Presence Services snap-in file and click Open.
• Click Commit to load the Presence Services snap-in to System Manager.
• Navigate to Elements > Inventory > Cluster Administration.
• Select the Breeze® cluster where you loaded the Presence Services snap-in and click Manage Snap-ins.
• In the Snap-ins tab, select the Presence Services snap-in and click Activate/Upgrade/Downgrade.
• Click OK to load the Presence Services snap-in into the Breeze® cluster

The output from the show mgc command (issued on a G430/G450 Gateway CLI) can indicate whether the G430/G450 is operating as an Internet Friendly (Edge) Gateway or an Enterprise Gateway. 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 Enterprise Gateway is a device that provides connectivity between endpoints on the same network, such as a LAN or a WAN. The show mgc command displays information about the Media Gateway Controller (MGC), which is the entity that controls the media gateway functions of the G430/G450, such as call processing, routing, and signaling. The MGC can be an Avaya Communication Manager (CM) server or an Avaya Session Border Controller for Enterprise (ASBCE) server. The output from the show mgc command includes these fields:

• Management Link Mode: This field indicates how the G430/G450 communicates with the MGC for management purposes, such as configuration, monitoring, and troubleshooting. The possible values are Direct or Tunnelled. Direct means that the G430/G450 communicates with the MGC using a direct IP connection over TCP port 5022. Tunnelled means that the G430/G450 communicates with the MGC using a tunnel over TCP port 2944 and secured using TLS. This mode is used when the G430/G450 operates as an Internet Friendly (Edge) Gateway and communicates with ASBCE as the MGC.
• H.248 Link Mode: This field indicates how the G430/G450 communicates with the MGC for media gateway control purposes, such as controlling media streams, allocating resources, and creating connections. The possible values areEGW or IFG. EGW means that the G430/G450 communicates with the MGC using H.248 protocol over UDP port 2944. This mode is used when the G430/G450 operates as an Enterprise Gateway and communicates with CM as the MGC. IFG means that the G430/G450 communicates with the MGC using H.248 protocol over TCP port 2944 and secured using TLS. This mode is used when the G430/G450 operates as an Internet Friendly (Edge) Gateway and communicates with ASBCE as the MGC.
• H.248 Link Status: This field indicates whether the H.248 link between the G430/G450 and the MGC is up or down, and whether it is encrypted or not. The possible values are UP/Encrypted, UP/Unencrypted, DOWN/Encrypted, or DOWN/Unencrypted. UP means that the H.248 link is established and functional. DOWN means that the H.248 link is not established or not functional. Encrypted means that the H.248 link is secured using TLS encryption. Unencrypted means that the H.248 link is not secured using TLS encryption.

Therefore, to determine whether the G430/G450 is operating as an Internet Friendly (Edge) Gateway or an Enterprise Gateway, you can look at these two fields in the output from the show mgc command:

• If the H.248 Link Mode displays IFG, it means that the G430/G450 is operating as an Internet Friendly (Edge) Gateway and communicating with ASBCE as the MGC using H.248 over TCP port 2944 and secured using TLS.
• If the H.248 Link Status displays UP/Encrypted, it means that the G430/G450 is operating as an Internet Friendly (Edge) Gateway and communicating with ASBCE as the MGC using a secure and functional H.248 link.