Configuring endpoints to support One-Touch Join

This topic describes how to configure each of the supported endpoint types so they can be used with Pexip Infinity One-Touch Join.


We recommend that you have already completed the steps in Configuring Pexip Infinity for One-Touch Join. In particular, you will need some of the information that you previously entered when Adding One-Touch Join endpoints to Pexip Infinity, in order to complete the configuration on each endpoint.

Configuring Cisco OBTP endpoints for OTJ

In order for Cisco OBTP endpoints to obtain One-Touch Join meeting information, the Conferencing Node associated with the endpoint uses the endpoint's API to push the information out to the endpoint.

The endpoint must have an account set up with a role of Admin that can be used by One-Touch Join to access the endpoint's API.

Hiding or changing the meeting subject

The next major release of Pexip Infinity, version 25, will include options to hide or change the meeting subjects that will appear on OTJ endpoints, according to rules that can be applied across your One-Touch Join deployment. In the meantime, you can hide meeting subjects from appearing on the screen of individual Cisco endpoints (running CE 9.12.3 or later) by configuring the endpoint as follows:

  1. On the Cisco endpoint web UI, go to Setup > Configuration > User interface.

  2. For Bookings Visibility Title, select Hidden:

Configuring Poly OTD endpoints for OTJ

In order for Poly OTD endpoints to obtain One-Touch Join meeting information, each One-Touch Join Conferencing Node emulates a Microsoft Exchange server. The Poly endpoint then connects to the Conferencing Node and registers to the calendaring service on the node in order to pull meeting information, as shown in the diagram below.

Note that this emulation of an Exchange calendaring service on the Conferencing Node is purely to provide the Poly endpoint with its meeting information. It is completely separate to the process by which the Conferencing Node initially obtains the meeting information from the calendar/email service being used for One-Touch Join — which can be either Exchange or G Suite.

It is important that you do not set up your Poly endpoints until after you have completed the steps to add the endpoint details to Pexip Infinity.

DNS records

If you have a One-Touch Join deployment that includes Poly endpoints in a location with more than one Conferencing Node, you should spread the Poly endpoint registrations across all nodes in the location to maximize performance and provide redundancy. To achieve this, we recommend that all Poly endpoints in a location register to a single FQDN which uses round-robin DNS to resolve to each Conferencing Node in turn. This will require you to set up appropriate DNS records for all Conferencing Nodes in the location, and ensure that your DNS server is configured to round-robin between these records.

For more information and examples, see Enabling Poly endpoints to register to One-Touch Join.

Poly authentication

In normal Pexip Infinity usage Poly endpoints authenticate to One-Touch Join using digest authentication, with the exception of HDX endpoints which require NTLMv2.

When Pexip Infinity has been deployed in a secure mode of operation (and therefore FIPS compliance has been enabled), NTLMv2 and digest authentication are disabled and basic authentication is used. As a result, when in this mode:

  • HDX endpoints are not supported
  • Trio endpoints must be configured to allow basic authentication.