Avaya Avaya Certifications 71301X Questions & Answers

• Question 41:

  When integrating the Application Enablement Services (AES) with the Avaya Aura Communication Manager (CM), in which two places is the Switch Password configured?

  A. on the "ip-services" screen in the Avaya Aura Communication Manager (CM), and in "Switch Connections'1 on the Application Enablement Services (AES)

  B. on the "cti-link" screen in the Avaya Aura Communication Manager (CM), and in "Switch Connections" on the Application Enablement Services (AES)

  C. on the "ip-services" screen in the Avaya Aura Communication Manager (CM), and in "TSAPI Link" on the Application Enablement Services (AES)

  D. on the "cti-link" screen in the Avaya Aura Communication Manager (CM), and in "TSAPI Link" on the Application Enablement Services (AES)

  Correct Answer: B

  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.

• Question 42:

  To allow communications between the Avaya Aura Device Services (AADS) and the Avaya Aura Web Gateway (AAWG), which three configuration steps are required? (Choose three.)

  A. On the AAWG, the Server-to-server interface port needs to be opened using a shell script.

  B. The AAWG FQDN needs to be configured as a Trusted Host on the AADS.

  C. The AADS FQDN needs to be configured as a Trusted Host on the AAWG.

  D. The AADS FQDN, Client interface port and Server-to-server interface port needs to be configured on the AAWG.

  E. On the AADS, the Server-to-server interface port needs to be opened using a shell script.

  Correct Answer: BCD

  To allow communications between the Avaya Aura Device Services (AADS) and the Avaya Aura Web Gateway (AAWG), you need to perform the following configuration steps: Configure the AAWG FQDN as a Trusted Host on the AADS: A Trusted Host is an entity that is allowed to communicate with the AADS server using HTTPS or REST APIs. You need to configure the Fully Qualified Domain Name (FQDN) of the AAWG server as a Trusted Host on the AADS server, using the System Manager web interface. This allows the AAWG server to access the AADS server for device management and configuration purposes3 Configure the AADS FQDN as a Trusted Host on the AAWG: Similarly, you need to configure the FQDN of the AADS server as a Trusted Host on the AAWG server, using the app configure command line utility. This allows the AADS server to send dynamic configuration parameters and certificates to the AAWG server for WebRTC call signaling and media processing4 Configure the AADS FQDN, Client interface port and Server-to-server interface port on the AAWG: You also need to configure the FQDN, Client interface port and Server-to-server interface port of the AADS server on the AAWG server, using the app configure command line utility. These parameters are used by the AAWG server to establish secure connections with the AADS server for device management and configuration purposes. The default Client interface port is 9443, while the default Server-to-server interface port is 84434

• Question 43:

  Which statement describes how an H.248 signaling link connects the Internet Friendly (Edge) Gateway to the Avaya Communication Manager (CM)?

  A. It is transported using HTTPs/REST via the Avaya Session Border Controller for Enterprise (ASBCE).

  B. It is transported using HTTPs using port 443.

  C. It is tunnelled using TCP port 2944 and secured using TLS.

  D. It is transported using TCP port 80 and secured using a VPN connection to the Avaya Session Border Controller for Enterprise (ASBCE).

  Correct Answer: C

  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.

• Question 44:

  Which statement regarding the license for the Avaya Aura Web Gateway (AAWG) is true?

  A. A non-virtualized AAWG has an embedded local WebLM server where the license file is installed.

  B. Each AAWG deployed requires its own license file.

  C. Use of AAWG is an entitlement included with a Session Manager (SM) license, and therefore AAWG does not require a separate license.

  D. The AAWG license file can be installed on the WebLM server embedded in the System Manager (SMGR), or on a standalone WebLM server.

  Correct Answer: D

  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

• Question 45:

  In the Avaya Session Border Controller for Enterprise (ASBCE), what is the state of a Network Interface, after the deployment?

  A. Deployed

  B. Active

  C. Disabled

  D. Enabled

  Correct Answer: C

  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

• Question 46:

  In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, where do you access the tracesbc tool that displays SIP messages in real- time as they pass through the ASBCE?

  A. from the EMS component / device command line via SSH session using PuTTY

  B. from the SBC component/ device command line via SSH session using PuTTY

  C. from the Avaya Aura System Manager (SMGR) web interface, under the Elements>; Session Border Controller for Enterprise > Session Border Controller menu

  D. from the EMS web interface

  Correct Answer: B

  In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, you can access the tracesbc tool that displays SIP messages in real-time as they pass through the ASBCE from the SBC component/ device command line via SSH session using PuTTY. A Multi-Server/ HA deployment is a deployment where two or more ASBCE servers are deployed in a pair or cluster, providing redundancy and scalability for the ASBCE server. Each ASBCE server consists of two components: the EMS component and the SBC component. The EMS component is responsible for managing and monitoring the ASBCE server, while the SBC component is responsible for processing and routing the SIP traffic. The tracesbc tool is a CLI tool that runs on the SBC component and captures and displays SIP messages and mediastatistics for calls that traverse the ASBCE server. You can use PuTTY, which is a terminal emulator application, to establish an SSH session with the SBC component and run the tracesbc tool from the command line.

• Question 47:

  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. You try to ping this IP address from a PC in the same subnet, but it fails.

  What is the first step to resolve the problem?

  A. Navigate to Network and Flows > Network Management > Interfaces and enable the Bl interface.

  B. Navigate to Device Management, and click on Restart Application.

  C. Navigate to Device Management, and and click on Reboot.

  D. Connect to the ASBCE CLI and reboot the ASBCE.

  Correct Answer: A

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

• Question 48:

  Which three SIP headers should be overwritten with a SIP domain in a Topology Hiding Profile associated with a Session Manager in a typical Avaya Session Border Controller for Enterprise (ASBCE) deployment? (Choose three.)

  A. From

  B. Refer-To

  C. To

  D. Request-Line

  E. Referred-By

  Correct Answer: ABC

  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, [email protected] can become [email protected], 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

• Question 49:

  Which statement about SIP Entities being required to support Avaya Aura Presence Services hosted on a single Avaya Breeze?server is true?

  A. Only one SIP Entity is required, using the Avaya Breeze?server Security Module IP address. This SIP Entity should have the type Presence Services selected.

  B. Only one SIP Entity is required, using the Avaya Breeze?server Security Module IP address. This SIP Entity should have the type Avaya Breeze?selected.

  C. Two SIP Entities are required, using the same Avaya Breeze?server Security Module IP address. One SIP Entity should have the type Avaya Breeze?selected, and the other should have the type Other selected.

  D. Two SIP Entities are required, using the same Avaya Breeze?server Security Module IP address. One SIP Entity should have the type Avaya Breeze?selected, and the other should have the type Presence Services selected.

  Correct Answer: D

  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

• Question 50:

  Which Avaya Breeze?cluster type is required to install the Avaya Aura Presence Services snap-in?

  A. General Purpose

  B. IM_Presence

  C. Core Platform

  D. Presence Services

  Correct Answer: C

  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.