33160X Sample Questions Answers

According to the Avaya Contact Recorder Advanced Installation Guide1, the following server roles are valid for recording:

• RTP Proxy: This role is responsible for receiving RTP streams from the network and forwarding them to the IP Recorder role. It also handles SIP signaling for call recording.
• IP Recorder: This role is responsible for recording RTP streams received from the RTP Proxy role and storing them as audio files on the disk. It also handles metadata extraction and encryption of the recordings.
• Screen Recorder: This role is responsible for recording the screen activity of the agents using a screen capture driver. It also handles compression and encryption of the screen recordings.

The other two roles, Recorder Integration Service and Replay role, are not directly involved in recording, but rather in integrating with other systems and providing playback functionality.

References: 1: Avaya Contact Recorder Advanced Installation Guide

According to the Avaya Workforce Optimization Select Migration Guide, the side-by-side approach is a migration method that involves installing a new Avaya Workforce Engagement system on a separate set of servers, and then transferring the data and configurationfrom the existing AWFO system to the new system. Some of the factors that led to this recommendation are:

• B. It will support rollback by reverting to the 15.1 Data Center. The side-by-side approach allows the customer to keep their existing AWFO system intact and operational until they are ready to switch to the new Avaya Workforce Engagement system. This means that if there are any issues or problems with the new system, the customer can easily revert to the 15.1 Data Center by changing the DNS settings and restoring the database backups.
• C. It will minimize upgrade downtime risks. The side-by-side approach reduces the downtime risks associated with upgrading the system, as the customer can perform most of the migration steps in parallel with their normal operations. The customer can also schedule the final cutover to the new system at a convenient time, and avoid any disruption to their service levels or customer experience.

The statements A and D are incorrect because:

• A. It is suitable for small systems only. This is not true, as the side-by-side approach can be used for any size of system, depending on the customer’s preference and resources. The side-by-side approach may require more hardware and software licenses than the in-place approach, but it also offers more flexibility and reliability for the migration process.
• D. The data on the source DC servers are reformatted with Windows Server 2016, and installed with R20.X. This is not true, as this describes the in-place approach, not the side-by-side approach. The in-place approach is a migration method that involves upgrading the existing AWFO system on the same set of servers, and then applying the R20.X installation on top of it. The in-place approach requires reformatting the source DC servers with Windows Server 2016, which can result in data loss or corruption if not done properly. References: Avaya Workforce Optimization Select Migration Guide

According to the Avaya Workforce Optimization Select Installation Guide, the prerequisites for installing Avaya Workforce Engagement server in deployment level 3, 4 or 5 are as follows:

• B. The Framework components can be installed using a Management Service Account (MSA). An MSA is a domain account that has local administrator privileges on all servers in the Framework domain. The MSA is used to install and run the Framework services and components.
• C. The Framework components need to be installed using a domain account with local administrator privileges in the Framework server. This account is different from the MSA and is used to log in to the Framework server and run the installation wizard.
• D. Data center zone servers, service user and group account, must all be members of the domain’s Active Directory. A data center zone is a logical grouping of servers that share common resources and settings. A service user account is a domain account that has local administrator privileges on all servers in the data center zone. A service group account is a domain group that contains all service user accounts in the data center zone.

The statements A and E are incorrect because:

• A. Data center servers can be split in multi-domain forests. This is not a prerequisite for installing Avaya Workforce Engagement server, but rather an optional configuration that allows for more flexibility and scalability. However, this configuration requires additional steps and considerations, such as setting up trust relationships between domains and configuring DNS suffixes.
• E. The Framework components can be installed in a workgroup environment. This is not a prerequisite for installing Avaya Workforce Engagement server, but rather an alternative configuration that is only supported for deployment level 1 or 2. A workgroup environment does not use Active Directory or domain accounts, but rather local accounts and groups on each server. References: [Avaya Workforce Optimization Select Installation Guide]

