Gong Dialer network connectivity requirements

Who can use this: Tech admin, Business admin

Available on: Gong Foundation, Gong Engage

To make high-quality calls with the Gong Dialer, your network must meet specific requirements. Without the right setup, reps may experience dropped calls, audio delay, robotic-sounding audio, or one-way audio.

Hardware and browser requirements

• At least 8 GB of RAM

• An Intel i5 CPU or equivalent or better

• Google Chrome, latest version, running on Windows or macOS

The Gong Dialer works best on Google Chrome because Chrome tags call media packets and prioritizes them in your network. If reps are experiencing audio quality issues, check CPU usage in the activity monitor or task manager to identify spikes from other applications.

Headset

Connect a USB headset directly to the computer, not through a USB hub or dock. Devices connected via a hub or dock may experience audio issues.

Network performance thresholds

For high-quality voice calls, the following network metrics must be met:

When calculating required bandwidth, add at least 20% buffer to cover peak calling periods.

Connection type

Use an Ethernet connection rather than Wi-Fi where possible. If Wi-Fi is required, additional connection configurations may be needed.

Firewall settings

Your firewall should allow outgoing TCP and UDP traffic from your applications to Gong's infrastructure and allow return traffic in response. Externally initiated connections back into the network should not be permitted.

Any firewalls, switches, and wireless access points used should support marking and prioritizing traffic to ensure optimal voice quality.

If your organization uses SIP ALG on firewalls or routers, disable it to allow VoIP traffic to work correctly.

IP addresses and FQDNs to allow

The following IP range is used to process call audio:

The following FQDNs are used by Gong for call signaling. Allow TCP on port 443 for each:

Using a proxy, MPLS, or VPN

If your organization uses a proxy, MPLS, or VPN, set up a split tunnel so that traffic to Gong, Twilio, and your Gong subdomain is routed locally, directly to the internet from the rep's physical location. Routing Gong and Twilio traffic through a centralized proxy or VPN can mask the rep's actual location, causing less efficient call routing, added latency, and reduced call quality.

Exclude the following from your proxy, MPLS, or VPN:

• Gong traffic

• Twilio traffic

• Your specific Gong subdomain, for example: subdomain.gong.io

• The relevant IP addresses listed in the IP address table above

Gong uses a background service called Global Low-Latency (GLL) to find the most efficient network path for calls. This service requires that the rep's actual network location is visible.

If you work in a shared office or co-working space that manages its own network infrastructure, share this article with the IT team. If they are unable to make these changes, call quality may be affected. In that case, using a personal mobile hotspot instead of the shared network may be a better option.

Quality of Service (QoS)

All Gong Dialer voice traffic should be prioritized across your network. Configure Quality of Service (QoS) settings on your network equipment to ensure voice packets are given priority over other traffic types.