Allow 3rd party devices to join Meet video meetings

As an administrator, you can set up Google Meet to let participants join your organization’s Meet video meetings from third-party video conferencing systems.

Join Meet meetings from a Zoom Room device

Zoom Room devices can join Meet meetings using Meet’s built-in interoperability at no additional cost. To join Google Meet meetings, the supported Zoom Room must be configured using the Zoom Admin. For details on supported devices and how to turn Meet interoperability on for your Zoom Rooms, see the Zoom support article.
Some features are not supported when joining from a Zoom Room. For example:
  • Present Via HDMI
  • Dual-screen support
  • Change layout
  • Closed captions
  • Activities (Polls, Q&A, Recording, Breakout Rooms)
  • Chat

Note that when joining a scheduled Meet meeting set to private in Google Calendar from a Zoom Room, users with access to the device will be able to one-touch join without being prompted to enter the meeting code.

Allow Zoom Rooms to connect to a Meet call without asking

By default, participants joining using a Zoom Room must be admitted to the Meet meeting by someone already in the meeting. As an administrator, you can allow Zoom Room devices to join Meet meetings without asking by generating an interop token and adding it to the Zoom Admin.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. In the Admin console, go to Menu ""and then"" Appsand thenGoogle Workspaceand thenGoogle Meet.
  3. Click Interoperability tokensand thenAdd a token.
  4. Select Zoom from the dropdown menu.
  5. Enter a token name for your own reference and click Create a token.
  6. Copy the token to your clipboard and click Close
    Important: Be sure to copy the token. It will not be shown again.
  7. Go to Zoom Web Portal and log in as an admin with the privilege to edit Zoom Rooms settings. Add your unique token. 
  8. In the Zoom Web Portal, go to Room Managementand thenZoom Roomsand thenSupport Google Meet web client meeting on Zoom Rooms.
  9. Paste the token into the Google Meet Interop Token field.
    For details, see the Zoom support article.
Join Meet meetings from a Cisco Webex device

Cisco Webex video conferencing devices can join Meet meetings using Meet’s built-in interoperability at no additional cost. To join Google Meet meetings, the supported Cisco Webex device must be configured using the Cisco Control Hub. For details, see the Cisco Webex documentation.

Some features are not supported when joining from a Cisco Webex device. For example:

  • Present via HDMI
  • Dual-screen support
  • Change layout
  • Closed captions
  • Activities (Polls, Q&A, Recording, Breakout Rooms)
  • Send chat

Allow Webex systems to connect without asking

By default, participants joining using a Cisco Webex device must be admitted to the Meet meeting by someone already in the meeting. As an administrator, you can allow Cisco Webex devices to join Meet meeting without asking by generating an interop token and adding it to the Cisco Webex Control Hub.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. In the Admin console, go to Menu ""and then"" Appsand thenGoogle Workspaceand thenGoogle Meet.
  3. Click Interoperability tokensand thenAdd a token.
  4. Select Cisco from the dropdown menu.
  5. Enter a token name for your own reference and click Create a token.
  6. Copy the token to your clipboard and click Close
    Important: Be sure to copy the token. It will not be shown again.
  7. Go to Cisco Webex Control Hub and add your unique token.
    For details, see the Cisco Webex documentation.
Join Meet meetings from other 3rd-party devices using Pexip

To join Meet video meetings, third-party systems must be standards-based (SIP/H.323), and they can be located inside or outside your organization. If a third-party system has calendar integration that supports SIP URI (uniform resource identifiers), participants may also join Meet meetings with a single touch.

Supported third-party systems include:

  • Cisco
  • Polycom
  • Lifesize
  • Sony
  • Microsoft Skype for Business and Surface Hub

View all supported devices.

Before you begin

To use Meet with third-party systems, you need to use the Google Workspace partner product Pexip for Google Meet.

  1. Sign up for the Pexip for Google Meet interoperability service at pexip.com/google-meet-contact.
  2. Configure Pexip to work with Google Meet.
  3. To let participants connect to Meet meetings using Skype for Business, get a Skype for Business hostname from Pexip.