According to the Avaya Workforce Engagement Support Installation Guide, if the framework installation fails, the installer will stop but does not quit from the tool. The failed components are tracked to the installer’s log file, which is located in C:\Program Files\Avaya\Avaya Workforce Engagement Support\Logs. The installer will also display a message indicating which component failed and provide a link to the log file. The user can then review the log file, resolve the issue, and resume the installation from where it left off. References: Avaya Workforce Engagement Support Installation Guide, page 34.

According to the Avaya Workforce Engagement Support Administration Guide, Central Archive is a feature that allows administrators to archive recordings from one or more recorders to a central location. Central Archive uses campaigns, which are sets of filter rules that define which recordings to archive based on criteria such as date range, recording type, agent ID, DNIS, ANI, and others. Central Archive does not pull and archive specified recordings from a local recorder only, as it can archive recordings from multiple recorders. The archive role does not reside on the recorder, but on a separate server that communicates with the recorder. Central Archive does not archive 100% of recordings, as it depends on the campaign configuration. References: Avaya Workforce Engagement Support Administration Guide, page 105.

Avaya Contact Recorder Advanced (ACRA) is a component of the Avaya Workforce Engagement suite that provides the capability to record, store, and play back voice and screen interactions. The two primary functions of ACRA are record and store/archive. Record function allows businesses to capture customer interactions across multiple channels and media types, such as voice, video, chat, email, and social media. Store/archive function enables businesses to securely store and manage the recorded interactions in compliance with various regulations and standards, such as PCI, GDPR, and MiFID II. ACRA also supports replay function, which allows users to search and play back the recorded interactions based on various criteria, such as date, time, agent, customer, and keywords. Quality monitor function is not a primary function of ACRA, but it is a separate component of the Avaya Workforce Engagement suite that synchronizes the agent’s on-screen activity to the audio recording and provides agent performance evaluation tools. References:

• Avaya Workforce Optimization
• Avaya Contact Recording - ESi
• Avaya Contact Recording – ESi

According to the Avaya Contact Recorder Configuration and Administration Guide, the three main components for analysing an Avaya Workforce Engagement recording integration with Avaya Contact Recorder Advanced (ACRA) are:

• A. Customer Environment. This component refers to the customer’s network infrastructure, communication platform, contact center applications, and endpoints that are involved in the recording process. The customer environment determines the type and source of the audio and data that are captured by ACRA, as well as the recording method and configuration that are used. For example, the customer environment may include Avaya Aura Communication Manager, Avaya Aura Application Enablement Services, Avaya Experience Portal, Avaya Proactive Outreach Manager, Avaya IP Office Contact Center, etc.
• D. Recorder. This component refers to the ACRA server or servers that are responsible for recording, storing, and playing back voice and screen interactions. The recorder component consists of various services and components that perform different functions, such as capturing audio and data from different sources, applying recording rules and schedules, encrypting and compressing recordings, archiving recordings to external storage devices or locations, providing search and replay capabilities, etc.
• E. RIS (Recorder Integration Service). This component refers to the service that enables ACRA to integrate with Avaya Workforce Engagement applications, such as Quality Management, Coaching, eLearning, etc. The RIS component allows ACRA to send recording metadata and files to Avaya Workforce Engagement applications for further analysis and evaluation. The RIS component also allows ACRA to receive requests from Avaya Workforce Engagement applications to start or stop recording on demand.

According to the Avaya Workforce Engagement Support Installation Guide, the recorder Integration Service is a component that enables the recorder to communicate with the switch and receive call signaling and metadata. The recorder Integration Service requires a CTI adapter, which is a software module that connects to the switch and provides the necessary information to the recorder. There can be multiple CTI adapters per system, depending on the number of data sources and switches. A CTI adapter is necessary for Integration Service, as it is responsible for providing the call data to the recorder. References: Avaya Workforce Engagement Support Installation Guide, page 18.

Interactions is an Avaya Workforce Engagement component that can help customers evaluate an agent and increase customer satisfaction. Interactions allows customers to monitor, search, replay, and evaluate voice and screen recordings of agent interactions with customers. Customers can use Interactions to assess the quality of service, identify best practices, provide feedback, and coach agents to improve their performance and customer satisfaction. References:

