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

The initTM -f command is used to initialize the trust management between the Avaya Breeze® server and the Avaya Aura® System Manager. This command requires an enrollment password that is configured in the System Manager web interface, under Security > Enrollment Password. The enrollment password has a validity period that can be set by the administrator. If the enrollment password has expired, the initTM -f command will fail. Therefore, before running the initTM -f command, you should verify that the enrollment password is configured and valid12

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

The Avaya Spaces Calling extension is a softphone that provides calling features to users of Avaya Spaces by leveraging their existing Avaya infrastructure. This extension can be used alongside the Avaya Spaces web application or desktop client to make and receive audio calls through the Avaya Aura® Web Gateway (AAWG). To add the Avaya Spaces Calling extension, you need to have internet access and use the Google Chrome browser to open the Chrome Web Store. Then, you need to search for the Avaya Spaces Calling extension and click on the Add to Chrome button. The extension will be installed and added to your Chrome browser. You can then use the extension icon in the browser toolbar to access the Avaya Spaces Calling settings and features12

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

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

When configuring the Avaya Call Park and Page snap-in, the Call Park Extension Group attribute is used to specify the extensions that can be used to park calls. The format of the Call Park Extension Group attribute is as follows:

():,,…

The location ID is a numeric value that identifies the location where the Call Park and Page snap-in is deployed. The number of digits is the number of digits in each extension. The extensions are the actual extensions that can be used to park calls. For example, 3(1):4000,4001,4002 means that the Call Park and Page snap-in is deployed in location 3, each extension has one digit, and the extensions are 4000, 4001, and 40021

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

After installing a new Avaya Session Border Controller for Enterprise (ASBC6) component / device using the EMS GUI, you click on the Install link on the EMS Device Management page. After briefly displaying the Provisioned status, the final status that the ASBCE component / device should display is Running. The EMS Device Management page is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The EMS Device Management page displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Running. The Running status means that the component / device is fully operational and ready to handle traffic. Therefore, after installing a new ASBCE component / device using the EMS GUI, you should wait until it displays a Running status on the EMS Device Management page.

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.

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.

If the Avaya Session Border Controller for Enterprise (ASBCE) does not trust the Certificate Authority (CA) that signed the WebLM server identity certificate, you can use the sbceconfigurator.py fix-weblm-cert command issued from the EMS CLI to fix the trust issue. The WebLM server is a web-based licensing application that manages licenses for various Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. The WebLM server uses an identity certificate to authenticate itself to other entities that communicate with it using HTTPS or REST APIs. The identity certificate is signed by a CA, which is an entity that issues and verifies certificates. The ASBCE server needs to trust the CA that signed the WebLM server identity certificate in order to communicate with it securely and obtain licenses from it. If the ASBCE server does not trust the CA, you can use the sbceconfigurator.py fix-weblm-cert command to install the CA certificate on the ASBCE server and establish trust with it. The sbceconfigurator.py tool is a Python script that runs on the EMS component of the ASBCE server and performs various configuration tasks. The EMS component is responsible for managing and monitoring the ASBCE server. You can access the EMS CLI using SSH or Telnet and run the sbceconfigurator.py tool from there.

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

The Survivable Communication Manager (CM) is configured on the System Manager (SMGR) as a Managed Element. A Managed Element is an entity that can be managed by SMGR, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. A Survivable 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 can be deployed on an S8300D server or on an external server such as Dell R620/R630 or HP DL360 G8/G9. To configure a Survivable CM as a Managed Element on SMGR, you need to specify its name, type, IP address, login credentials, and security settings56

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

If the customer requires High Availability (HA) for the Avaya Session Border Controller for Enterprise (ASBCE), the minimum number of servers or virtual machines that are required is 2. High Availability (HA) is a feature that provides redundancy and fault tolerance for the ASBCE server by deploying two ASBCE servers in a pair, either in the same location or geographically dispersed. The two ASBCE servers act as a single logical entity and share a common configuration and license. One ASBCE server is designated as the active server and handles all traffic, while the other ASBCE server is designated as the standby server and monitors the status of the active server. If the active server fails or becomes unreachable, the standby server takes over and becomes the new active server, ensuring continuity ofservice. The two ASBCE servers synchronize their configuration and state information using a dedicated HA link between them