TLS support for Google Meet

Quick launch summary

We’re adding a new network option to help you ensure higher quality video meetings with Google Meet. Now, in addition to the range of official, fixed IP addresses in Google Workspace domains and non-Google Workspace users, Google Meet supports TLS over port 443.

Some network setups do not work with SRTP over 443 which was preventing Meet calls from connecting. Meet now encapsulates SRTP in TLS which increases overall compatibility. This change will initially be available on the web, and will be available for mobile soon. We’ll announce it on the Google Workspace Updates blog when it’s available.

Getting started

  • Admins: If your or partner organization is already using Meet today no changes are required and this change will have no impact. If you or your partner organisation uses DPI technology on port 443, make sure to add the corresponding user SNIs to the allowlist:
    • Google Workspace admins: Meet traffic over TLS will use the same fixed IP range dedicated for Google Meet in Google Workspace domains.
    • Non-Google Workspace admins: Meet traffic over TLS will use the fixed IP range dedicated for non-Google Workspace users from July onward and will use temporary IP range from June to July 30th. See the Help Center article for additional information.
  • End users: No end-user impact.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

Resources

TLS support for Google Meet

Quick launch summary

We’re adding a new network option to help you ensure higher quality video meetings with Google Meet. Now, in addition to the range of official, fixed IP addresses in Google Workspace domains and non-Google Workspace users, Google Meet supports TLS over port 443.

Some network setups do not work with SRTP over 443 which was preventing Meet calls from connecting. Meet now encapsulates SRTP in TLS which increases overall compatibility. This change will initially be available on the web, and will be available for mobile soon. We’ll announce it on the Google Workspace Updates blog when it’s available.

Getting started

  • Admins: If your or partner organization is already using Meet today no changes are required and this change will have no impact. If you or your partner organisation uses DPI technology on port 443, make sure to add the corresponding user SNIs to the allowlist:
    • Google Workspace admins: Meet traffic over TLS will use the same fixed IP range dedicated for Google Meet in Google Workspace domains.
    • Non-Google Workspace admins: Meet traffic over TLS will use the fixed IP range dedicated for non-Google Workspace users from July onward and will use temporary IP range from June to July 30th. See the Help Center article for additional information.
  • End users: No end-user impact.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

Resources