CDR and Archived Content Importer settings

General

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Wait Time Between Query Cycles [sec]

If the schedule is set to No Schedule at any of the settings, this setting defines the time interval between the runs.

Internal Domain, Numbers Pattern

A regular expression that defines the internal phone numbers or phone number ranges to accurately identify the direction of the recorded calls. For example: 842|844|846

In multi-tenant environments, if an internal pattern regular expression is defined in both the environment and CDR and Archived Content Importer configuration, the pattern specified in the environment configuration is used to determine the internal values, not the pattern defined in the CDR and Archived Content Importer configuration.

Create IM Transcript FilesYes/No

CDR Import

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Cisco CDR Column Filters

Sets which CDR records should be excluded from the CDR Import. Column names and values can be provided in "column_name:value" format, on at each line. The value is a regex.

Cisco External Device/IP CriteriaDevices to be excluded from the Cisco CDR Reconciliation can be provided in this setting with a regex, so they won't be recognized as a recorded party, even if their extension is added as recorded in the Verba extension list.
SfB UserAgent FiltersSkype for Business User Agent Filters
Import ScheduleSets the schedule of the CDR Import. The configuration can be changed by clicking on the icon, then following the wizard in the right panel.
Wait Time for Recorder's CDR [sec]The CDR Reconciliation won't check the calls which are not older than the time specified in this setting.
Recheck ScheduleSets the schedule of the CDR Import Recheck. The configuration can be changed by clicking on the icon, then following the wizard in the right panel.
Number of Days to Recheck Imported RecordsSet the number of days to recheck in case of CDR Import Recheck.

Microsoft Teams IM

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

API Version

For example: v1.0

Graph Api UrlFor example: graph.microsoft.com

Cloud9 Recording System API

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Audio Transcoder Profile

Audio Transcoder Profile, such as 16 bit PCM in wav, Speex (CELP) in Ogg with silence suppression, Opus in Ogg, etc.

Cloud9 Call Data API

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Maximum Query Page Size

Default: 500

Query Interval [seconds]Default: 60
Work FolderLocation of temporary data. If not set, the default is: {Verba path}\work\cdrimport\cloud9calldata
Cloud9 Call Data API URLDefault: https://calldataapi.xhoot.com:443
Cloud9 Call Data API Metadata EndpointDefault: /v1/calls/metadata
Cloud9 Call Data API Recordings EndpointDefault: /v1/calls/recordings
Delete Metadata from Local Cache After [hours]Default: 72 (3 days)
Delete Media from Local Cache After [hours]Default: 72 (3 days)
Initial Query Look Back [days]Default: 14 (2 weeks)
Minimum Available DiskSpace [MB]Default: 500. Alert is raised if disc space is less than this setting.
Enable User FilteringDefault: No
Metadata and Media Query Intervals (minutes)Default: 240 (4 hours)
Query Start Time Compensation for Verba/C9 Time Drift (seconds)Default: 90
Enable Media Filtering WorkaroundUse end time as Call Detail Record create time. Default: Yes

Microsoft Azure Storage

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Connection timeout (ms)

Default: 300000 (5 minutes)

TLS Key password
TLS Key file
TLS Certificate
TLS CA Certificate
Forward Proxy Address
Forward Proxy Port
Forward Proxy Username
Forward Proxy Password

Zoom Phones

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

