Configuring Pexip Infinity as a Google Meet gateway

The Infinity Gateway provides any-to-any video interoperability with Google Meet.

Third-party systems can connect to Google Meet conferences via the Infinity Gateway either by dialing the conference directly or via a Virtual Reception (IVR).

This topic describes the configuration and administrative steps that are required to use Pexip Infinity as a Google Meet gateway. It assumes that you have already performed a basic installation and configuration of Pexip Infinity. This topic covers:

See Integrating Google Meet with Pexip Infinity for more information about the user experience within Google Meet conferences.

Ensuring a Google Meet (ghm) license is installed

You must have a ghm license enabled on your platform (Platform > Licenses). This allows you to configure access tokens and route calls to Google Meet.

The ghm license specifies the total number of access tokens you can configure, and is required in addition to the standard Pexip Infinity call licenses. If necessary, contact your Pexip authorized support representative to purchase the required license.

Configuring your access tokens

All communication between Pexip Infinity and Google Meet is authenticated by access tokens that identify your Google Workspace account (see Generating your interoperability access tokens).

To configure your trusted and untrusted access tokens in Pexip Infinity:

  1. Go to Call control > Google Meet Access tokens and select Add Google Meet access token.
  2. Add the details of your trusted 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

    The access token value as shown in your Google Workspace account when you generated it.

  3. Select Save.
  4. Repeat the above steps to add the details of your untrusted token.

These tokens will now be available to associate with any Virtual Receptions and Call Routing Rules that you configure (as described below) to handle Google Meet conferences.

Note that:

  • The access tokens apply to the entire Google Workspace tenant, but you can enable interoperability on a per-OU (organizational unit) basis within Google Workspace.
  • Service providers may need to apply multiple pairs of access tokens for each tenant they are managing.

Configuring Virtual Receptions and Call Routing Rules

There are two ways in which you can configure Pexip Infinity to route calls into Google Meet conferences:

  • Routing directly via the Infinity Gateway: here you use a Call Routing Rule to route incoming calls for specific alias patterns — that will typically include the meeting ID — directly into the relevant Google Meet conference. This means that the endpoint can dial an alias, such as and be taken directly into the conference.
  • Routing indirectly via a Virtual Reception: here you configure Pexip Infinity to act as an IVR gateway or "lobby" by configuring a Virtual Reception to prompt the caller to enter the meeting ID of the required conference, and then use a Call Routing Rule (typically the same rule as used for direct routing) to route the call into the Google Meet conference. This means that the endpoint can dial a general alias, such as and then enter the specific meeting ID, such as 1234567890123, and then be transferred into the conference.

You can use either or both of these two methods, depending upon your requirements. The configuration required for direct and indirect routing is explained below.

Depending on your dial plan requirements, you may want to use multiple Call Routing Rules, where some rules use a trusted token and other rules use an untrusted token. For example, if you want to associate calls received via a particular location as trusted, and all calls received in other locations as untrusted then you will need to configure two rules — one rule for calls received in the trusted location that is associated with the trusted token, and then another lower priority rule that is associated with the untrusted token.

DNS and ports requirements

You need to ensure that the endpoints and systems you want to gateway into Google Meet can call into Pexip Infinity Conferencing Nodes, and that Conferencing Nodes can call out to Google Meet.

These are the port usage rules for call signaling and media between Google Meet and Conferencing Nodes (Proxying Edge Nodes and Transcoding Conferencing Nodes):

Source address Source port Destination address Dest. port Protocol Notes
Google Meet 19302–19309 Conferencing Node 40000–49999 ** UDP SRTP/SRTCP
Conferencing Node 33000–39999 **

Google Meet

( and

443 TCP (HTTPS)  
Conferencing Node 40000–49999 ** Google Meet 19302–19309 UDP SRTP/SRTCP

‡ See for the actual IP ranges that need to be allowed.

** Configurable via the Media port range start/end, and Signaling port range start/end options (see About global settings) .

Call signaling and media ports

Call and participant status

When using the Pexip Infinity Administrator interface to monitor calls that are placed into Google Meet conferences, you should note that:

  • Each participant who is gatewayed into a Google Meet conference is listed as a separate gateway call. However, if multiple participants are connected to the same Google Meet conference, the Live View (Status > Live View) shows them as connected to the same external conference.

  • When viewing the participant status for a gateway call, the meeting ID, such as 1234567890123, is shown as a participant alias. This participant represents the gateway call leg into Google Meet. If you look at the media streams associated with that participant you see that:

    • Pexip Infinity sends (subject to bandwidth) three VP8 video streams (each at different resolutions) and one 1 audio stream to Google Meet for that participant.
    • Pexip Infinity receives one video and one audio stream for each external participant in the conference, up to a maximum of 8 video streams (to support Pexip's standard 1+7 layout). If there are more than 8 other participants then only an audio stream is received for those extra participants.

    Other participant aliases that are displayed for that call include the device that placed the call (such as and one or more aliases in the format spaces/<id>/devices/<id> which represent the other participants in the Google Meet conference.

  • You cannot control (e.g. disconnect, mute or transfer) any of the other participants connected to the Google Meet conference.
  • VTCs may be unable to connect to the meeting, or get disconnected from the meeting, if the meeting host disables the Turn on their video option in the meeting settings. These types of disconnections are reported as SIP 480 errors (with a cause of "Call rejected" and type of "RemoteDisconnect").

Additional deployment information

  • Each participant who is gatewayed via Pexip Infinity into a Google Meet conference consumes two call licenses (one for the inbound leg of the call and one for the outbound leg, as is standard for calls via the Infinity Gateway calls). Any external participants who are connected directly to the Google Meet conference do not consume a license. See Pexip Infinity license installation and usage for more information.
  • You cannot limit the Maximum outbound call bandwidth (the call leg towards Google Meet) — it is fixed at 2 Mbps.
  • If the Google Meet conference is recorded, "streaming enabled" indicators are included in the video stream sent to gatewayed participants.
  • Chat messages are supported in both directions between Google Meet and other chat-enabled clients. However, the name of the sender from the Google Meet side is not identified on messages received by Skype for Business clients.