Create a peering policy to organize your viewers into peering groups based on their IP addresses. Use the API setup to keep IP addresses private from Google.
Important: Custom settings override all previous settings and apply to the entire organization. For example, if you upload a custom rules CSV file for one organizational unit, those rules will be used for everyone in your company.
Select network policies & upload network rules
Test Google Meet's Enterprise Content Delivery Network (eCDN) using the Testing policy before uploading custom rules.
-
In the Google Admin console, go to Menu
Apps Google Workspace Google Meet.Requires having the Service Settings administrator privilege.
- Click Meet video settings.
-
(Optional) To apply the setting only to some users, at the side, select an organizational unit (often used for departments) or configuration group (advanced).
Group settings override organizational units. Learn more
- Click eCDN settings.
- Select a policy:
- Testing: Devices in the network connect randomly. Use this policy for testing only.
- Subnet: Devices within the same block connect. Configure a fixed subnet mask of N bits so the entire IP address space is divided into /N CIDR blocks.
- Custom rules: Devices connect according to your custom network rules. You can also specify a fallback peering policy. The default fallback peering policy is Blocked.
- On-premises service: Devices connect without sending IP information to Google. Choose this advanced setting to provide a custom implementation of the Meet eCDN on-premises API and manually map IP information to peering groups. This setting requires a URL pointing to a custom web service implementation. For more information about creating a local service for the Meet eCDN On-Premises API, go to Work with the Meet eCDN On-Premises API.
- Next:
- If you're not using custom rules, click Save.
- If you're using custom rules, click Upload file Import.
You are ready to start testing Meet eCDN.