Configuring G Suite for Google Meet integration

This topic explains the G Suite configuration steps that are required when integrating Pexip Infinity with Google Meet.

It covers the following processes:

Generating your gateway access tokens
Google Meet interoperability settings

You can configure your Google Meet settings from the Google Admin console via Apps > G Suite > Google Meet.

Generating your gateway access tokens

Gateway access tokens are the private codes assigned to your G Suite account that are used by Pexip Infinity when it routes calls into your Google Meet conferences. Tokens can be defined as "trusted" or "untrusted", see Enabling access and admitting external participants into Google Meet conferences for details.

The generated tokens are only displayed once in G Suite, at the time of creating them. These tokens need to be configured on your Pexip Infinity system. Therefore you should have your Pexip Infinity Administrator interface open and available at the same time as you are generating the tokens within G Suite.

To set up your trusted and untrusted gateway access tokens from the G Suite administrator console:

Go to Apps > G Suite > Google Meet > Gateways for Interoperability.
Select Add Gateway.
Enter a gateway name, for example the domain of your Pexip Infinity deployment plus a "trusted" or "untrusted" label, for example "example.com (trusted)".
Select Generate.

You are shown the generated access token.

This is the token you must enter into Pexip Infinity.
Use the option to copy the token to your clipboard.

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

Switch to your Pexip Infinity Administrator interface and configure this gateway token in Pexip Infinity:

Go to Call control > Google Meet Access tokens and select Add Google Meet access token.

Add the details of your token:

Name	The name that you specify here is used elsewhere in the Pexip Infinity interface when associating the token with a Call Routing Rule or Virtual Reception, so we recommend including an indication if it is your trusted or untrusted token.
Access token	Paste in the access token from your clipboard.

Select Save.

You can now return to the G Suite console and Close the token dialog.
Use the Trusted device button to set the token to either trusted or untrusted as appropriate.
If you want to create a trusted and an untrusted token, repeat the above steps to generate the second gateway token.

You can create as many trusted and untrusted gateways as required, although one of each type is normally sufficient. Service providers may need to apply multiple pairs of access tokens for each tenant they are managing.

See Configuring Pexip Infinity as a Google Meet gateway for more information about Pexip Infinity configuration requirements.

Google Meet interoperability settings

You also need to enable Google Meet interoperability to allow other systems to dial into your Google Meet calls. You do this via Apps > G Suite > Google Meet and then configure the Meet settings.

In particular, you should configure the following Interoperability options:

Name	Description
Interoperability	Select this option to enable gateway interoperability and to configure the other settings.
PIN prefix	This prefix is applied to generated conference meeting codes. It can then also be part of any regex-based validation within Pexip Infinity when users are entering meeting codes. Note that you cannot control the overall length of the generated meeting code.
Gateway IP address and Gateway DNS address for external guest joining instructions	The IP address and DNS address you specify here are used when Google Meet generates the addresses that allow third-party system to access the conference. They are used to direct callers to your Pexip Infinity Conferencing Nodes that will then connect them into the Google Meet conference. Gateway IP address: set this to the IP address of one of your Conferencing Nodes. Gateway DNS address: set this to the name of the DNS SRV record that you have set up for your Conferencing Nodes (e.g. vc.example.com). Alternatively you can use the FQDN of one of your nodes (e.g. px01.vc.example.com). Ensure that you refer to Conferencing Nodes that will be routable from those systems and devices that will be using those dial-in addresses. See DNS record examples for more information about enabling endpoints to route their calls to Conferencing Nodes.

Name

Description

Interoperability

Select this option to enable gateway interoperability and to configure the other settings.

PIN prefix

This prefix is applied to generated conference meeting codes. It can then also be part of any regex-based validation within Pexip Infinity when users are entering meeting codes.

Note that you cannot control the overall length of the generated meeting code.

Gateway IP address and Gateway DNS address for external guest joining instructions

The IP address and DNS address you specify here are used when Google Meet generates the addresses that allow third-party system to access the conference. They are used to direct callers to your Pexip Infinity Conferencing Nodes that will then connect them into the Google Meet conference.

Gateway IP address: set this to the IP address of one of your Conferencing Nodes.
Gateway DNS address: set this to the name of the DNS SRV record that you have set up for your Conferencing Nodes (e.g. vc.example.com). Alternatively you can use the FQDN of one of your nodes (e.g. px01.vc.example.com).

Ensure that you refer to Conferencing Nodes that will be routable from those systems and devices that will be using those dial-in addresses.

See DNS record examples for more information about enabling endpoints to route their calls to Conferencing Nodes.

Controlling access to gateway interoperability

You can enable everybody in your organization to offer gateway interoperability to their Google Meet conferences, or you can limit interoperability to specific OUs (organizational units). It is not currently possible to enable it for individual users.