A phone data source.

A trader data source.

An application data source.

A Collector configured for a data source with External Recorder or IP Trade switch/sub-type.

Unique name for the Collector.

Type of Collector available for the selected data source. If the field is disabled, no other type of Collector can be created for the selected data source.

• Local: The CDR storage location is either on the same server as the Collector, or elsewhere on the same Local Area Network (LAN).

• SFTP: The Collector uses the SSH File Transfer Protocol (SFTP) to connect to the data source host.

• BT TradeSense WBA: Only available for the Collectors of BT Trading Enterprise/IP Trade data sources.

• Genesys PureEngage: Only available for the Collectors of Genesys Engage (formerly PureEngage) data sources.

• Genesys CX API: Only available for the Collectors of Genesys Cloud CX data sources.

• Kinesis Stream: Only available for the Collectors of Amazon Connect data sources.

• Unigy Blue Wave API: Only available for the Collectors of IPC Unigy data sources.

• Zoom Meeting API: Only available for the Collectors of Zoom Meetings data sources.

• Zoom Phone API: Only available for the Collectors of Zoom Phone data sources.

IP address or Fully Qualified Domain Name (FQDN) for the data source host.

Port number that the Collector uses to connect to the data source host.

If the connection requires the Windows domain name, the name for the domain.

If the data source requires the Collector to use account credentials for access, the user name for the account.

If the data source requires the Collector to use account credentials for access, the password for the account.

If the connection requires the Collector to use account credentials for access, the unique identifier for the account.

If the data source requires the Collector to use account credentials for access, the client key or identifier.

If the data source requires the Collector to use account credentials for access, the client value or secret.

Location of the files on the data source host that the Collector needs to access. Example:

/cisco/440XXX

Regular expression Capture Verification uses to identify the required Call Detail Record (CDR) files on the data source host.

Capture Verification locates the required CDRs by file pattern. Each file pattern is specific to a switch type. For example, for Cisco Unified Call Manager, the default CDR file names start with CDR_ or cdr_.

Version of the switch API the Collector connects to.

When checked, all server certificates are trusted, even if they are invalid.

If the data source requires the Collector to use an API key or API token for authentication, the value of the API key or token.

If selected, it allows the configuration of connection details for a second BT TradeSense endpoint to be used in resilient TradeSense deployments.

IP address or Fully Qualified Domain Name (FQDN) for the secondary TradeSense endpoint.

Only available if Use multiple TradeSense endpoints is selected.

Port number that the Collector uses to connect to the secondary TradeSense endpoint.

Only available if Use multiple TradeSense endpoints is selected.

If the secondary TradeSense endpoint requires the Collector to use an API key or API token for authentication, the value of the API key or token.

Only available if Use multiple TradeSense endpoints is selected.

When checked, the Collector uses the TLS (Transport Layer Security) protocol version 1.2 to encrypt the connection to the API.

Unique identifiers for switch user groups or queues. If specified, Capture Verification only collects CDRs for calls or meetings with a participant that is part of one or more of the listed groups or queues.

You can add multiple group or queue IDs by entering multiple values separated with a comma and selecting Apply, or you can add multiple values one by one. You can edit or delete values using the buttons under Actions.

Method of uniquely identifying the Kinesis stream.

• Stream ARN: Use the Amazon resource name (ARN) of the Kinesis stream.

  The stream ARN is a universally unique identifier (UUID) across AWS.

• Stream name only: Use the name of the Kinesis stream.

  The stream name is only unique to an AWS account and region, so you can have more than one Kinesis streams with the same name associated with the same AWS account, as long as they are in different regions.

Unique identifier for the Amazon Kinesis stream.

Enter the value in the format required by the selected Stream identification method. For example:

• Using the stream ARN, enter arn:aws:kinesis:us-east-2:123456789012:stream/mystream.

• Using the stream name, enter mystream.

Region hosting the call center.

To set the region, either select a pre-defined region from the list, or enter a custom region. If specifying a custom region, only enter the region code, not the region name. For example, for the region with the name Europe (Frankfurt), enter the region code, eu-central-1.

Method of authenticating the Identity and Access Management (IAM) user the Collector uses to access AWS.

• Access key: Use an access key to authenticate the IAM user.

• IAM role: Use a role to authenticate the IAM user.

Access key ID for the IAM user in AWS.

Only available if the Authentication method is Access key.

Access key secret for the IAM user in AWS.

Only available if the Authentication method is Access key.

Amazon resource name (ARN) that uniquely identifies the role of the IAM user.

Only available if the Authentication method is IAM role.

Name that uniquely identifies the IAM role session.

Only available if the Authentication method is IAM role.

External ID used in the IAM role trust policy.

Only available if the Authentication method is IAM role.

When selected, the Collector connects to the switch data source API through a proxy server.

IP address or Fully Qualified Domain Name (FQDN) for the proxy server.

Only available if Use proxy server for API connection is selected.

Port number that the Collector uses to connect to the proxy server.

Only available if Use proxy server for API connection is selected.

User name for the account that the Collector uses to connect to the proxy server.

Only available if Use proxy server for API connection is selected.

Password for the account that the Collector uses to connect to the proxy server.

Only available if Use proxy server for API connection is selected.

Length of time leading up to the most recent CDR collection during which the delayed collection gathers CDRs.