After you register, Pexip will contact you to complete the configuration.

Turn on Meet interoperability for Pexip

Step 1: Add interoperability gateways

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. In the Admin console, go to Menu ""and then"" Appsand thenGoogle Workspaceand thenGoogle Meet.
  3. Click Interoperability tokensand thenAdd a token.
  4. Select Pexip from the dropdown menu.
  5. Enter a token name for your own reference and click Create a token.
  6. Copy the token to the clipboard and click Close.
    Important: Be sure to copy the token. It will not be shown again.
  7. Send the gateway token to Pexip.
  8. On the Interoperability tokens list, under Trusted devices, choose how you want third-party systems to connect to this gateway:
    • To require third-party systems to ask before connecting to a meeting, click Turn off "".
    • To allow third-party systems to connect without asking, click Turn on "".

Step 2: Turn on Meet interoperability for Pexip

  1. In the Meet video settings section, click Gateway Interoperability.
  2. In the Interoperability section, check the Allow interoperability with other systems box.
  3. Choose the format for the meeting IDs used to join meetings:
    • Use long meeting IDs—Allow third-party systems to join automatically by SIP URI or when participants manually enter IDs into the system. Long IDs are added to calendar events and invites when events are created and can be used as long as the Meet link itself is available.
      Best practice: Long meeting IDs are recommended for most domains.
    •  Use short meeting IDs—Let participants join meetings using third-party systems by entering short IDs. When you choose this option, calendar events and invites contain a link to a page where participants get the short ID. Short IDs themselves are not added to calendar events and invites, SIP URIs are not generated, and calendar integrations don’t work. To join meetings using third-party systems, participants always need to enter the short IDs manually. Short IDs expire about 2 weeks after the last time they are used to join a meeting.
      Best practice: Short meeting IDs are recommended only for domains with existing interoperability configurations during transition periods while integrated joining options roll out.
    • Use both long and short meeting IDs—Provide both long IDs, which support calendar integrations, and short IDs, which support systems with limited-input functionality. Calendar events and invites show both long IDs and the link to the page where participants get short IDs. Participants can join meetings from supported third-party systems using a single touch. Participants can also join by manually entering long IDs (from events and invites) or short IDs (retrieved from a link in the calendar event or invite).
      Best practice: Using both long and short meeting IDs is recommended for domains that need to support both third-party systems with calendar integrations and systems with limited-input functionality, such as remote controls that make entering meeting IDs time-consuming or error-prone.
  4. Enter the gateway IP address, gateway hostname, and meeting ID prefix. External guests use these to join Meet meetings from third-party systems. What you enter should match the settings of your Pexip Infinity gateway.
  5. (Optional) To set up interoperability for Skype for Business:  
    1. In the Interoperability with Skype for Business section, check the Provide an additional gateway for Skype for Business users box. 
    2. In the hostname field, enter the Pexip Skype for Business hostname. To get this hostname, contact Pexip.
  6. Click Save. If you configured an organizational unit or group, you might be able to either Inherit or Override a parent organizational unit, or Unset a group.

    In most cases, existing third-party calendar integrations discover new SIP URIs for Meet, and upcoming Meet video meetings appear on meeting lists automatically.

    To get joining information for Skype for Business, participants click More joining options on the calendar event or invite.

Information that Google shares with Pexip

When interoperability between Google Meet and third-party conference systems is turned on for your organization, Google shares with Pexip:

  • That interoperability is turned on for your Google Workspace domain and that an authentication token was created. Pexip requires this information for validation and compliance purposes.
  • Debugging and troubleshooting information, including meeting logs that contain participant IDs, meeting codes, and device information. 

Related topics

For administrators:

For users:


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

Search
Clear search
Close search
Google apps
Main menu
Search Help Center
true
true
false
true
true
73010
false
false