O2
Mobile Recording from O2 is a next generation mobile voice recording (MVR) solution that captures calls and text messages made and received on any mobile device regardless of operating system.
O2 MVR can be delivered as a hosted on premise or hybrid solution. For more information on the O2 solution, please refer to the O2 website at https://www.o2.co.uk/business/why-o2/customer-stories/mvr
Verba directly imports O2 recordings via secure connection and depending on the value of the Polling Lag will run behind the current time a certain number of hours or minutes. This is to allow current calls to finish recording before import.
For a general description of Verba Import sources, please refer to Import sources.
Recording is supported for the following modalities:
Voice
Creating an O2 import source
Follow the steps below to create a new Verba Import source for O2:
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 the source across the system. |
Type | Select O2. |
Service URL | Mandatory. Must be provided by O2/customer. Typically https://mr.o2.com/player/ - note trailing backslash is mandatory. |
Liquid Account Id | Mandatory. Must be provided by O2/customer. Id of the Liquid Account with access to O2 recordings |
Solution Instance Id | Mandatory. Must be provided by O2/customer. Solution Instance Id of the Liquid Account with access to O2 recordings |
User | Mandatory. Liquid Account Username. Must be provided by O2/customer. |
Password | Mandatory. Liquid Account Password. Must be provided by O2/customer. |
Polling Lag | Mandatory. Number of seconds import runs behind current time. Typical lag is 15 minutes. |
End Timestamp | Mandatory. The earliest recording time to import from. |
Step 4 - Click Save to save the settings
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 |
O2 metadata
The system captures the following metadata specific to O2 recordings. These fields are available through the standard metadata template only and only those fields listed are available.
Metadata Field | Description |
|---|---|
Start Date | Recording Start Date |
Start Time | Recording Start Time |
End Date | Recording End Date |
End Time | Recording End Time |
Duration | Recording Duration |
From | Subscriber / Third Party Phone number |
From (Verba) | Verba user name associated with the From Number |
To | Subscriber / Third Party phone number |
To (Verba) | Verba user name associated with the To number |
Direction | Call Direction |
Direction (User) | Call Direction from user perspective |
From (Verba) | Verba user name associated with calling party |
To (Verba) | Verba user associated with called party |
Source Platform | O2 |
Conversation Type | Voice |
Record Type | Standard |
O2 Retry Capability
The O2 import source can retry ingestion if required. Add empty files to the directory Program Files\Verba\work\cdrimport\retryBuffer_policyId_importSourceId with the same name as the O2 Id (no file extension).
Once added, the file is automatically removed from the retry buffer when the import runs, but is automatically added back if there is any issue.