Verba Conversation Import
- Kiss, Mate
The Conversation Import scans a given local or remote folder hierarchy for formerly exported calls with a valid Verba XML conversation detail record (CDR) file. Conversations without valid XML CDR files are discarded.
Verba Conversation Import Sizing
The Verba conversation import policy can process 14 calls every second on average. However, this is highly dependent on the file sizes and the network bandwidth.
If the network bandwidth is not holding back the import capacity, it takes up 0.2 CPU core of the server where the Import service runs.
On the SQL server side, the policy takes up 0.3 CPU core. It generates 75 IOPS with 0.7% R/W ratio. If the recording rules setting is turned off, it takes up 0.25 CPU core.
Creating a Verba Import source
Follow the steps below to create a new Verba Import source for Verba conversation data:
Step 1 - Open the Verba Web interface then select Data > Import Sources from the top menu
Step 2 - Click on the Add New Import Source link on the top right
Step 3 - Complete the configuration according to the requirements in the following table
Configuration item | Description |
|---|---|
| Name | Name your import source. This name will identify this source across the system |
| Type | Select Verba |
| Source folder | Specify the network path to the shared folder where the Verba conversations are available for import. The original Year / Month / Day folder structure is required. |
Step 4 - Click Save to save the settings
Please note that the content of the Source Folder will be deleted after the successful import. Therefore, the Source Folder cannot match any of the Verba storage targets or the media folders! It is highly recommended to create a temporary folder for the calls which has to be imported.
Import policy configuration
Follow the steps below to configure the Data Import action:
Step 1 - In the Verba web interface, navigate to Data > Data Management Policies
Step 2 - Click on the Add New Data Management Policy button at the top-right corner of the page
Step 3 - For the action, select Data Import
Step 4 - Under Available Import Sources, select the Import Source that you created, then click on the Add button just below the text field
Step 5 - Configure the policy details, based on the information that is shown in the configuration items summary table below
Step 6 - Set up how frequently the Import should be run in the Scheduling section
Step 7 - Click on Save
| Configuration Parameter Name | Description |
|---|---|
| Enable Recording Rules | Specifies if all data should be processed in the imported data set or just the records of the recorded users as configured in Verba |
| Execute Only on Selected Servers | If enabled, a specific server can be chosen that will run this policy |
Please note that the policy is executed by the Verba Import Service. To start the import, the activation and start of that service is required.
Enabling data import policy execution on servers
Step 1 - Login to the web interface with System administrator rights.
Step 2 - Navigate to the Configuration / Servers menu item and select the Media Repository server (or Single server) from the list.
Step 3 - Go to the Service Activation tab, then activate the Verba Import Service by clicking on the 
icon.
Step 4 - Save the changes by clicking on the 
icon.
Step 5 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.
Step 7 - Click on the Service Control tab.
Step 8 - Start the Verba Import Service by clicking on the 
icon.