About One-Touch Join

Pexip Infinity's One-Touch Join (OTJ) feature integrates support for existing "click to join" videoconferencing endpoint workflows into your Pexip Infinity deployment. With One-Touch Join, when users schedule a meeting in Microsoft Outlook or Google Calendar and include in the meeting invitation a room that contains a supported Cisco or Poly endpoint, the endpoint will display a Join button just before the meeting is scheduled to begin. Participants can then simply walk into the room and select the button, and the endpoint will automatically dial in to the meeting.

One-Touch Join is available as an optional licensed feature within the Pexip Infinity platform.

In most cases, One-Touch Join will be implemented as a feature within a wider Pexip Infinity deployment, and run on Conferencing Nodes alongside other Pexip Infinity services. However, you can also set up separate OTJ locations within your deployment that contain Conferencing Nodes used solely for One-Touch Join. A third option appropriate in some situations is to implement a separate Pexip Infinity deployment purely for One-Touch Join, for example if you are a Pexip Service customer wishing to use One-Touch Join, or you are a large enterprise wishing to separate the resources used for your One-Touch Join deployment. For more information, see Deploying a dedicated One-Touch Join platform.

Enabling One-Touch Join

All Conferencing Nodes are capable of running One-Touch Join, although the service will only come into active operation on a node when the location the node is in is associated with a One-Touch Join Endpoint Group.

Enabling the Pexip One-Touch Join service within your Pexip Infinity deployment involves the following steps, each described in separate topics:

  1. Permitting the One-Touch Join service to access the calendars used for One-Touch Join. How this is achieved depends on which calendar/email service is used in your environment:

    • For Google Workspace, you create a service account and share OTJ calendars with the service account. This service account authenticates to Google Workspace with a private key using 2-legged OAuth. For full details, see Configuring Google Workspace for One-Touch Join.

      We also offer an alternative means for Google Workspace environments where the recommended method of using a service account is not desirable. This alternative method uses a domain user which authenticates to Google Workspace using 3-legged OAuth. For full details, see Configuring Google Workspace for domain user authorization.

    • For Exchange on premises, you create a service account that uses application impersonation to read the OTJ calendars. This service account authenticates to Exchange using basic authentication. For full details, see Configuring Exchange on-premises for One-Touch Join.

    • For Office 365, you create an application registration in Azure for OTJ, and grant the application permission to read OTJ calendars using Microsoft's Graph API. OTJ uses 2-legged OAuth to authenticate to Office 365 without the need of a service account. For full details, see Configuring Office 365 using Graph for One-Touch Join.

      We continue to support existing One-Touch Join deployments for Office 365 that used a service account with application impersonation to read OTJ calendars. This service account authenticated using OAuth and used the EWS API to access mailboxes. However, the EWS API is being deprecated by Microsoft, so for new One-Touch Join deployments in Office 365 environments you should instead use the Graph API to provide access to room resource mailboxes. For information on managing these existing deployments, see Configuring Office 365 using EWS for One-Touch Join.

  2. Configuring Pexip Infinity for One-Touch Join
  3. Configuring endpoints to support One-Touch Join
  4. Viewing One-Touch Join status

For an overview of the process and general deployment and network considerations for One-Touch Join, see One-Touch Join process and deployment overview.

For a guide for end users, see Scheduling and joining meetings using One-Touch Join.

For help with troubleshooting your One-Touch Join deployment, see Troubleshooting One-Touch Join.

Supported Google Workspace editions

Pexip One-Touch Join is supported in the following Google Workspace environments:

  • Google Workspace Basic
  • Google Workspace Business
  • Google Workspace Enterprise

Supported Exchange environments

Pexip One-Touch Join is supported in the following Microsoft Exchange environments:

Exchange servers

  • Office 365
  • Exchange 2013 (with the latest updates)
  • Exchange 2016 (with the latest updates)
  • Exchange 2019 (with the latest updates)

Outlook clients

Meetings scheduled in all Outlook clients are supported. Note that different third-party Outlook add-ins for different Outlook versions may format the join details for some meeting types slightly differently.

Supported endpoints

Endpoints used for One-Touch Join must not also be registered to the calendaring service on other systems such as the cloud-based Webex Hybrid Calendar Service, or Cisco TMS XE.

Cisco OBTP

