Specifications and Requirements

This topic contains specifications and requirements to enable call recording for MS Teams. Only specifications relevant to this Teams integration are listed here.

Prerequisites – Customer Specific

MS Teams License

Each customer must have one of the following MS Teams license plans to enable compliance recording per user.

Microsoft 365 Tenant with Teams Enabled

Windows PowerShell 5.1

Azure Environment

An Azure Cloud Service (Extended Support) environment must be available and will be used to host the Uniphore Compliance Bot that runs as an Azure cloud service – see Cloud Service Pricing for more details. Uniphore recommends that as a minimum, Cloud Services Instance D2 v2 is available. The table below illustrates the number of channels that can be handled by D2 v2 (low specification), D3 V2 (medium specification) and D5 V2 (high specification) servers:

Cloud Services Instance	Channels
D2 v2 (low spec)	Up to 200
D3 V2 (medium spec)	Up to 750
D5 V2 (High spec)	Up to 1500

Note

The Cloud Services Instance H8m (high spec) has been removed from the table above as it is no longer under Microsoft support. D5 v2 is now the recommended high spec environment.

Azure Subscription

Also:

The Azure Subscription must be connected to the same tenant as the Microsoft 365 account.
The U-Capture / MS Teams integration also requires access to an Admin Account to complete the installation. The account must have the relevant permissions Uniphore requires to create resources and modify users in Azure Active Directory.

Agent Based Recording - User Recording Configuration

DNS CNAME Record

The CNAME requires an SSL Certificate as detailed below.

SSL Certification

The U-Capture / MS Teams integration also requires an SSL certificate for the new CNAME in the DNS.

The SSL certificate must be in .pfx file format (public and private key format) with its associated password, and must meet both the Azure Certificate Requirements and MS Teams Compliance Recording Certificate Requirements detailed in this section. Some customers have decided to use a wildcard certificate for example, *.companyname.com.

Note

Self-signed certificates do not work.

Azure Certificate Requirements

The certificate must meet the following requirements for TLS/SSL certificates in Azure:

The certificate must contain a public key.
The certificate must be created for key exchange, exportable to a Personal Information Exchange file ( .pfx file).
The certificate's subject name must match the domain used to access the cloud service.
The certificate must use a minimum of 2048-bit encryption.

For further information, see Microsoft's Azure TLS/SSL.

MS Teams Compliance Recording Certificate Requirements

The certificate must be created using a Cryptographic Service Provider, or CSP – see MS Cryptographic Service Providers for more details.

Note

Cryptography API: Next Generation (CNG) and Key Storage Provider (KSP) based certificates are not supported by the MS Teams Media Platform.

Prerequisites – Uniphore Specific

U‑Capture

In general, these integration guidelines assume that:

A U‑Capture Core Services Kubernetes cluster has been deployed.
One or more MS Teams Collectors have been deployed.
Each Collector has been provisioned with “basic configuration” to connect the Collector with the U‑Capture Core Services.

Uniphore Compliance Bot

Each customer requires at least one Uniphore Compliance Bot which sits in the Microsoft Cloud and links to the MS Teams platform using the MS Teams Communications API.

Deployment Assets

The U‑Capture / MS Teams installation requires access to the following deployment assets which are available from the Uniphore SFTP site. Further details for installation/configuration are provided in Installation and Configuration.

File Type	Description
.json	Template configuration files for the Compliance Bot.
.cspkg	The Azure Cloud Service package files for the Compliance Bot – each package represents different sizes of Cloud Service deployment.
.cscfg	The Azure Cloud Service configuration file for the Compliance Bot – templated to allow easy update.
.csdef	The Azure Cloud Service resource definition file – templated to allow easy update.

Call Recording Capabilities

Call Recording Scenarios

The following call scenarios are supported by the U‑Capture / MS Teams integration:

Basic Internal Call – A call between two MS Teams users in the same organisation.
Basic External Call – A call between an MS Teams user and MS Team user in a different organisation.
Basic Call (External PSTN User) – A call between an MS Teams user and a standard PSTN number via direct routing.
Holds – A call continues to be recorded when it’s put on hold. There is no call segmentation *
Transfers (Warm and Blind) – A call ends when it’s transferred away from an MS Teams user. If the call is transferred to another recorded MS Teams user, the call is recorded as a new call.
Conference Calls (MS Teams & PSTN) / Teams Rooms / Screen Sharing – The recorded call contains all audio for all participants in the meeting. MS Team users are recorded as they join the call, and call recording ends for them when they leave the call. *
Redirects / Forwards – A call that is forwarded to a recorded MS Teams user is recorded as a basic call. A call that is forwarded to a non-MS Teams user is not recorded.
Voicemail – The call audio and metadata is not recorded if a voicemail is left by an external user, however, retrieval of voicemail is recorded as the MS Teams user is playing the call back.
Delegated Calls – Allows an MS Teams user to have their calls answered on their behalf by another MS Teams user. For example, a manager whose calls are directed to their assistant. When someone phones the manager, both the manager’s phone and the assistant’s phone ring. Call recording is based on the MS Teams user who answers the call.
Call Parking – When a call is placed on hold by an MS Teams user on one device, and picked up on a different device. Call recording stops when the call is placed on hold, and a new call recording starts when the call is retrieved.
Federated Calls – A call between an MS Teams user and a Skype for Business user.
Call Queueing – Calls routed via a Queue to a recorded MS Teams user are captured when the call connects.

