Google Meet setup for Pexip interoperability

This article explains how to make your environment ready for using Pexip's interoperability service for Google Meet. (For information on how to integrate Google Meet with Pexip Infinity, please go here.)

It covers the standard steps for configuring your environment, and the optional additional steps to enable SIP Guest Join.

Configuring your environment

To configure your environment for Google Meet interoperability:

  1. If you are using your own domain you need to set up the DNS records for your own domain prior to starting the process described below. You do not need to set up DNS records if you are using your own subdomain on
  2. When we enable your Meet Gateway interoperability within our system, you’ll receive an initial email with instructions on enabling the feature within your Google Admin pages and generating a security token to upload to Pexip. This establishes the trust relationship between your environment and Pexip's environment.

  3. Generate your security token in Google, and then upload it to Pexip:

    1. Go to Apps > Google Workspace > Google Meet > Interoperability tokens.
    2. Select Add Token.
    3. Select a Type of Pexip.
    4. Give the token an appropriate name, e.g. PexipInterop.
    5. Select Trusted device so that your endpoints registered on the service can bypass the Meet lobby.

    6. Select Create a token.

      You are shown the generated interoperability token.

      This is the only time you will be able to see the token before it is stored and encrypted in Google Workspace.

    7. Save and upload the security token to Pexip, using the link in your email. This process also includes entering any prefix provided in the email, if you are using short meeting IDs.

  4. Go to Apps > Google Workspace > Google Meet and then configure the Meet video settings and select the Interoperability settings.
  5. Enable Allow interoperability with other systems and then enter your Google Meet interoperability settings:

    Meeting ID length Select Use long meeting IDs.
    Gateway IP address and Gateway hostname Enter the settings as specified in your email.
    Meeting ID prefix Leave blank.
    Provide an additional gateway for Skype for Business users

    Select this option if you want to generate an address that allows Skype for Business users to join your meetings (available via the "More joining options" link in the calendar event or invite). If you enable the additional SfB gateway, you must set the Hostname to (irrespective of whether you use your own domain or a custom domain).

  6. You can also configure who has access to the gateway interoperability feature.

    When you enable gateway interoperability (by selecting Allow interoperability with other systems), it is made available by default to everyone in the organization.

    However, you can restrict access to the interoperability functionality to specific Organizational Units (OUs) or groups, although it is not currently possible to enable it for individual users. See for more details about how to do this.

    Note that:

    • You can configure a subset of specific OUs/groups for interop access before turning on the main Allow interoperability with other systems to avoid temporarily making it available to everybody in the organization. If you subsequently want to broaden the access you can add other OUs/groups or just enable it for everybody in the organization.
    • The security/access token applies to the entire Google Workspace tenant (i.e. to all specified OUs, groups or the entire organization, as appropriate).
  7. You’ll receive a confirmation email from Pexip saying the service has been configured and you can start using the service.

Host management and video lock

Within a meeting, a meeting host must ensure that the Turn on their video setting (within the Host management options for that meeting) is enabled, otherwise VTCs will not be able to join the meeting.

Using SIP Guest Join

Pexip's standard Google Meet interoperability solution allows your own video conferencing endpoints (and your guests) to join Google Meet meetings that you are hosting. The "SIP Guest Join" (SGJ) feature lets you join Google Meet meetings with your own video conferencing endpoints where that meeting is being hosted by an external third-party organization who has not enabled Pexip interoperability themselves.

Note that this is a guest join experience, therefore someone has to be in the Google Meeting to admit you from the lobby. If nobody admits you within 30 seconds, you will have to dial again.


As a prerequisite to enabling Guest Join you must:

  • Enable One-Touch Join — either using One-Touch Join for Pexip Service (controlled via Pexip Control Center) or via a self-hosted Pexip Infinity platform that is dedicated to managing OTJ. See About One-Touch Join for more information.
  • Register your endpoints to the Pexip Service or have the Trusted Devices add-on (this is included in the ERC Premium license bundle).

Enabling guest join

If you are using One-Touch Join for Pexip Service (controlled via Pexip Control Center) then no additional configuration is required — you are automatically able to use the guest join feature.

Using a self-hosted Pexip Infinity platform for OTJ

If you are using a self-hosted Pexip Infinity platform for OTJ, then you need to add a suitable OTJ Meeting Processing Rule to handle invitations to Google Meet meetings (see Adding One-Touch Join meeting processing rules for general details on how to do this).

  1. Add an OTJ Meeting Processing Rule (One-Touch Join > OTJ Meeting Processing rules) with a Meeting type of Google Meet SIP Guest Join.
  2. Save the rule. Your endpoints can now join externally-hosted Google meetings.

More information

These articles provide further details about the Google Meet interop service: