Testing
NOTE: there is a limitation in this lab exercise as we are using a single Azure tenant and MS365 subscription for all lab groups. Ideally, we would use a single tenant per group, but we have yet to find a practical way to achieve this. This limitation means that we can only add one CVI setting, and this points to just one group, which is the demo deployment used by the trainer (group vc20). All users will therefore get Teams Invite links that point to this group rather than your group, however, you can substitute this groups domain information for your own group’s details. For example, the Teams meeting Invite would always link to the Virtual Reception teams@vc20-osl.pexip.net, however, if you were in group vc1, you would use teams@vc1-osl.pexip.net.
To create a Teams meeting, you need to log into the Teams client (on your OWN laptop/PC, NOT in the RDP session) with the credentials for your user and group (see Section #12 in the lab sheet). If you already use a Teams login, you could either:
- Log out of the Teams client and use the lab login details.
- Use the Teams WebApp (potentially, you may need an incognito browser session) https://www.microsoft.com/en-gb/microsoft-365/microsoft-teams/group-chat-software.
- Use the awesome free Portals app from My Teams Lab that allows you to set up and test multiple Teams user logins (see https://www.myteamslab.com/2020/01/portals-for-office-365.html).
You can set up a Teams meeting in a couple of ways via the calendar:
Using New Meeting:
Click the Calendar Tab, then “New Meeting”
You MUST ensure that you add an attendee (such as your email address) otherwise the Teams Meeting invite details will not be added. Even so, these details will not appear until you have saved the invite and re-opened it:
Initial Meeting invite with no Join instructions:
Meeting Invite re-opened once it has been “Sent”:
E.g, you now see in the body of the message:
Join with a video conferencing device
teams@vc20-osl.pexip.net
Video Conference ID: 127 557 862 4
Alternative VTC dialling instructions
Learn more | Meeting options
NOTE: Be aware that the domain seen will be that of “vc20-osl.pexip.net”, and the “Alternate VTC dialling instructions” link will also point to the VC20 edge node. Please ignore this and use the domain for your group. Calls should be therefore routed through your groups Infinity deployment, and if you have set things up correctly, all will work just fine.
Using Meet Now:
This is a little clunky and it may be that Microsoft will continue to work on this (it has changed a few times recently), but at the time of writing, you should be able to follow these steps:
Click the Calendar Tab, then “Meet Now”, then “Start Meeting”:
Click “Join Now”(there is a link that says “Other join options”, but it simply seems to turn from purple to white and nothing else),. Once in the meeting, Click “More actions” (the three dots in the action bar), then select
NOTE: As before, the domain seen will be that of “vc20-osl.pexip.net”, and the “Alternate VTC dialling instructions” link will also point to the VC20 edge node. Please ignore this and use the domain for your group. Calls should be therefore routed through your groups Infinity deployment, and if you have set things up correctly, will work just fine.
Using the Pexip Infinity Virtual Reception to Teams gateway service:
After the Virtual Reception and Call Routing Rule have been configured, third-party systems and devices can now dial the alias of the Virtual Reception (e.g. teams@<your Pexip Infinity domain>) and then, when prompted by the IVR service, enter the meeting code of the Teams conference they want to join. The Pexip Infinity distributed gateway will then route the call into the appropriate Teams conference.
Using the direct gateway service:
After the Call Routing Rule has been configured, third-party systems and devices can now dial an alias that matches your specified pattern (e.g. teams.1234567890@<your Pexip Infinity domain>) to be routed directly into the appropriate Teams conference (in this example the conference with a meeting code of 1234567890).
In both cases, try dialling from a registered device or internal connection, and from an external connection to ensure that lobby bypass is working as expected.
