Admins that are migrating from Videonor Teams gateway to Teams gateway provided by the Pexip cloud service.
Follow the instructions in this article carefully.
We will follow the standard Pexip cloud CVI setup procedure until item 4 at which time we will deviate from it. This is because the auto-generated instructions assume a clean setup which is not the case if your company is already using Teams gateway via Videonor. This guide takes this into consideration and specifies what you need to do instead to ensure a smooth transition.
After requesting access to the service, you will receive an email asking you to authorize the Pexip CVI application. Click the link "Initiate consent for your Tenant".
This opens a web page where you again need to click on "Initiate consent for your Tenant".
Follow the instructions to log in with your O365 account and then click "Accept" when prompted.
First, sign in:
Then, accept the request:
Please see this link for more information about permissions and what they are used for.
Finally, a confirmation page verifies that the consent was successfully provided and it will list some powershell commands. DON'T RUN THOSE POWERSHELL COMMANDS YET - you will encounter an error if you do that.
We must use other powershell commands to avvoid disturbing the existing config. What you must do is:
Take note of the "Application ID", like below:
In this case, it is "923c9f0a-b883-4efe-af73-54810da59f83". Compare this value with what you got - if it differs - USE THE ONE FROM THE WEB PAGE!
Step 5: Add the new Application ID to the existing "CsVideoInteropServiceProvider" config
First, set the domain you are managing.
You can use your company's tenant-name + onmicrosoft.com OR a domain configured with that tenant.
Run ONE of these commands to set the domain:
$microsoftdomain = "company-azure-tenant-name.onmicrosoft.com"
$microsoftdomain = "company-domain.com"
Once that's done, run these three commands (the second will prompt you for your microsoft sign-in)
$sfbSession = New-CsOnlineSession -OverrideAdminDomain $microsoftdomain
If that went well your powershell prompt should look like this (except the domain part of course):
Now - check if your tenant already have a "pexip" type provider.
If you get a result like this and the application is "cc9dc74a-612b-436f-ada9-e85fa2f92746", then this is the Videonor Teams gateway.
If you don't get ANY result here - double check that you pasted the correct command. If you still don't get a result you probably doesn't have an active Teams gateway. In that case, just go back to the web page - copy paste the commands from there and you're all set.
Otherwise, read on:
Now, take the Pexip CVI "AadApplicationId" obtained at the consent screen. If you got the same one as mentioned in figure 4.1, you don't need to alter the command below, but if you did, you must change the second AadApplicationId given here. Without any edit, it looks like this:
Set-CsVideoInteropServiceProvider -Identity Pexip -AadApplicationIds "cc9dc74a-612b-436f-ada9-e85fa2f92746;923c9f0a-b883-4efe-af73-54810da59f83"
Once that's done, run this command again to verify you now have two applicationids set to:
When done, your output should look something like this:
At this point, all we've done is to allow the Pexip cloud service to work as a MS Teams gateway for your Azure tenant. We haven't touched the invitation template or other parts of the existing configuration.
Make a test call at this point. It can take several hours before the configuration changes we just made are applied to the Teams back-end so at this point we'll simply use any video endpoint to make this test (i.e the trust portion of the setup won't work yet).
Book a Teams meeting in outlook and connect to it with Teams.
Then, on a video system, connect to that same meeting using the meeting id from the invitation but the domain from the pexip cloud service, like this:
123456789@domain. If your company is setup with mydomain.onpexip.com, then dial firstname.lastname@example.org
Notice in the Teams client that the video endpoint joins as a guest.
This concludes part 1. At this point, we will simply have to wait until the changes takes effect. The changes we're waiting for is the trust part which separates your own endpoints from 3rd party endpoints.
You can try proceeding after 8 hours. In most cases, the configuration changes have been applied to the Teams back-end at this point. Part is found here:
Migrate to Pexip cloud Teams gateway PART 2