Skip to main content

Uniphore Customer Portal

Specifications and Requirements
Prerequisites – Customer Specific

The following Microsoft Teams and Azure components are required for the U-Capture/MS Teams integration.

Note

These are pre-requisites required for installation, but are listed here for reference and general information.

MS Teams License

You 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
Azure Subscription
Agent Based Recording - User Recording Configuration
DNS CNAME Record

The U‑Capture / MS Teams integration requires a new CNAME to be created in your DNS. During the installation, the DNS CNAME will be mapped from the public DNS to the Uniphore Compliance Bot running as an Azure cloud service – for example, recordingbot.companyname.com, botname.cloudapp.net.

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 below.

Prerequisites – Uniphore Specific (U-Capture)

In general, there are no additional U‑Capture system requirements specific to a Microsoft Teams integration.

Call Recording Capabilities
Call Recording Scenarios

* Limitation: see Known Limitations.

Call Metadata

* Limitation: see Known Limitations.

Integration Dependent Features
Channel Registration

Auto detected channels are enabled by default, this is a configurable option during install.

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” – you may need to consider this limitation during your capability evaluation.

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.

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.

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).

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).