Pass the Avaya ACIS-7130 71301X Questions and answers with ExamsMirror

To associate the Avaya Call Park and Page snap-in to an Avaya Workplace Client, you need to perform the following key configuration steps:

Add a Service Profile: A Service Profile is a set of parameters that defines the features and capabilities of a user or device in System Manager. You need to create a Service Profile for the Call Park and Page snap-in, under Users > User Management > Service Profiles. In the Service Profile, you need to specify the name, type, domain, and SIP Entity of the Call Park and Page snap-in. You also need to enable the Call Park feature and configure the Call Park activation and deactivation feature codes1

Configure a Call Park activation and deactivation feature code: A feature code is a numeric sequence that activates or deactivates a specific feature on Communication Manager. You need to configure a Call Park activation and deactivation feature code on Communication Manager, using the change feature-access-codes command. The Call Park activation feature code allows a user to park a call on a specified extension, while the Call Park deactivation feature code allows a user to retrieve a parked call from any extension2

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

With Dynamic Licensing configured in the Avaya Session Border Controller for Enterprise (ASBCE), the ASBCE will issue a request to the WebLM server to allocate additional licenses based on the Fetch Count value when the percentage of free (available) standard sessions licenses drops below 30% (Low Watermark). Dynamic Licensing is a feature that allows the ASBCE to dynamically allocate and release licenses from a pool of licenses managed by the WebLM server. The Fetch Count value is a parameter that specifies how many licenses are requested from the WebLM server at a time. The Low Watermark value is a parameter that specifies the threshold percentage of free licenses that triggers a request for more licenses from the WebLM server. The High Watermark value is a parameter that specifies the threshold percentage of free licenses that triggers a release of unused licenses to the WebLM server

The CLI tool that is used to trace messages in real-time as they pass through the Avaya Session Border Controller for Enterprise (ASBCE) is tracesbc. The tracesbc tool is a CLI tool that runs on the SBC component of the ASBCE server and captures and displays 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 SIP registration and call setup.

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

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

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.