API Lookback safety margin for imports in minutesExtend the query interval backward in time this much before the last seen import. Phones APIs can not be queried by archiving time, and calls might not end in the order they are archived. This parameter makes sure no calls are missed because of that. Set to the expected maximum time it takes for Zoom to archive a call. Smaller values increase the risk a call might be missed, larger values slightly increase API load.  
Worker Thread CountThe maximum number of (per policy) threads to parallelly download media. If set higher than the thread count of the underlying server's CPU, will limit to thread count. Low values like 1 will make download slightly less efficient. High values (4+) will not increase download speed as its fundamentally limited by bandwidth, not threads. Recommended values: 2 - 8
Give Up Timeout In MinutesMinutes of time after which the service will abandon a failed import's daily re-try attempt. 1440 minutes = 1 day. Set to less than minimum of Zoom side archiving retention or meetings and phones calls, but more than 2 days. Recommended values 5,760 (4 days) - 14,400 (10 days)
Working DirectoryWorking Directory
Zoom Api Remaining Rate-Limit
Threshold For Alerting
Number or remaining Zoom API calls in the daily limited APIs before a warning alert is sent. Recommended to set to a value that will warn you in time to take actions, 10%-30% of your total daily limit (please note this config should NOT be set to percent, but absolute value). If daily API limit is reached, import will continue from next day and no data will be lost. If daily limit is reached every day, data loss eventually will.
Reconciliation delay
behind Import in minutes
Time in minutes that needs to pass between an interaction's end and its import's current progress for reconciliation to consider it. In other words: Reconciliation ignores everything that ended after import's current progress minus this value in minutes. It prevents reconciliation from producing false positives by processing events before they get archived by Zoom. Should be set to the lowest value possible that is strictly bigger than the time it takes for Zoom to archive an interaction. Too low value causes false positive alerts, too high value causes slow reaction of reconciliation for true positive cases. Recommended values: 15 - 90

Zoom Meetings

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Maximum Number Of Entries To Import

Maximum number of meetings archiving / meeting logs to paginate in a single import interval. It does not affect the number of imports in an import cycle (single run of the policy), it only limits memory use. Low values will make API use inefficient, very high values will cause high memory use and potentially timeouts. Recommended values are 300 - 3000.

Worker Thread CountThe maximum number of (per policy) threads to parallelly download media. If set higher than the thread count of the underlying server's CPU, will limit to thread count. Low values like 1 will make download slightly less efficient. High values (4+) will not increase download speed as its fundamentally limited by bandwidth, not threads. Recommended values: 2 - 8
Give Up Timeout In MinutesMinutes of time after which the service will abandon a failed import's daily re-try attempt. 1440 minutes = 1 day. Set to less than minimum of Zoom side archiving retention or meetings and phones calls, but more than 2 days. Recommended values 5,760 (4 days) - 14,400 (10 days)
Working DirectoryWorking Directory
Zoom Api Remaining Rate-Limit Threshold For AlertingNumber or remaining Zoom API calls in the daily limited APIs before a warning alert is sent. Recommended to set to a value that will warn you in time to take actions, 10%-30% of your total daily limit (please note this config should NOT be set to percent, but absolute value). If daily API limit is reached, import will continue from next day and no data will be lost. If daily limit is reached every day, data loss eventually will.
Reconciliation delay behind Import in minutesTime in minutes, that needs to pass between an interaction's end and its import's current progress for reconciliation to consider it. In other words: Reconciliation ignores everything that ended after import's current progress, minus this value in minutes. It prevents reconciliation from producing false positives by processing events before they get archived by Zoom. Should be set to the lowest value possible that is strictly bigger than the time it takes for Zoom to archive an interaction. Too low value causes false positive alerts, too high value causes slow reaction of reconciliation for true positive cases. Recommended values: 15 - 90
Participant Cache TTL (minutes)Participant Cache TTL (minutes)

Verint Ingestion

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Remove Trailing Mac Address from extensions

Default: No

Delete Metadata from Local Cache After [minutes]Default: 1440 (one day)
Sleep Time Between Metadata Cleanups for Local Cache [minutes]Default: 60 (one hour)

Cisco Webex Teams

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Maximum number of events per cycle

Limits how many Cisco Webex Teams events can the service process per import cycle. These events can be message events or leave/join events. Minimum value for this setting is 100, maximum is 1000.

User Cache TTL (hours)Default: 24
Room Cache TTL (hours)Default: 24
Participant Cache TTL (hours)Default: 6

Generic Import

The following table provides detailed instructions on each configuration setting:

Configuration Parameter Name

Description

Maximum metadata file size [MB]

Sets the maximum valid metadata size. Default: 100

Use given URL only to find media filesThis setting has an effect when a media URL provided in the input file is not pointing directly to the location of the media file. If No is set (default), then further searches are performed in the subdirectories for the media file. To speed up the processing of csv files that have incorrect media URLs or does not have any media file given, set this to Yes. In this case, the service does not perform additional searches for the missing media files.