In order to complete the steps below, you must have System Administrator role in Verba.
The registration consists of the following steps:
Table of Contents
The following diagram shows the connections in a highly available Microsoft Teams IM recording environment.
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.
Highly available setup with load-balancing:
Highly available setup without load-balancing:
Assigning a Public IP Address
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:
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.
If there are multiple Recording Servers, a common certificate is required for the Azure connection. The certificate needs to have an exportable private key. Besides the private key, there is not other requirement for the certificate. The certificate has to be added to the Certificate Store of all the Recording ServersA publicly signed certificate is required. 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 a single-recorder setup
The configrauin steps of the single-recorder setup can be found here:
Configuring a highly-available setup
The following configuration steps needs to be done when the Recording Director and the Media Recorder roles are separated:
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.