In order to complete the steps below, you must have System Administrator role in Verba. 

The registration consists of the following steps:

Recording architecture

The following diagrams shows the connections in a highly available Microsoft Teams IM recording environment when using the Webhook/DLP API (left), and Export API (right).

File queue setup for failover and load-balancing

In the case of the Webhook/DLP API, only one of the Recording Director components is writing into the file queues at once, depending on which one receives the events from the Application Gateway. In the case of the Export API however, the Recording Director components distribute the user list amongs each other equally, and only query the chats of their own portion of the user list.

The "Number of Receiving Queues Owned by Director Role" setting has to be the same on all Recording Director servers. This setting has to be the same as the total Media Recorder cores (without redundancy) multiplied by two.

Number of Receiving Queues Owned by Director Role = Total Recording Server cores * 2

The Media Recorder component works the same way reagrdless of the API being used. In the service configuration, the "Number of Processing Queues Owned by Recorder Role" setting has to be specified, and it has to be the same on all the Recording (Media Recorder) servers. This setting is always equals to the number of CPU cores of the individual Recording (Media Recorder) servers multiplied by two.

Number of Processing Queues Owned by Recorder Role = Individual Recording Server cores * 2

For example, if there are two 4-cores Recording Servers, then the "

Number of Processing Queues Owned by Recorder Role

When there is no load-balancing (1+1 servers), then the "Number of Processing Queues Owned by Recorder Role" configuration will be equal to the total number of file queues. When load-balancing is being used (N+1), the file queues have to be distributed between the (active or N) Media Recorders, so the "Number of Processing Queues Owned by Recorder Role" configuration will be the quantity of the file queues divided by the quantity of the (active or N) recorders.

In the case of N+1 setup, an extra Media Recorder has to be added. When a Media Recorder (N) is started, it will pick up X queues depending on its "Number of Processing Queues Owned by Recorder Role" configuration. When the last Media Recorder (+1) is starting up, all the file queues will be taken already, so the last recorder will be the standby recorder. If a Media Recorder goes down, the standby recorder picks up its queues, and becomes an active recorder. When the Media Recorder comes back, it will be the new standby recorder.

Configuration

Prerequisites

Assigning a Public IP Address (Webhook/DLP API only)

For a single non-HA setup, the Recording Server (Recording Director) needs to have a public IP address. In the case of a highly-available setup, the public IP address has to be assigned to the loal-balacer.

Creating an App Registration in Azure

Before configuring the Verba Recording Server(s) for Microsoft Teams Chat recording, an App Registration has to be created in Azure. For the configuration steps, see: 

Registering an App for Mirosoft Teams Chat Recording in Azure

Creating the File Queue folder

A root folder has to be created for the processing queues. In the case of a single-recorder setup, this folder can be created on the local disk of the server (recommended path: [APPLICAION_FOLDER]\media\processing_queue). In the case of a HA setup, the processing queue folder cannot be created on the local disk of the Recording Server. Instead, it has to be created on a seperate network location accessible from all servers.

Assigning Certificates

(Webhook/DLP API only, optional)

The connection encryption certificate can be both publicly signed or locally generated. Only CSP certificates are supported (CNG/KSP certificates are not supported). The SAN configuration of the certificate must include the public address of the Recording Server, or the load-balancer in the case of multiple Recording Servers. Using asterisk in the SAN is accepted. The private key of the certificate has to be exportable.

Configuring

Microsoft Teams Chat Recording with Webhook/DLP API

The configrauin steps of the single-recorder setup for the Webhook/DLP API can be found here:

 Configuring the Verba Unified IM Recorder Service for Microsoft Teams Chat Recording

Configuring Microsoft Teams Chat Recording with Export API

The configrauin steps for the Export API can be found here:

Configuring the Verba Unified IM Recorder Service for Microsoft Teams Chat Recording with Export API

Configuring

Separated Recording Director and Media Recorder roles

In the case of the Webhook/DLP API, it is possible to separate the recorder roles. The following configuration steps needs to be done when the Recording Director and the Media Recorder roles are separated:

Step 1 - Configuring the Verba Unified IM Recorder Service on the Recording Director Servers

Step 2 - Configuring the Verba Unified IM Recorder Service on the Media Recorder Servers

Co-located Recording Directors and Media Recorders in a highly available setup

Alternatively, the Recording Director and the Media Recorder servers can be co-located. In this case, do the single-recorder setup for each servers, but use the file queues on the network location instead of creating them on the local disks, and use the common certificate for the Teams connections.

Image Removed