To set up Meet eCDN, configure your network to let eCDN traffic pass through. After that, create and upload a CSV file containing your network configuration to the Google Workspace admin console.
Before you begin
Note: You may need a network engineer for the tasks on this page.
Use a Chrome browser with version 121 or higher. Mobile apps and other browsers can still watch live streams without Meet eCDN. They'll get the live stream directly from Google's data centers but won't share media. This could increase bandwidth.
Step 1: Check technical compatibility
Make sure your network settings, software, and devices are compatible with eCDN.
Step 2: Allow persistent WebSockets connections
Allow persistent connections and WebSockets (with HTTPS as the underlying protocol) upgrades for meet.google.com/ecdn/tracker/* in all proxy or firewall software.
For instructions, check out the documentation for your proxy or firewall.
Step 3: Allow P2P connections over WebRTC
Devices within your network must be able to connect directly using WebRTC over UDP. To ensure this, make devices visible to each other and allow UDP traffic with ports above 30,000 in your network.
Step 4: Define peering groups to create network rules
A peering group is a collection of nodes that are allowed to share media with each other. Devices in a peering group are either allowed to peer or are blocked from peering. Allowed devices can only connect to other devices in the same peering group.
A peering group should have high speed networking between its members and not span a bottleneck. This allows for efficient media delivery and avoids overloading network links inside the network.
Configure peering groups and network rules and add them to a CSV file. Google provides a template you can use in the Format your CSV file section on this page.
Setting up peering groups for local peering within buildings or sites is a good way to avoid bandwidth constraints. More complex network scenarios can be solved with more detailed peering groups.
Avoid VPNs
Viewers should never use Meet eCDN when connecting from a VPN. It’s strongly recommended that IP ranges used by VPNs are defined as excluded peering groups in your CSV file. Otherwise, devices will appear to be in close network proximity when they aren't. Connecting them might use more bandwidth than not using eCDN.
Format your CSV file
Create a CSV file that defines a contained network environment for eCDN. This file is uploaded as part of the Meet eCDN custom rule settings. A rule is one row in the file.
Custom rules are evaluated from top to bottom when applied to the private IP address of a device. The first rule that matches a device will be applied for that device. Any conflicting rules lower down in the file are ignored.
The file size upload limit is 10 MB. Google provides a file template you can use, or you can create your own using the table structure below. To find the template:
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
In the Admin console, go to Menu
Apps
Google Workspace
- Click Meet video settings.
- Click eCDN settings.
- Select the ➕ icon in the top right corner of the section.
- Click Download template.
CSV file table structure
| Column | Description | Format | Examples |
|---|---|---|---|
|
Network name |
Defines the peering group Grouping key (allowed devices with the same network name will potentially connect). |
30 character limit | US-NYC |
| Network location | A more detailed description of the subnet range. | 30 character limit | Wi-Fi |
| IP range start | Smallest IP of the specified range. | 123.123.123.123 | 192.168.1.1 |
| IP range end | Largest IP of the specified range. | 123.123.123.123 | 192.168.2.255 |
| Peering policy | Either “allowed” or “blocked” | ”Allowed" or "blocked" | Allowed |