* Limitation: see Known Limitations.

Call Metadata

* Limitation: see Known Limitations.

Integration Dependent Features

U-Capture	MS Teams
Recording
Supported Media	Voice
Supported Devices	All MS Teams Supported Devices
Max Supported Channels (per Collector)	Dependent on Azure bot size (See Select Deployment Assets).
Mono/Stereo Recording	Mono/Stereo
Record Internal Calls	Y
Record Encrypted Calls	Y
Supported Codecs	PCM
Single Call Through Hold *	Y
Device Discovery	Automatic
Device Enablement *	Auto Enable *
Silence Suppression *	N
Discard Call on Silence	N
Recording Alarms	Y
U‑Capture Collector
Recommended Resiliency Model	Active/Active (2N, Parallel)
Additional Supported Resiliency Model	Active/Standby (N+1, Failover)
U‑Capture
Linked Calls	N
Blocklist	Y
Other Features
Requires CTI Feed to Record	NA

* Just to clarify a few features:

Single Call Through Hold: When a call is put on hold the recording appears as a single recording or is split into multiple calls.

Device Enablement: Indicates if new devices are automatically enabled or disabled for recording. Configurable – default is automatically enabled.

Silence Suppression: Recording of silence is suppressed.

Channel Registration

Auto detected channels are enabled by default, this is configurable – see Configure the Collector Integration Adapter.

Known Limitations

Conference Calls / Teams Rooms / Screen Sharing
Currently, only call audio and metadata is captured for Conference Calls (MS Teams and PSTN), MS Teams Rooms, and Screen Sharing calls. Metadata related to the “other party” for these call scenarios displays as “meeting/conference” – whilst this in itself does not impact the customer's ability to adhere to MiFID II requirements, system design and installation engineers may need to consider this limitation and discuss with the customer.

Teams Channels & Teams Chat
Teams channels and Teams chat are not supported in the U‑Capture / MS Teams integration as they are an Instant Messaging feature.
Linked Calls
Linked Calls are not supported in the U‑Capture / MS Teams integration, Single Call on Hold is always enabled and cannot be disabled.
Prevent Toll Bypass
Microsoft have a calling policy that can be applied to users called Prevent toll bypass and send calls through the PSTN (i.e. Location Based Routing). This can be found through the Microsoft Teams admin center under Voice | Calling policies . Microsoft state:
“It is expected that compliance recording will be turned off for a user if they are enabled for Location Based Routing.”
Therefore, any users that have this calling policy applied will not be recorded, even if they also have the compliance recording policy assigned.
Meetings
At the time of publishing (December 2022) Microsoft are currently working on performance improvements of meetings, which may impact recording performance for meetings.
Resiliency Duplicate Calls
When using multiple Collectors for resiliency, identical calls (duplicate) will be present in U-Capture, one call for each Collector present in the resiliency model.

Firewall Port Considerations

The following ports are required for connections to/from the Uniphore Compliance Bot:

Bot rules for the Collector:

Port	Protocol	Description
2012	TCP Inbound Only	Configured websocket/https port, 2012. Restrict to external IP addresses.

Port

Protocol

Description

2012

TCP

Inbound Only

Configured websocket/https port, 2012.
Restrict to external IP addresses.

Bot rules for MS Teams:

Port	Protocol	Description
9440, 9444-9544, 10100-10199, 20100-20199	TCP Bidirectional	Required ports for MS Teams. It is possible to limit to published Azure IPs, however in our experience, these lists are frequently changing and/or have omissions, therefore not recommended.

Port

Protocol

Description

9440,

9444-9544,

10100-10199,

20100-20199

TCP

Bidirectional

Required ports for MS Teams.
It is possible to limit to published Azure IPs, however in our experience, these lists are frequently changing and/or have omissions, therefore not recommended.

General:

Port	Protocol	Description
443	TCP Bidirectional	Secure connection between Azure and the Collector (The U-Capture / MS Teams integration requires port 443 to be open between Azure and the Collector).

Port

Protocol

Description

443

TCP

Bidirectional

Secure connection between Azure and the Collector (The U-Capture / MS Teams integration requires port 443 to be open between Azure and the Collector).

Tested Configuration

Integration testing of a basic interop between Teams and U‑Capture (Teams Compliance Bot 1.12 and U‑Capture Core Services) has been completed using Teams Desktop App v1.5.00.31117, Teams Web (Chrome v107.0.5304.107), and Teams on IOS (4.19.0).

In this section:

Uniphore Customer Portal

Specifications and Requirements

Prerequisites – Customer Specific

MS Teams License

Note

Microsoft 365 Tenant with Teams Enabled

Windows PowerShell 5.1

Azure Environment

Note

Azure Subscription

Agent Based Recording - User Recording Configuration

DNS CNAME Record

SSL Certification

Note

Note

Prerequisites – Uniphore Specific

U‑Capture

Uniphore Compliance Bot

Deployment Assets

Call Recording Capabilities

Call Recording Scenarios

Call Metadata

Integration Dependent Features

Channel Registration

Known Limitations

Firewall Port Considerations

Tested Configuration

Search results