Voice connectivity requirements

High-quality audio calls with Google Voice require a properly configured network. Verify that your network is ready for voice traffic:

Make sure your network has enough bandwidth to handle all concurrent calls.
Open the outbound ports to allow voice traffic to flow to and from your network.
Allowlist the URIs used by Voice for web traffic, APIs, feedback reports, logs upload, and connectivity setup.

Voice Architecture

Outbound ports need to allow voice traffic

Set up your network so the following ports allow media traffic to flow to and from your organization:

Outbound UDP ports range: 19302–19309
Outbound UDP ports range: 26500–26501
Outbound TCP port 443

Voice UDP ports ranges use the Chrome WebRTC UDP Ports Setting.

Bandwidth requirements per site

A site’s network should have enough bandwidth for all concurrent voice calls, plus extra bandwidth for other needs.

To calculate the optimal bandwidth requirement range, multiply the amount of bandwidth required for each voice call by the peak number of concurrent participants.

Average bandwidth per participant * peak number of concurrent participants = Minimum site bandwidth requirements

Bandwidth recommendation per participant

Minimum requirement: 32 kbps (to account for actual media and RTCP signaling overhead)
(Recommended) Good quality: Above 50 kbps (to account for actual media and RTCP signaling overhead)
Calls between two Google Voice clients will attempt to adapt to lower bitrates when possible

Allowlist URIs

Make sure there's full network access to core Google services. If your network has restrictions or filtering policies for users, make sure there’s network access to the following URI patterns. These patterns are used by Voice for web traffic, APIs, feedback reports, logs upload, and connectivity setup.

https://*.google.com/*
https://*.googleapis.com/*
https://*.gstatic.com/*
https://*.googleusercontent.com/*
https://*.telephony.goog/*
stun.l.google.com:19302 (used for STUN requests)

Voice IP address range

Voice traffic is secured and encrypted, so there’s no need to restrict traffic to the Google IPs.

If, however, you have network constraints that require you to restrict traffic, put the following set of IP ranges on an allowlist to allow Voice media servers. The IPs are used exclusively for Voice for Google Workspace, so you can identify voice traffic used in Google Workspace. This can help you better set up and optimize network and firewall access.

IPv4: 74.125.39.0/24
IPv6: 2001:4860:4864:2::0/64
IPv4: 74.125.250.129/32 (used for STUN requests)

Additional connectivity requirements

For Poly trusted ports and IP addresses, read Poly's documentation.

For mobile phones connected to corporate WiFi:

Apple push notifications—Apple's documentation
Firebase push notifications—Google's FCM documentation

Was this helpful?

How can we improve it?