Overview

Vault Streams enables recorded interactions from any source to be securely stored, retained, and accessed via a single system. Custom Streams can be set up to both store recorded interactions from other systems, and also to import historical legacy recordings in the Streams module.

Where to find the Streams module:

  • Open Vault

  • Select Streams from Settings.


1. Display Streams

This feature allows you to navigate the list of available Streams in Vault.

A list of configured Streams is displayed. For each, the list displays the following details:

Column

Contents

ID

The unique identifier for the Stream

Title

The name of the stream is displayed.

Type

The data type. Currently only Call Recording is available.

Schema

The schema assigned to the Stream

Once a schema is assigned to a stream then it cannot be updated or opened until it is unassigned from that stream.

Stream key

An authorisation key for the Stream

An Options icon appears if the mouse pointer is located above a row.  If this is clicked, the following options are available:

  • Edit (Not available for a Default Stream)

  • Manage Keys

  • Delete


2. Add a new Stream

This feature is used to create and configure a new Stream.

  1. In Vault, select Streams from the Settings menu

    1. To create a new Stream, click the Create new Stream button 

  2. Enter the new Stream Name

  3. Select the Schema to be used with the Stream

  4. Click Save


3. Manage Stream Keys

This feature is used to view and rotate API Keys on an existing Stream.

  1. Open Vault.

  2. Select Streams from the Settings menu

  3. Locate the Stream from the list and click the Options icon and Select Manage Keys

  4. For a new Stream, the API keys will be empty. To generate a key, click Rotate key

  5. The user will be asked to confirm the key rotation:

  6. Once the key is rotated, a confirmation message will show briefly and the key is available to be viewed (hidden by default) and copied.

  7. If required, a second API key can be configured under API key2