Migrating to One-Touch Join for Pexip Infinity

This guide explains how Pexip Service customers who are currently using the Pexip Service's One-Touch Join feature can migrate to One-Touch Join using a dedicated Pexip Infinity deployment.

For information on migrating from a dedicated Pexip Infinity deployment to One-Touch Join for Pexip Service, see Migrating to One-Touch Join for Pexip Service.

To ensure a smooth migration with minimal loss of service, we recommend you complete the required steps in the following order:

  1. Ensure you have met the required Prerequisites.

  2. Configure One-Touch Join on Pexip Infinity.

  3. Reconfigure your calendar service.

  4. Reconfigure your endpoints to obtain meeting information from One-Touch Join for Pexip Infinity.

Prerequisites

Obtaining licenses

You will require an OTJ license for every endpoint that will use the One-Touch Join feature.

For information on licensing, see One-Touch Join (OTJ): trial, orderability and enablement or contact your Pexip account manager.

Configuring a calendar service

Although One-Touch Join supports meetings created in Microsoft Outlook, Google Calendar, and most other calendar providers, we recommend that the room resources and mailboxes associated with your OTJ endpoints are created in Microsoft 365 tenants (on-premises mailboxes are not officially supported, even in Exchange hybrid deployments). This feature uses the Graph API to authorize access to the mailboxes used for OTJ.

  • If your Pexip Infinity One-Touch Join deployment will also use Microsoft 365, you can continue to use these mailboxes. However, you will need to reconfigure the mail enabled security group, because this will use a different app ID. For full information, see Reconfiguring your Microsoft 365 calendar service.

  • If your Pexip Infinity One-Touch Join deployment will use another calendar service, you must set this up before you migrate to One-Touch Join for Pexip Infinity.

Configuring One-Touch Join on Pexip Infinity

You must set up your Pexip Infinity One-Touch Join deployment before you migrate from the Pexip Service.

Full information about how to do this is available in the Pexip Infinity documentation under Configuring and using One-Touch Join.

Reconfiguring your Microsoft 365 calendar service

If your Pexip Infinity One-Touch Join deployment will use the same Microsoft 365 tenant used for One-Touch Join on the Pexip Service, you can continue to use the existing mailboxes. However, you will need to reconfigure the mail-enabled security group in Microsoft 365, because this uses a different app ID for the Pexip Service than it does for Pexip Infinity.

To do this, connect to Exchange Online PowerShell and update the application security policy and run the following command, using the following values:

  • AppId: the Application (client) ID that was generated by Azure when you created the OTJ Graph API application.
  • PolicyScopeGroupId: the email of the mail-enabled security group containing the One-Touch Join resources.
  • Description: a description of the access policy.

For example:

New-ApplicationAccessPolicy -AppId e7e4dbfc-046f-4074-9b3b-2ae8f144f59b -PolicyScopeGroupId otjrooms@pexample.com -AccessRight RestrictAccess -Description "Restrict this app to members of distribution group otjrooms."

Reconfiguring your endpoints

Both One-Touch Join for Pexip Infinity and One-Touch Join for Pexip Service require that every endpoint used for OTJ has an associated calendar and mailbox. In both cases the OTJ service reads the calendars of each meeting room endpoint, parses information about all the meetings to which the endpoint has been invited, and then provides this information to the endpoint. However, the mechanism by which the information is provided to the endpoint depends on the service and endpoint type:

  • Cisco endpoints

    • for Pexip Infinity, OTJ pushes the meeting information to the endpoint using the endpoint's API

    • for Pexip Service, OTJ works via an individual macro that you create in Pexip Control Center and install on each endpoint.

  • Poly endpoints

    • for Pexip Infinity, the endpoint connects to the OTJ service on a Conferencing Node and pulls the meeting information.

    • for the Pexip Service, the endpoint connects to the OTJ service and pulls the meeting information.

For this reason, you will need to reconfigure any endpoints used for One-Touch Join so that they obtain meeting information from the appropriate service as per the instructions below.

Cisco endpoints

To migrate Cisco endpoints to use One-Touch Join for Pexip Infinity, you must first uninstall the macro and remove the endpoint from the Pexip Service, and then configure the endpoint to allow One-Touch Join to connect to it.

Repeat the process for every endpoint you wish to migrate.

Poly endpoints

To migrate Poly endpoints to use One-Touch Join for Pexip Infinity, you must reconfigure the endpoint to connect to a Conferencing Node using the credentials you created for it in Pexip Infinity.

Full details of how to do this are given in the Pexip Infinity documentation under Configuring Poly OTD endpoints for OTJ.