• Avaya Workforce Engagement Administration Guide, page 233
• Avaya Workforce Engagement Interactions User Guide, page 94

According to the Avaya Workforce Optimization Select Administration Guide, one of the possible causes for the “Edit Access Rights” button being greyed out when creating a new user on the Framework server is that the user profile has not been created as a supervisor. Only supervisors can have access rights assigned to them, which determine what functions and features they can access in the Avaya Workforce Engagement system. To create a user profile as a supervisor, the administrator must select “Supervisor” from the Role drop-down list in the User Details tab of the User Profile screen. References: Avaya Workforce Optimization Select Administration Guide

The Disk Manager is a component of the Avaya Contact Recorder Advanced that manages the storage of recording files on disk partitions. It performs two main tasks:

• It removes all the data associated with a recording file when necessary, such as when the retention period expires, when the file is deleted manually, or when the file is corrupted or inaccessible.
• It monitors the disk space usage and deletes the oldest recordings from the drive to make free space for the new recordings, according to the configured thresholds and policies.

According to the Avaya Documentation website1, the documentation category that covers the Avaya Workforce Engagement install and configure process up to the successful SAT on the customer site is Implementation guides. Implementation guides provide step-by-step instructions on how to install, configure, test, and troubleshoot Avaya Workforce Engagement components and features on various platforms and environments. Implementation guides also include information on system requirements, prerequisites, best practices, tips, and examples for successful deployment of Avaya Workforce Engagement solutions. References: Avaya Documentation

According to the Avaya Contact Recorder Administration Guide, the Capture Status tool is a web-based application that provides information related to the configuration of Avaya Contact Recorder Advanced (ACRA), such as adapters, data sources, recording rules, and real time monitors. The Capture Status tool can be used for troubleshooting andmonitoring the recording system. The tool can display the status of each component, such as online, offline, or error. The tool can also show the details of each component, such as name, type, IP address, port, version, and configuration. The tool can also provide logs and statistics for each component, such as number of calls recorded, number of errors encountered, and number of active channels. References: Avaya Contact Recorder Administration Guide

According to the Avaya Contact Recorder Installation Guide, the first step to properly setting up the voice recording in an ACRA environment is to create a phone Data Source. A phone Data Source defines the type of phone system that is being recorded, such as Avaya Aura Communication Manager, Avaya IP Office, or Avaya Communication Server 1000. A phone Data Source also specifies the connection details and recording parameters for the phone system. References: [Avaya Contact Recorder Installation Guide]

The Employee Archive Report is a monitoring tool that can be used to get information about the number of call employee segments recorded and archived. The EmployeeArchive Report shows the number of recordings, the total duration, the total size, and the average size of the recordings for each employee or group of employees. The Employee Archive Report can be filtered by date range, organization, group, employee, recording type, and recording status. The Employee Archive Report can also be exported to a CSV file for further analysis1 References: 1: Avaya Workforce Engagement Support - Reporting Guide, page 25-262

To have voice recording with Avaya Contact Recorder Advanced (ACRA), Avaya Workforce Engagement requires a Phone data source type. A Phone data source type is used to import phone-related data from ACRA, such as agent IDs, extensions, call IDs, call durations, and call directions. This data is used to associate voice recordings with agents and calls in the Avaya Workforce Engagement system. References:

• Avaya Workforce Engagement Integration Services User Guide, page 294
• Avaya Workforce Engagement Integration Services User Guide, page 464

Enterprise Manager (EM) is a browser-based interface that provides centralized administration and management of the Avaya Workforce Engagement suite. It allows application-level functionality configuration, such as recording rules, quality monitoring forms, and coaching assignments. It also eliminates duplicate configuration and shares data across applications, such as users, groups, and schedules. User access is not through the system Management desktop applications, but through the web browser. EM also provides system-level configuration and monitoring, such as license management, backup and restore, and system health. References:

• Avaya Workforce Optimization
• Avaya Workforce Engagement Installation Guide