Avaya 71301X Avaya Aura Communication Applications Implement Certified Exam Exam Practice Test

To connect to the Application Enablement Services (AES) web interface, you need to use the correct URL and the default login ID. The AES web interface is a web-based application that allows you to configure and manage the AES server and its features. You can access the AES web interface using any web browser that supports HTTPS. The URL for connecting to the AES web interface is https:// :8443, where is the IP address of the AES server that you want to connect to. The port number 8443 is the default port for HTTPS communication with the AES server. After entering the URL in the web browser, you will see a login screen where you need to enter the login ID and password for accessing the AES web interface. The default login ID for the AES web interface is craft, which is a system administrator account that has full access to all features and functions of the AES server. The default password for the craft account is craft. You can change the password or create other user accounts with different access levels using the Security Database feature of the AES web interface.

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

The Avaya Aura® Media Server (AAMS) associated with the Avaya Aura® Web Gateway (AAWG) is used for media processing for calls to or from Avaya Spaces Calling. Avaya Spaces Calling is a softphone that provides calling features to users of Avaya Spaces by leveraging their existing Avaya infrastructure. When a user makes or receives a call using Avaya Spaces Calling, the AAWG handles the WebRTC call signaling and the AAMS handles the media. The AAMS converts the WebRTC media to SIP media and vice versa, and provides services such as announcements, music on hold, conferencing, transcoding, and recording. The AAMS processes the media for the duration of the call, regardless of whether the call is shuffled or not by Communication Manager

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

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.

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.

In the context of Avaya Aura® Presence Services, a Watcher is a user who is interested in the presence information of another user, called a Presentity. A Watcher sends a Subscribe message to the Presence Services snap-in on the Avaya Breeze® server, requesting to receive notifications about the current and future presence status of the Presentity. The Presence Services snap-in then sends a Notify message to the Watcher, containing the presence information of the Presentity. The Watcher can use this information to decide how and when to communicate with the Presentity12

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

After deploying Avaya Aura® Web Gateway (AAWG) in a Virtualized Environment (VE), the next step is to enroll AAWG with System Manager (SMGR) by running the initTM command on the AAWG CLI. The initTM command is used to initialize the trust management between the AAWG server and the SMGR server. This command requires an enrollment password that is configured in the SMGR 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 command will fail. Therefore, before running the initTM command, you should verify that the enrollment password is configured and valid

Avaya Aura® Presence Services does not require a separate license file or an instance license. User licenses are an entitlement as part of the Avaya Aura® suite licensing, such as Foundation, Mobility, Team Engagement, or Customer Engagement. The user licenses are consumed based on the number of users who are provisioned for Presence Services in System Manager

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.

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

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.

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

When setting up the Avaya Session Border Controller for Enterprise (ASBCE) SIP Trunking, you need one Subscriber Flow and one Server Flow. A Subscriber Flow is a configuration object that defines how the ASBCE handles SIP requests and responses from or to an endpoint, such as an IP phone or a softphone. A Server Flow is a configuration object that defines how the ASBCE handles SIP requests and responses from or to a server, such as a Communication Manager or a Session Manager. For SIP Trunking, you need one Subscriber Flow that connects the ASBCE to the internal SIP server, and one Server Flow that connects the ASBCE to the external SIP service provider. These flows specify parameters such as source and destination IP addresses, ports, protocols, codecs, encryption, authentication, and routing rules3

To access the TSAPI Test from the Application Enablement Services (AES) menu, you need to select Utilities. The TSAPI Test is a basic application for making a call using TSAPI, which is a high-level API for CTI applications based on CSTA I standard. TSAPI allows access to the third party call control capabilities of CM through AES. The TSAPI Test application can be used to verify that the TSAPI client is correctly installed and working on AES. If the TSAPI Test application fails to make the call, an error message is provided to aid in troubleshooting the cause of the failure. To access the TSAPI Test from the AES menu, you need to follow these steps:

• Log in to the web interface of AES using your username and password.
• Click on Utilities on the left side menu.
• Click on TSAPI Test under Utilities.
• Enter the parameters for making a call, such as device name, destination number, user ID, and password.
• Click on Make Call.

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.

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

To trace SIP messages exchanged during a Remote Worker registration in real-time, you can use the tracesbc CLI tool on the Avaya Session Border Controller for Enterprise (ASBCE). The tracesbc tool is used to capture and display SIP messages and media statistics for calls that traverse the ASBCE server. You can use various filters and options to specify which calls or messages you want to trace. For example, you can filter by source or destination IP address, port, protocol, or call ID. You can also specify how long you want to run the trace and how many messages you want to display. The tracesbc tool can help you troubleshoot and diagnose issues with Remote Worker registration and call setup