Collectors for Genesys PureEngage integrations run multiple separate collection cycles. As CDR records of long and ongoing calls can be made available by the switch after the default collection, a delayed collection cycle runs in parallel to the default collection cycle to gather these CDRs. The delayed collection cycle runs as a sweep of a broader time range leading up to the most recent default collection cycle. The polling frequency of the delayed collection is different to the default collection, as it only runs again if the same amount of time has passed as its collection time range.

The minimum value is 05:00 (5 minutes) and the maximum is 360:00 (6 hours).

Format:

mm:ss

Time period by which a secondary, deferred collection cycle is delayed in time.

Collectors for Genesys PureEngage integrations run multiple separate collection cycles. As CDR records of long and ongoing calls can be made available by the switch after the default collection, a deferred collection cycle runs in parallel to the default collection cycle to gather these CDRs. The polling frequencies of the deferred and default collections are identical, but the deferred collection runs a configurable time interval later.

The minimum value is 01:00 (1 hour), and the maximum value is 120:00 (5 days).

Format:

hh:mm

If selected, Capture Verification deletes CDR data copied from the switch after processing the data.

If selected, Capture Verification moves the CDR data copied from the switch to a specified destination after processing.

Destination for CDR files copied from the switch when Move processed files to is selected.

The time span before the request to the switch data source API times out.

Format:

mm:ss

Adds a time delay between attempts to connect to the switch data source API.

The maximum number of retries the Collector carries out before the attempt to connect to the switch data source API fails.

The number of CDR records the switch data source API returns in response to a request.

The length of time to keep cached data received from the switch data source API before removing from memory. Applies to individual data records in the cache.

• For Genesys PureEngage Collectors, this parameter applies to the caching of user login and group IDs required for the filtering of CDRs by groups.

• For Genesys CX API Collectors, this parameter applies to the caching of user login data required for call matching.

• For Unigy Blue Wave API Collectors, this parameter applies to the caching of user and Line Resource Address of Record (AOR) data required for call matching. As long as a data record in the cache exists in the switch environment, its cache lifetime is reset to the value configured by this parameter when the daily cache synchronization runs, and the data record is kept in memory.

• For Zoom Phone API Collectors, this parameter applies to the caching of user email data required for CDR collection. The cache lifetime cannot be reset, and the data record is removed from memory after the period configured by this parameter.

Time of day when the Collector refreshes its cached data received from the switch data source API.

• For Unigy Blue Wave API Collectors, this parameter applies to the Line Resource Address of Record (AOR) values required for call matching. Capture Verification requests the list of Line Resource AOR values configured in the Unigy environment when the Collector is enabled. Further newly configured Line Resource AOR values are read once a day at the time set in the Daily cache refresh time parameter.

  Calls made on devices with Line Resource AORs configured after the latest cache synchronization are categorized as Not recorded until Capture Verification caches the new Line Resource AORs in the next synchronization process. Depending on the value of the Daily cache refresh time parameter, this state can last up to 24 hours.

• For Genesys CX API Collectors, this parameter applies to the user login data required for call matching.

Format:

hh:mm

Length of time to cache the CDR data of ongoing calls received from the TradeSense WBA before removing from memory and processing.

Format:

d.hh:mm:ss

Length of time between Capture Verification checks to see if ongoing calls have completed.

Format:

d.hh:mm:ss

Adds a time delay to the collection of CDR data to avoid a mismatch with recording data.

As soon as Capture Verification collects CDR data for a call segment, it attempts to match the CDR data to recording data. If recording data for the call segment is still being processed, the Collector is not able to match the CDR to recording data and logs an issue. A time delay added to the collection of CDR data allows for recording data to become available, reducing the number of false issues.

Format:

d.hh:mm

Tolerance Capture Verification uses when matching call data to recording data or recording data to call data.

Format:

mm:ss

If time offset is set to 10 seconds (00:10), Capture Verification searches for corresponding call or recording data that starts or ends at the same time, plus or minus 10 seconds.

Collector polling frequency.

Local and SFTP Collectors actively poll the data source for data. Read delay is the time between polls.

Maximum page size (number of rows) a Collector reads from a data source in a single query.

Setting a maximum ensures that not all data is loaded at the same time. Loading large amounts of data could cause an unresponsive state due to connection or memory issues.

Earliest point in time that Capture Verification matches call data to recording data.

Format:

d.hh:mm:ss

CDR definition to use when processing CDR files collected from the switch data source.

The Collector can be configured to process non-standard CDR formats for Avaya Aura switch data sources. The format of the CDR file can be defined in a JSON file, which is uploaded to Capture Verification to create a CDR definition. A CDR definition can be assigned to one or more Collectors.

Opens the Manage CDR definitions menu to create, edit, or delete CDR definitions.

If selected, Capture Verification saves the unprocessed CDR data copied from the switch to the Automated Verification database with the processed data.

The list of email domains that are exempt from redaction.

The user emails of all Zoom meeting participants are redacted in Capture Verification, unless their email domain is on the whitelist. If no domains are configured, Capture Verification does not redact any user emails.

You can add multiple domains by entering multiple values separated with a comma and selecting Apply, or you can add multiple values one by one. You can edit or delete values using the buttons under Actions.

Example:  

If verint.com is added to the whitelist, a meeting between john.smith@company.com and jane.doe@verint.com shows the participants as da90ec85061e416d@company.com and jane.doe@verint.com.