BT Trading Enterprise integration with Capture Verification

For customers with BT Trading Enterprise (formerly IPTrade), Capture Verification verifies calls recorded by a recorder product against BT Trading Enterprise Call Detail Records (CDRs).

Capture Verification uses its Collector to connect to the BT TradeSense Websocket Backend API (WBA) and collect CDRs from the BT Trading Enterprise environment so that it can verify recordings against the CDRs.

BT Trading Enterprise integration diagram

BT Trading Enterprise turrets are configured to send their events that form the CDRs to TradeSense. The Collector connects to the TradeSense WBA through a secure websocket connection using the API user token generated in TradeSense, and requests the CDRs by regular polling.

Multiple Collectors can be configured for a single BT Trading Enterprise (formerly IPTrade) switch data source in Capture Verification. Due to a limitation in TradeSense, the maximum number of traders supported on a single TradeSense server is 200. If the number of traders configured in the BT Trading Enterprise deployment and associated with the data source exceeds 200, multiple Collectors must be configured for the data source in Capture Verification, with each Collector connecting to a separate TradeSense server.

Support for multiple Collectors and TradeSense endpoints requires Automated Verification Database hotfix KB227003 or higher.

In high-availability TradeSense server setups where CDR data is duplicated, both the primary and secondary TradeSense endpoints can be configured for a Collector.

Only configure separate primary and secondary TradeSense servers for a single Collector if they are in a high-availability pair and they provide duplicates of the same CDR data. If you have multiple TradeSense servers that have different traders configured and provide different CDR data, configure separate Collectors for each TradeSense server.