Cloud9

Cloud9

Overview

Cloud 9 Technologies is a cloud communications service provider. They provide high-performance voice, messaging and collaboration services designed for the unique needs of distributed workgroups and teams. C9 Trader connects the institutional trading community with a voice and messaging solution designed especially for the financial markets. It provides a secure and compliant way to connect with your trading counterparties while eliminating the hassle and expense of legacy turret systems and private lines.

The C9 Trader application is able to record all calls in standard Ogg/Opus and M4A/AAC format.

There 2 integration options available for Cloud9:

  • The files with related metadata (JSON) can be automatically uploaded from the C9 desktops to the Verba servers using the Cloud9 Recording System API, where a configured Cloud9 import source can receive, process, and archive the data. Multiple Verba serves can be deployed and used for the import. In this case, an HTTP load balancer has to be placed in front of the servers to provide load balancing and/or failover for the uploads.

  • Cloud9 Call Data API allows downloading the recordings from the Cloud9 cloud platform and archives them in Verba. The C9 clients are initially uploading the recordings to the Cloud9 cloud platform and the Verba application is periodically checking the Call Data API for new data. C9 clients are uploading metadata and media files separately, media files are not necessarily available at the same time metadata is retrieved. The Verba system creates the CDR entry in the database after downloading the metadata record and when the media file becomes available, the record is updated in the database and the file is imported to the default media folder. An upload or move data management policy has to be configured to place the files on the storage infrastructure.

Cloud9 recording features

  • Voice recording

  • Integration options:

    • Cloud9 Call Data API

    • Cloud9 Recording System API

  • Compatible with trader voice recording data model (Cloud9 Call Data API only)

  • All types of recording mix layouts are supported

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

Version support

Switch Name & Model

Cloud9

Supported Symphony Versions

Contact Cloud9

Supported Endpoint / DeviceTypes

All

Deploying Cloud9 recording

The following section contains the necessary steps for setting up a Cloud9 recording infrastructure.

Server sizing

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

Preparation

The Cloud9 integration requires additional prerequisites and configuration in Cloud9, which out of scope for this guide. Contact your Cloud9 representative for further information.

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

Installation

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

Configuration

The system has to be configured for Cloud9 in the following way:

  • Cloud9 Recording System API based integration requires configuring the related import sources and enable the Import Service on one of the Recording Servers. For more information, see Cloud9 Recording System API.

  • Cloud9 Call Data API based integration requires configuring the related import sources and enable the Import Service on one of the Recording Servers. For more information, see Cloud9 Call Data API.

  • Recorded users can be synchronized from Active Directory. To match the imported conversations to an extension (and to a user account) you need to add the Cloud9 login names as extensions with type User / Agent ID.

Cloud9 Recording System API metadata

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

Metadata Field

Description

Template

Available

Start Date

Start date of the conversation

Standard

Yes

Start Time

Start time on the conversation

Standard

Yes

End Date

End date of the conversation

Standard

Yes

End Time

End time of the conversation

Standard

Yes

Duration

Length of the conversation

Standard

Yes

User

Name of the recorded user

Standard

Yes

From

Phone number, Button name, User name

Standard

Yes

From Info

User / contact name

Standard

Yes

To

Phone number, Button name, User name

Standard

Yes

To Info

User / contact name

Standard

Yes

Direction

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

Standard

Yes

Direction (User)

Direction of the call from the recorded user perspective

Standard

Yes

From (Verba)

Name of the Verba user associated with the calling party

Standard

Yes

To (Verba)

Name of the Verba user associated with the called party

Standard

Yes

Location

Hostname of the recording server

Standard

Yes

End Cause

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

Standard

No

Audio Codec

Audio codec of the recorded streams

Standard

No

Video codec

Video codec of the recorded streams

Standard

No

Platform Call ID

Unique conversation identifier received from the recorded platform

Standard

Yes

Silence Ratio

Ratio of silence in the conversation

Standard

No