Launch Summary
We’ve added a new network option to help ensure better quality video meetings with Google Meet. Now in addition to the range of fixed and official IP addresses of domains Google Workspace and users who are not from Google Workspace, Google Meet supports TLS over port 443.
Some network configurations do not work with SRTP over 443, which prevented Meet calls from connecting. Meet now encapsulates SRTP in TLS, increasing overall compatibility. This change will be available initially on the web and soon on mobile devices. When it is available, we will announce it on the Google Workspace updates blog.
How to get started
- Administrators: If you or your partner organization already use Meet, no change is required, and this change won’t affect you. If you or your partner organization uses DPI technology over port 443, you must ensure that you add the corresponding user SNIs to the allowed entities list:
- Google Workspace admins: Meet traffic over TLS will use the same fixed IP range exclusive for Google Meet on Google Workspace domains.
- Non-Google Workspace admins: Meet traffic over TLS will use the same fixed IP range exclusive for non-Google Workspace users starting in July and will use the temporary IP range from June until June 30 July. See the Help Center article for additional information.
- End users: Will not be affected.
Throwing rhythm
- Rapid Release Domains: Gradual release (up to 15 days for feature visibility) starting on June 16
- Scheduled release domains: Gradual release (up to 15 days for feature visibility) starting from June 30
Availability
- It is available to all Google Workspace customers, as well as G Suite Basic and Business customers
Resources
This article is the translation of the English blog published on June 16.
