BT IP Trade

BT IP Trade

Overview

The integration between the Verba and IP Trade systems is based on duplication of the media stream on the turrets or TPO side. For each call, the dealer board system creates a copy of the associated inbound and outbound RTP streams. These are sent to the voice recorder server which records and archives the streams. The transmission of call detail information (CDR) and the negotiation of the RTP session parameters are performed using an XML protocol co-developed by IP Trade and Verba back in 2007. The dealer boards handle special call scenarios that require special handling on the recorder side too:

  • Several calls can be active simultaneously on the dealer board, these are recorded separately

  • A dealer board can register on the IP telephony infrastructure with single or multiple directory numbers, all of these are captured

  • Call durations can vary from seconds up to several hours (e.g. open lines), all these are recorded as expected, with silence suppressed in long calls

BT IP Trade recording features

  • Certified BT IP Trade recording solution

  • 2N and N+1 recorder configurations

  • Support both turret and TPO based recording

  • Compatible with trader voice recording data model

  • Support for VAD (voice activity detection) and media segmentation for long calls

  • All types of recording mix layouts are supported

  • Support for selective recoding by configuring trader IDs as recorded extensions

  • Support for turret based playback

Version support

Switch Name & Model

IP Trade

Supported BT IP Trade Versions

5.2 or later

Supported Turret Types

All



If you are on a different version, contact your BT representative for more information.

Features not available

  • Silent monitoring only available for Media-Only records

  • Full / Always-on, Do-not-record, Never-record recording modes only (no On-demand, no Controlled)

  • Desktop Screen Capture is not available

  • Recoding Director and Media Recorders roles cannot be separated, no dynamic load balancing available

Deploying BT IP Trade Recording

The following section contains all the necessary steps for setting up a BT IP Trade recording infrastructure.

For BT IPTrade deployments, the Recording Director and Media Recorder roles cannot be split out to different servers. These 2 roles must run on the same Recording Server to avoid limitations around failover design inherit in the IP Trade recording protocol design. This means that the Recording Servers must be allocated across the turrets and there is no dynamic load balancing available.

Server Sizing

Allocating the appropriate resources to the different servers is crucial. For guidance, see Server sizing and requirements

Preparation

Make sure that all the required prerequisites are installed on each server prior to the installation.

For guidance on configuring the necessary firewall port, visit Firewall configuration for BT IP Trade recording deployments.

Installation

The following articles contain all the step for installing the various server roles:

Configuration

For configuring the Verba system for BT IP Trade recording, see Configuring IP Trade recording

BT IP Trade metadata

The system captures the following metadata specific to BT IP Trade calls when CTI messages are available. These fields are available through the standard and the IP Trade specific custom metadata template.



Metadata Field

Description

Template

Available

Turret based recording

TPO based recording

Available in
CDR-Only record

Available in
Media-Only record

Available in
CDR-Only record

Available in
Media-Only record

Start Date

Start date of the conversation

Standard

Yes

Yes

Yes

Yes

Yes

Start Time

Start time on the conversation

Standard

Yes

Yes

Yes

Yes

Yes

End Date

End date of the conversation

Standard

Yes

Yes

Yes

Yes

Yes

End Time

End time of the conversation

Standard

Yes

Yes

Yes

Yes

Yes

Duration

Length of the conversation

Standard

Yes

Yes

Yes

Yes

Yes

User

Name of the recorded user

Standard

Yes

Yes

Yes

Yes

No

From

Source phone number, SIP URI

Standard

Yes

Yes

No

Yes

No

From Info

Source display name

Standard

Yes

Yes

No

Yes

No

To

Destination phone number, SIP URI

Standard

Yes

Yes

No

Yes

No

To Info

Destination display name

Standard

Yes

Yes

No

Yes

No

Direction

Direction of the call from the system perspective, requires configuring internal number/domain patterns

Standard

Yes

Yes

No

Yes

No

Direction (User)

Direction of the call from the recorded user perspective

Standard

Yes

Yes

No

Yes

No

From (Verba)

Name of the Verba user associated with the calling party

Standard

Yes

Yes

Yes

Yes

No

To (Verba)

Name of the Verba user associated with the called party

Standard

Yes

Yes

Yes

Yes

No

Location

Hostname of the recording server

Standard

Yes

Yes

Yes

Yes

Yes

End Cause

Normal, Hold, Transfer, Conference, Device Change, From Terminated, To Terminated

Standard

Yes

Yes

Yes

Yes

Yes

Audio Codec

Audio codec of the recorded streams

Standard

Yes

No

Yes

No

Yes

Video codec

Video codec of the recorded streams

Standard

No

No

No

No

No

Platform Call ID

Unique conversation identifier received from the recorded platform

Standard

Yes

Yes

Yes

Yes

Yes

Silence Ratio

Ratio of silence in the conversation

Standard

No

No

No

No

No

Talkover Ratio

Talkover ratio of the conversation

Standard

No

No

No

No

No

Longest Silence

Length of the longest silence present in the conversation

Standard

No

No

No

No

No

User ID / Agent ID

Trader ID

Standard

Yes

Yes

Yes

Yes

No

From Device

Recorded turret ID

Standard

Yes

Yes

Yes

No

No

To Device

Recorded turret ID

Standard

Yes

Yes

Yes

No

No

Dialed Number

Original dialed number

Standard

No

No

No

No

No

From IP

IP address of the media source

Standard

Yes

Yes

Yes

No

Yes

To IP

IP address of the media source

Standard

Yes

Yes

Yes

No

Yes

From Proxy IP

IP address of the proxy server associated with the calling party

Standard

No

No

No

No

No

To Proxy IP

IP address of the proxy server associated with the called party

Standard

No

No

No

No

No

Source Platform

IPTrade

Standard

Yes

Yes

Yes

Yes

Yes

Conversation Type

Voice

Standard

Yes

Yes

Yes

Yes

Yes

Forward Reason

Forward reason for the conversation (e.g. forwarded, transferred, team call, delegated, etc.) 

Standard

No

No

No

No