| Available in version 9.3 and later |
|---|
This page guides the users through the configuration of a Bloomberg Vault service as a Storage Target in the system.
Bloomberg Vault is a cloud-based information management service that delivers compliance, eDiscovery, and enterprise, archiving by leveraging the scalability and reliability of Bloomberg’s global infrastructure.
Organizations use Bloomberg Vault to manage and archive a broad range of enterprise communications and collaboration data, including email, instant message (IM), mobile, files, voice data and social media.
The SaaS solution provides information governance and information analytics solutions, including enterprise archiving, surveillance, eDiscovery, trade reconstruction and data analytics.
For a general description of storage targets, please refer to Storage and export targets.
Please refer to the official Bloomberg Vault guide to configure the cloud service.
| Supported Data Management Policies | Advanced Export |
|---|---|
| Supported Record Types / Modalities | Voice |
The export of conversation transcripts is supported for Bloomberg Vault voice integrations. The transcripts are converted to the format used by Bloomberg Vault.
Reconciliation
The Bloomberg Vault platform has a reconciliation feature which indicates if an uploaded record was successfully processed and ingested into the archive or not.
The reconciliation process can take up to 2 hours, it is not an instantaneous process. The export job only marks the export successful for a record when the Bloomberg Vault successfully reconciled the uploaded file.
The Bloomberg Vault generates a response XML with the processed media file hashes. If this is not a match with Verba media file hashes the Verba Storage Service will re-try the upload. This re-try can only occur 5 times after this the Verba Storage Service will log that the upload as failed and it will start the (5) tries again in the export task's next schedule time. Also, after 5 failed upload tries the Bloomberg Vault creates an alert and the Bloomberg staff will investigate what caused the failure on their side.
Due to the reconciliation feature in Bloomberg Vault, the system caches the exported files on the local disk of the Media Repository until the Bloomberg Vault system processes the uploads. It is recommended to allocate at least the size of the total export as free space always available for the system.
Creating a Bloomberg Vault: Voice target
Follow the steps below to create a new Verba Storage target for Bloomberg Vault:
Step 1 - Open the Verba Web interface then select Data > Storage targets from the top menu.
Step 2 - Click on Add New Storage Target
Step 3 - Fill in the configuration form according to the requirements in the following table.
| Configuration item | Description |
|---|---|
| Name | Name your storage target. This name will identify this target across the system. |
| Type | Select Bloomberg Vault: Voice |
| SFTP Server | IP address or hostname or FQDN of the SFTP server |
| Port | SFTP Port |
| SFTP User | Login name |
| SFTP Password | Login password |
| SFTP Custom ID | The custom ID received from Bloomberg Vault. This helps Bloomberg distinguish ingested media records from different vendors/applications. |
Step 4 - Click Save to save the settings
After this point, the Storage target is available for use by other VFC components (e.g. Data management policies).
CDR Metadata Mapping
Bloomberg Vault ingests voice recording metadata in a specific set of fields set out by its XML schema. The fields can be populated with the values of different VFC CDR metadata fields, depending on the call scenario.
| Bloomberg Metadata Field | Bloomberg Metadata Field Description | Value or VFC CDR Field |
|---|---|---|
| CallID | A unique identifier for the call recording. | The value of the CdrId field, but hyphens are replaced by underscores. Example: ca7307ab_a00c_11ee_837b_005056c00008 |
| ChannelNumber | The number for the channel on which the call was recorded. | The value is always 0. |
| Direction | The direction of the call from the perspective of the recording party. Possible values:
| The value is set to:
|
| CLI | The calling line identifier. | Empty for outbound calls, otherwise it is the value of the SourceCallerId field. |
| StartTime | The time at which the call recording begins. | The value of the StartTime field. |
| StopTime | The time at which the call recording ends. | The value of the EndTime field. |
| CallDuration | The length of the call. | The value of the EndTime field minus the value of the StartTime field, in the format PnYnMnDTnHnMnS. Example: P0Y0M0DT0H15M2.000S |
| TraderID | The Trader ID for the person logged into the turret (turrets only). | The value of the AgentId field. Note: AgentID is called UserId on the user interface. |
| TraderName | The name of the trader associated with the Trader ID. | This field can be populated by different VFC metadata fields depending on the available metadata or the call scenario, in the following order of priority:
|
| POSerialNumber | The unique serial number of the turret device. | If the direction is Outbound, the value of the SourceDevice field. If the direction is Inbound, it is set to the value of the DestinationDevice field. |
| NameOfLine | The speed dial name or number for outbound calls. | The value of the DestinationName field. If the DestinationName field is empty, it is set to the value of the DestinationCallerId field. |
| NameOfCaller | The name of the caller for inbound calls, if available. | If the direction is Inbound, the value of the SourceName field, otherwise empty. |
| Device | The phone device used to make the call: left handset(LHS), right handset(RHS), or intercom (INT). | The value is set to LHS, except if the metadata template is bt-its, in which case the value depends on the value of the devicetype field in the template:
|
| DialedNumber | The dialed number for outbound calls. | If the direction is Outbound, the value of the DestinationCallerId field, otherwise empty. |
| RecSiteID | The site ID for the recording server. | The hashed value of the RecorderServerName field (location). |
| FileRef | The reference to the associated voice recording media file provided with the XML. | The Media file name. |