Integrating Microsoft Teams Rooms into Q-SYS

Q-SYS QuickStarts : Integrating Microsoft Teams Room

2 ) Automatic Camera Preset Recall (ACPR)

13m 16s

3 ) Video Freeze for NV Endpoints

1m 41s

4 ) Camera Streams to NV Series devices

2m 47s

5 ) Q-SYS Security – Introduction and Best Practices

13m 35s

6 ) Integrating Microsoft Teams Room

8m 54s

7 ) Integrating Axon C1

14m 34s

8 ) Bring Your Own Control with Q-SYS

4m 32s

9 ) Feature License Activation

4m 12s

10 ) Q-SYS Video 101 Training

0m 0s

11 ) Block Controller

19m 9s

12 ) Online Connectivity & Security Considerations

12m 37s

15 ) Dynamic Pairing

6m 38s

16 ) Core-to-Core Streaming

8m 23s

17 ) Room Combining

12m 23s

18 ) Notch Feedback Controller

4m 0s

20 ) Intro to Control Scripting

12m 30s

22 ) E-Mailer

6m 30s

Video Transcript

Integrating Microsoft Teams Rooms into Q-SYS 8m 54s
Today we’re going to show you how QSC can easily scale the Microsoft Teams Room experience into a high value space like this executive boardroom,
using an intuitive suite of resources, software innovations, and optimization tools. Let’s go over the physical components first.
First, the Teams Room “compute” device is running the Microsoft Teams Room software,
and is also connected to the Room control console—in this case, the Logitech Tap.
The Q-SYS Core is connected to this PC through a single USB cable, which delivers all of the room’s processed audio,
including the audio from the Sennheiser Team Connect Ceiling 2 microphone.
This same USB cable also delivers the conference video from the native Q-SYS PTZ cameras to the Teams compute device.
The Q-SYS Core is also delivering audio signal to the QSC SPA Series amplifier and the AcousticDesign Series loudspeakers,
as well as processing the control for all the audio, video and environmental pieces in the room.
The Q-SYS Core can also present a Room Control interface on the Logitech Tap. So in addition to all the expected Teams Room controls,
you can also provide the users with controls of the environmentals, cameras, video routing, etc., all on the same display device.
This Teams experience comes to us through resources that are available for systems running Q-SYS Designer Software v9.0 or higher.
This suite includes Q-SYS software components for Teams Room, a control license bundle, design template and a lot more.
We’ve rethought these elements to help simplify the design and deployment process for these high value spaces.
So keep a room like this in mind as we go to our computer, and look at each of these elements and how they work together to make this all possible. Nate?
Thanks Patrick. Let’s start with the “Q-SYS Control for Microsoft Teams” application, which is a standalone software that gets installed on the Microsoft Teams Room PC.
This is what allows us to push the Q-SYS UCI to the Teams Console device.
Once it’s installed, you don’t need to do anything else with it – but it’s a critical piece of this solution.
Next is the Q-SYS Feature License for Teams Room.
We’ve bundled both our Scripting Engine feature license and the UCI deployment feature license into a single SKU, to make it easier for people to deploy them together.
A Q-SYS Core needs both of these licenses active to run the Teams Room components, so we just packaged them together.
In fact, if your Core already has a scripting engine feature license and a UCI deployment feature license, you don’t need this Q-SYS for Teams feature license at all.
The only thing worth noting is that this solution also needs a Software based Dante feature license installed.
The only reason that’s not bundled in the Q-SYS for Teams license is because nearly every new Core already includes an 8 x 8 Software-based Dante license!
But if you’re installing this on an older Core, you'll need to upgrade it with a Software-based Dante license if it doesn’t have one already.
Next is the Microsoft Teams Sample Design file.
You may have used one of our Conference Sample design files in the past, but this Sample Design file for Microsoft Teams is a little different.
Its step-by-step presentation is user friendly and, more importantly, its audio signal flow and processing settings meet Microsoft Teams Room certification.
We highly recommend using this design file, but if you choose not to,
you should ensure that its signal integrity and gain structure is maintained, otherwise your design may not meet those performance expectations.
In fact, most of these components carry an exclamation mark that warns you about making any changes.
On the other hand, items marked with this less-intimidating icon may be edited based on your room’s needs, such as adding more cameras or Video Bridge outputs.
There are seven easy steps to complete.
Start off by listing whatever clever name your company has given this meeting space, followed by selecting which loudspeaker type and models you’re using in the room,
which automatically applies QSC loudspeaker voicings.
Next, input the IP address of your Sennheiser TCC2 microphone,
which you can get from the Sennheiser Control Cockpit application that you used to install that microphone panel.
Don’t forget to select the name of the TCC2 device here and the name of its Dante audio out channel, as defined by your setup of that device in the Cockpit application.
Critically, the TCC2 also needs to receive a return AEC reference channel from Q-SYS, so you’ll need to clearly label yours with a unique name here.
Once you’ve named that Dante channel, you’ll have to open your Dante Controller application
and subscribe this AEC Reference channel of the TCC2 in question to the Dante audio flow that you just named.
Step 5 is to enter the IP address of the PC that is running the Microsoft Teams Room application,
and also to select the UCI in your design that you want to be displayed within its associated control software.
By default we’ve named this “Room Controls”.
Under the hood, the “Room Controls” UCI is already linked to a new Q-SYS component called the Microsoft Teams Room Component.
This is what provides the control link between Q-SYS and the Teams Room compute device.
But guess what – you don’t need to worry about it, because it’s already in the Schematic.
But if you ever need to add this component to one of your own designs, you can add it from the Inventory under Peripherals.
This component also provides monitoring information from the Microsoft Teams Room computer back into the Q-SYS environment,
which means you can monitor the health of all your Microsoft Teams Room PCs with Q-SYS Reflect Enterprise Manager.
Wait, what? Did somebody mention you can get a free trial available at Oh that was me. (Nailed it.)
Alright, back to our Sample Design walkthrough, Step 6 introduces us to something called: Webhooks.
This is an optional step that allows a system administrator to receive notifications if the approved Q-SYS design is altered or falls out of spec.
Simply create a new webhook in Teams, and copy this Webhook code right here to enable these notifications.
The final step in this setup process is the Room Optimization UCI for Teams Rooms.
This is a custom UCI that's built into the sample file that's intended to be opened on a mobile device in the room in question.
And Patrick’s still over there, so I’ll let him tell you about it.
Thanks! So now that the room is up and running thanks to what Nate’s done on the design—all that’s left is to finesse it.
As long as your system is on the same wifi network as your smartphone,
you can access the special Optimization UCI in this design from the palm of your hand,
which will guide you through some simple steps to optimize the audio flow for your specific space.
You’ll go through this friendly step-by-step guide by actually getting on a Teams call with someone else,
which allows someone on the far end to help you verify and fine-tune elements of the call quality.
Once you’re done, select the “Finish” button, and these optimized settings will be saved in your design.
In fact, now that Patrick’s done, my system’s status indicates that it's running with commissioned settings.
And once again, this update will appear in my Microsoft Teams Channel via the Webhook.
Finally, let’s look at that UCI Deployment within the Microsoft Teams Room Console.
Let’s look at our Logitech Tap which is displaying that Microsoft Teams Room application.
We can tap the options icon and then the “Room Controls” label to gain access to our UCI.
It looks like it’s a native interface to Microsoft Teams Room, and that is by design … but make no mistake,
you are interacting with a Q-SYS UCI, just the same way you might on a Q-SYS touch screen.
In fact, the version that I see inside Q-SYS looks noticeably more boring.
But that’s because we’re applying a Microsoft Theme that we’ve provided within this sample design file.
It tells the display to reinterpret each object according to particular colors, fonts,
and sizes that we’ve worked out to make each control look like it’s native to the Microsoft Teams environment.
So if you need to adjust this UCI, add or remove some controls, etc.,
you can specify which CSS Class styles to apply to each control to keep that visual appearance seamless for the end user.
Thanks for watching and we’ll see you next time.

Lesson Description

Integrating Microsoft Teams Rooms into Q-SYS 8m 54s

We show you how to use the new tools for achieving the Microsoft Teams experience in your next installation. 

Tutorial includes:

- Connecting "Q-SYS Control for MTR" app onto your Teams Compute device

- using the Sample Q-SYS design for Teams Room

- tuning the room with the Room Companion App

- controlling the room with a single pane of glass to control Teams and Q-SYS using Logitech Tap, 

- tuning the room activating to your Q-SYS Designer.

Downloads and Links

Integrating Microsoft Teams Rooms into Q-SYS 8m 54s