OTJ is supported on Cisco VTC endpoints that support Cisco One Button to Push (OBTP) and are running TC, CE, or RoomOS software. This includes:

  • Cisco Webex Room series (Room, Room Kit)
  • Cisco Board series
  • Cisco C series (C20, C40, C60, C90)
  • Cisco DX series (DX70, DX80)
  • Cisco EX series (EX60, EX90)
  • Cisco MX series (MX200, MX300, MX700, MX800)
  • Cisco SX series (SX10, SX20, SX80)
  • Webex Desk Series (Webex Desk, Webex Desk Pro, Webex Desk Mini)

There are two ways in which One-Touch Join can be implemented for these endpoints, depending on whether or not the endpoint is on the same network as the OTJ Conferencing Nodes.

  • If the endpoint is on the same network as the OTJ Conferencing Node, the Conferencing Node will connect directly to the endpoint to provide it with the necessary meeting information. When setting up these endpoints in Pexip Infinity, you assign them an Endpoint type of Cisco OBTP.

    For more information on how to configure these endpoints, see Configuring Cisco OBTP endpoints for OTJ.

  • If the endpoint is not on the same network as the OTJ Conferencing Node (for example if it is located in a home office) but is registered to Webex or Webex Edge for Devices, the Conferencing Node will connect to Webex Cloud, which will in turn connect to the endpoint to provide it with the necessary meeting information. When setting up these endpoints in Pexip Infinity, you assign them an Endpoint type of Webex Cloud registered.

    For more information on how to configure these endpoints, see Configuring Cisco Webex Cloud registered endpoints.

Poly OTD

OTJ is supported on Poly VTC endpoints that support Poly One Touch Dial (OTD). This includes:

  • Poly RealPresence Group series v5.0.0 or later
  • Poly Trio series
  • Poly HDX series (unless Pexip Infinity has been deployed in a secure mode of operation - for more information, see Poly authentication); must be running a software version that supports NTLMv2 for calendaring, e.g. 3.1.11 or later
  • Poly Studio X series
  • Poly G7500 series
  • Poly Debut series

For information on how to configure these endpoints to support Pexip One-Touch Join, see Configuring Poly OTD endpoints for OTJ.

Supported meeting types

This release of Pexip One-Touch Join can be used to join the following types of meetings:

  • Pexip Infinity meetings (i.e. those scheduled using the VMR Scheduling for Exchange feature)

  • Pexip Service meetings (i.e. those scheduled using the plugin available to Pexip Service users)

  • Google Meet (for Google Workspace integrations only)

  • Microsoft Teams

  • Skype for Business

  • Webex

  • Zoom

  • BlueJeans

  • GoToMeeting

You can also create your own meeting processing rules for meeting types not listed above. For more information, see One-Touch Join meeting types and transforms.

Supported number of endpoints and Conferencing Nodes

The One-Touch Join feature will support up to 4,000 room resource calendars and associated endpoints. This applies to One-Touch Join both when integrated with a Pexip Infinity deployment (i.e. when running on Conferencing Nodes alongside other Pexip Infinity services), and as a deployment dedicated to One-Touch Join.

For integrated One-Touch Join deployments (i.e. where OTJ is being implemented as a feature within a wider Pexip Infinity deployment), we recommend at least one Conferencing Node for every 1,000 endpoints in a location (although you may wish to include one or more additional Conferencing Nodes for redundancy). For large or busy deployments, you may need to add additional Conferencing Nodes per location to provide the additional capacity required when One-Touch Join is implemented — we recommend that you consult your Pexip authorized support representative for advice on your particular deployment.

For dedicated One-Touch Join deployments of all sizes (i.e. up to the supported 4,000 room resource calendars and associated endpoints), a minimal Pexip Infinity deployment of 1 Management Node and 1 Conferencing Node should suffice. However, we recommend adding additional Conferencing Nodes for redundancy.

Pexip Infinity server requirements

In most cases you will be enabling One-Touch Join within a new or existing Pexip Infinity deployment, and the One-Touch Join service can be run alongside other Pexip Infinity services on each Conferencing Node. Enabling One-Touch Join within most Pexip Infinity deployments (see Supported number of endpoints and Conferencing Nodes) will not significantly increase the processing requirements of the Management Node or Conferencing Nodes, therefore our standard Server design guidelines still apply. However, if your deployment is expected to be particularly large or busy, we recommend that you consult your Pexip authorized support representative for advice.

For dedicated One-Touch Join deployments, see Minimum hardware requirements.

In both cases, we recommend that each Conferencing Node runs on a different VM host and uses different storage.