Communication Recording Agent MS Teams Technical Guidelines
Version 1.5
This topic is aimed at customer System Administrators to provide a technical overview of the Communication Recording Agent integration for Microsoft Teams. It’s designed to help System Administrators manage and maintain a Uniphore/MS Teams system and to provide relevant Azure/MS Teams/Communication Recording Agent configuration that can be performed by a suitably qualified administrator/engineer. For system deployment details specific to your environment, please refer to your Solution Design Document from Uniphore.
Note
For Installation and Support Engineers, please refer to the full MS Teams Integration Guidelines topic for installation and configuration details.
New in this Topic
Version 1.1 of this Technical Guidelines topic contains the following general updates:
Architecture, specifications, and requirements all updated for the latest release.
MS Teams/Azure pre-reqs and configuration guidelines have been added/updated.
Additional limitation added regarding the Microsoft Prevent Toll Bypass calling policy.
For U-Capture upgrades (that have an existing MS Teams integration), no configuration changes are required for the integration, although you should upgrade the existing Compliance Bot to the latest version within Azure – see Upgrade the Azure Bot.
Version 1.2 of this Technical Guidelines topic contains the following general updates:
A new Azure Bot version is available – 1.12.
Changes made to reflect updated VM options.
Set API Permissions section updated.
Configuration options for appsettings.remote.json have been updated.
Version 1.3 of this Technical Guidelines topic contains the following general updates:
Call Metadata topic updated to include additional metadata captured by the Azure bot (Version 1.12 and above).
Integration Dependent Features topic updated to reflect that max concurrent channels is Azure bot size specific, as well as to specify that captured audio is stereo.
U-Capture was previously called Conversa, in this topic all instances of the "Conversa" name have been updated to U-Capture, be aware that UI and API names may not have been updated in the actual product at the time of reading.
Version 1.4 of this Technical Guidelines topic contains the following general updates:
Minor adjustments have been made throughout the topic to better align with the next generation of U-Capture.
Resiliency and Known Limitation topics updated to address duplication limitation when using multiple Collectors for resiliency.
Channel Registration topic updated to reflect maximum recorded users per Compliance Bot / Collector pair.
Version 1.5 of this Technical Guidelines topic contains the following general updates:
Descriptions added to each of the metadata fields listed in Call Metadata.
Changes have been made throughout this topic to reflect that the Core Services are no-longer used to stream captured conversation data to the Audio Connector.
Version 1.6 of this Technical Guidelines topic contains the following general updates:
U-Capture is now the Communication Recording Agent. This product name change has been made throughout the article, but may not be present in every aspect of the product at the time of reading.