IPC Data Exchange

IPC Data Exchange is part of the IPC Unigy 360 cloud service. IPC Data Exchange is an archiving service for Unigy 360. IPC Data Exchange offers APIs to:

  • archive external records into Unigy 360
  • download recordings from Unigy 360 for on-premise archiving

The import source implements the IPC Data Exchange REST-based download API. Each Unigy 360 tenant has a unique URL. Verba can import from multiple tenants. Security:

  • HTTPS using TLS 1.2
  • OAuth2 based authentication
  • Transmitted data is not encrypted

The records are imported as standard records because the Data Exchange API does not support the trader voice data model with separate CDR and Media records. It might result in bigger storage requirements compared to native recording where mixed recording channels are stored in an optimized format.

The Data Exchange service is offered in two options to the customer:

  • Redundant archiving: Unigy 360 continues to archive a call that has been downloaded via the API for redundancy. These calls can continue to be accessed via the Unigy 360 Cloud Services Portal.
  • Delete immediately: Unigy 360 purges the copy after confirmation of delivery of the call.


For a general description of Verba Import sources, please refer to Import sources.

Supported file format for import:

  • GSM-FR encoded audio in WAVE container

Recording is supported for the following modalities:

  • Voice

Creating an IPC Data Exchange import source

Follow the steps below to create a new Verba Import source for IPC Data Exchange: 

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
NameName your import source. This name will identify this source across the system.
TypeSelect IPC Data Exchange
Service URL A specific URL for each customer must be used to get the call list, retrieve a call and acknowledge the file has been processed
Authorization Provider URLA specific URL must be used to be authenticated and authorized to use the Data Exchange API.
Client IdOAuth client identifier
Client SecretOAuth client secret
User IdAn ID used for identifying the tenant
PasswordPassword for the user defined above
TLS Certificate File / Thumbprint

Specify the certificate file/certificate thumbprint that is being used for the IPC Data Exchange connection. If left empty then the Verba default certificate will be used

TLS Key FileSpecify the file where the certificate key is stored if not in the Windows certificate store
TLS Key File PasswordSpecify the password for the file that contains the certificate keys
TLS Trust List

Specify the list of certificates that Verba trusts from a 3rd-party connection. Available options:

    • .pem file with a list of certificates
    • comma separated certificate thumbprints
    • comma separated CA thumbprints

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
Enable Recording RulesSpecifies 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 ServersIf enabled, a specific server can be chosen that will run this policy

Extension configuration

To match the imported conversations to a Verba extension (and to a Verba User account) you need to add the IPC Data Exchange login names to Verba as extensions with type "User / Agent ID".

IPC Data Exchange metadata

The system captures the following metadata specific to IPC Data Exchange recordings. These fields are available through the standard and the IPC Data Exchange specific custom metadata template.

Metadata FieldDescriptionTemplateAvailable
Start Date StandardYes
Start Time StandardYes
End Date StandardYes
End Time StandardYes
Duration StandardYes
FromPhone number, Button name, User nameStandardYes
From InfoUser / contact nameStandardNo
ToPhone number, Button name, User nameStandardYes
To InfoUser / contact nameStandardNo
DirectionDirection of the call from the system perspective, requires configuring internal number/domain patternsStandardYes
Direction (User)Direction of the call from the recorded user perspectiveStandardYes
From (Verba)Name of the Verba user associated with the calling partyStandardYes
To (Verba)Name of the Verba user associated with the called partyStandardYes
LocationHostname of the recording serverStandardYes
End Cause StandardNo
Audio Codec StandardNo
Video codec StandardNo
Platform Call ID StandardYes
Silence Ratio StandardNo
Talkover Ratio StandardNo
Longest Silence StandardNo
User ID / Agent IDIPC Unigy Trader IDStandardYes
From Device StandardYes
To Device StandardYes
Dialed Number StandardNo
From IP StandardNo
To IP StandardNo
From Proxy IP StandardNo
To Proxy IP StandardNo
Source PlatformIPC Data ExchangeStandardYes
Conversation TypeVoiceStandardYes
Forward Reason StandardNo
Recording failed StandardNo
Media Length StandardNo
Media Error StandardNo
Voice Quality StandardYes
Record TypeStandardStandardYes
2N Source StandardNo