6. Redundant MS Teams Call Recording

Eventide Communications also provides a redundant solution for NexLog DX Ms Teams Recording. To ensure calls are always recorded even if a recorder were to become unavailable for any reason, it is recommended that a second recorder be installed in a separate location and configured to simultaneously record MS Teams calls. This primary and secondary solution implementation approach ensures access to recorded calls even if one of two recorders suffers a failure or if there is an network issue that prevents access to a single recorder. This approach also provides redundancy for the SaaS NTRS, which is a fundamental component of the NexLog DX MS Teams Recording solution.

On a rudimentary level, redundant MS Teams Call Recording requires having two NexLog DX and two NTRS. Compliant Recording Applications (the NTRS in this case) have the ability to be paired with another, enabling them to be under the same compliance policy.

Since multiple compliance policies cannot be put into effect at the same time, we achieve redundancy by pairing two NTRS. When assigning the paired NTRS to a compliance policy, the compliance policy will know to have both NTRS record the call.

Each NTRS will also store the recordings separately in addition to sending it to different NexLog DX, thereby creating true redundancy.

6.1. Creating and Pairing Compliant Recording Applications

In order to pair Compliance Recording Applications to each other, we must first have both Compliance Recording Applications created.

Once that is done please run the following command:

Get-CsTeamsComplianceRecordingApplication

Please take note of both the Identity and Object ID values of both applications. These will be needed for the next command.

Identity

Full identity of the application. This includes the Tag:policy_name. Format: Tag:policy_name/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Object Id

Strictly the unique identifier of the application. Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Please determine which compliance policy you would like to assign to your user. Whichever application that compliance policy is tied to will go into the Identity parameter.

The secondary application will be inserted into the Id parameter.

Set-CsTeamsComplianceRecordingApplication -Identity <Identity> -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id <Object Id>)

Example:

Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:my-recording-app/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx')

6.2. Configuring Both Nexlog DX

Now that both NTRS are recording, each recorder will need to connect to each NTRS’ storage.

Eventide Communications will provide the credentials for both NTRS that you will input into each NexLog DX MS Teams Recording Template.