Explanation
The Capture service is a component that is installed on an employee desktop along with the Screen Capture module. The Capture service communicates with the recorder to track employee logging/logoff, as well as to start and stop the Screen Capture module according to the recording rules. The Capture service also sends the screen capture files to the recorder for archiving1 References: 1: Avaya Workforce Engagement Support - Installation Guide, page 312

Explanation
The IP Capture log is a log file that records the RTP packets and the associated CTI metadata for each call that is recorded by the Avaya Workforce Engagement (AWE) solution. The IP Capture log helps to troubleshoot issues related to integration recording, such as missing or incomplete recordings, audio quality issues, or incorrect metadata. The IP Capture log shows the following information for each call:
The call ID, which is a unique identifier for the call
The start time and end time of the call
The source and destination IP addresses and ports of the RTP packets
The codec and payload type of the RTP packets
The CTI metadata, such as agent ID, skill ID, ANI, DNIS, etc., that are associated with the call The status of the recording, such as started, stopped, paused, resumed, etc.
The IP Capture log does not record management information, such as configuration settings, license information, or system events. It also does not show CTI statistics, such as the number of events received or processed, or the performance metrics of the CTI server. It only shows the CTI events that are relevant to the recording of each call.
References: 1: Avaya Workforce Engagement Support - Troubleshooting Guide - Chapter 4: Troubleshooting Integration Recording Issues - Section 4.2: Using IP Capture Log for Troubleshooting Integration Recording Issues 22:
https://documentation.avaya.com/en-US/bundle/troubleshootingAvayaWorkforceEngagement_r381/page/Troubl

Explanation
In a scenario with Avaya Contact Recorder Advanced (ACRA) using station-side recording (TDM), this statement is true because of how ACRA handles call segments and conferences. A call segment is a part of a call that has a single source and destination. A conference is a call that has more than two parties involved.
ACRA records each call segment separately and assigns them a unique ID. ACRA also records conferences as separate call segments with their own IDs. ACRA does not record internal calls between extensions unless they are explicitly configured to do so. Therefore, when there is an outgoing call that is put on hold for a consult with a supervisor, and then conferences with a supervisor, ACRA will record three call segments: one for the outgoing call with the customer, one for the internal consult with the supervisor, and one for the conference with both parties. However, ACRA will not archive the internal consult segment because it is aninternal call that is not configured to be recorded. ACRA will only archive the outgoing call segment and the conference segment, which can be searched and replayed using the Avaya Contact Recorder interface or other applications5 References: 5: Avaya Workforce Engagement Support - Contact Recording Technical Reference Guide, page 16-186

Explanation
The MSA account is a member of the SysAdmin role in SQL, and can perform all required activities related to database installation and first-time configuration in Avaya Workforce Engagement. The MSA account is a service account that is used to run the Avaya Workforce Engagement services and access the Archive Database. The MSA account must be created before installing the Avaya Workforce Engagement software and must have the appropriate permissions and privileges. The MSA account must also be added to the local Administrators group on each server where Avaya Workforce Engagement components are installed1 References: 1: Avaya Workforce Engagement Support - Installation Guide, page 18-192

Explanation
According to the Avaya Workforce Engagement Support Administration Guide, a campaign is a set of filter rules that define which recordings to archive. A campaign can include filters based on date range, recording type, agent ID, DNIS, ANI, and other criteria. A campaign can also specify whether to archive audio only, screen only, or both. A campaign can be associated with one or more archive profiles, which define the destination and format of the archived content. References: Avaya Workforce Engagement Support Administration Guide, page 105.