Network & Connectivity Requirements

This article provides a detailed overview of the network and connectivity requirements essential for the RingDNA Communication Hub. It includes information about the servers, port ranges, and IP addresses that users must have access to.

Connectivity Overview

The RingDNA Communication hub offers two options for call connectivity.

If your network is not properly configured to support cloud-based calling over WebRTC, your team may encounter issues that could disrupt their calling experience, such as robotic audio, one-way audio, dropped calls, and audio delays.

Hardware Requirements

Minimum System Requirements

• Desktop or laptop:

  	Minimum	Recommended
  RAM	8GB	16GB
  CPU	Dual-core 2.0GHz (Intel Core i5 6th gen+, AMD Ryzen 3, or Apple M1)	Quad-core (Intel Core i5 8th gen+, AMD Ryzen 5, or Apple M2)
  OS	Windows 10 or later / macOS 11 (Big Sur) or later	Same
  Browser	Google Chrome (latest two major versions)	Same

• USB Wired or Wireless Headset

  • For best results, connect wired headsets directly to the computer and not a USB hub.
  • For Wireless headsets, use the included USB dongle if it comes with one.

Headset Requirements

We recommend using a quality headset for your calls. A laptop’s built-in microphone can pick up background noise and isn’t suitable for use with RingDNA. The best choice is a USB headset, as it connects reliably to your computer and provides good sound quality.

While wireless headsets using Bluetooth can work, their connectivity can sometimes be unreliable resulting in audio that skips, cuts out, or has static. If you experience issues with a wireless headset, it’s best to switch to a wired one.

For the best results, plug the USB headset directly into your computer rather than using USB hubs or docking stations, which can sometimes cause audio issues.

Bandwidth Requirements

Fast internet isn’t the same as consistent, reliable internet. Even if your connection has very high-bandwidth or speed, there could still be issues with jitter, packet loss, bufferbloat (excess buffering that increases latency), or latency resulting in call quality issues.

The following table lists the network requirements to deliver acceptable audio quality through WebRTC with the OPUS codec:

For more information see: Running Network Tests and Interpreting Results.

Network Configuration Requirements

Domain Connectivity Requirements

Firewalls are used by network administrators to protect a private network by blocking or allowing traffic to and from internet destinations based on certain rules, such as traffic direction, protocol, and IP address.

In order to use the RingDNA Communication hub, traffic must be allowed to and from the following domains.

• *.revenue.io
• *.ringdna.net
• *.ringdna.com
• *.pubnub.com, *.pndsn.com, *.pubnub.net, *.pubnubapi.com
• *.launchdarkly.com

If access is not allowed for all domains listed above, the RingDNA Communication hub may not work as expected.

Carrier Connectivity Requirements

Your firewall should also allow outgoing TCP and UDP traffic to our carrier partner’s media servers and signaling gateways, and allow return traffic in response.

† The client will select any available port from the ephemeral range. On most machines, this means the port range 1,024 to 65,535

VPN

If your company uses a VPN, please configure a split-tunnel to allow a call’s signaling and media traffic to connect outside of the VPN.

Our dialer performs optimally when allowed to connect directly to our carrier partner (Twilio). Additional network hops introduced by your company VPN may introduce additional latency and degrade call quality.

Virtual Desktops and Remote Desktop Clients

We do not support using our services through Virtual Desktop Infrastructure (VDI) or Remote Desktop Clients (RDP).

These architectures do not support the low-latency connection required for real-time audio and communication platforms. Because audio is captured and processed on a remote server rather than the local machine, it must travel an extra round trip across the network before reaching the carrier. The added latency and packet loss will result in a poor experience for both your users and callers.

Global Low Latency (GLL) Requirements

By default, the RingDNA Communication Hub will resolve a hostname to the edge location with the least latency. In order for GLL to give accurate results, the intermediate DNS must:

• Support RFC 7871 - Client Subnet in DNS Queries.
• Reside in the same edge as the endpoint. For example, a user in the US configured with a VPN to Europe or configured with a DNS server that resides in Europe will result in connecting that user to an edge in Europe.

Routers, Switches, and Firewalls

Our services do not require specific network hardware. To achieve the best possible service quality, your network should be configured to:

• Enable Quality of Service (QoS) rules which prioritizes the voice media and signaling traffic
• Disable SIP-ALG
• Disable Deep Packet Inspection (DPI)
• Disable Stateful Packet Inspection (SPI)

Salesforce Authentication & API Access

If your Salesforce Org restricts login access to a range of IPs, you will need to allowlist our application IPs in Salesforce. More information can be found in this troubleshooting article: Salesforce OAuth Failed: Ip Restricted

Improving Call Quality

If your connection meets the thresholds in the Bandwidth Requirements table but you’re still experiencing issues, the following steps can help:

• Connect using an ethernet cable whenever possible.
• Move closer to your Wi-Fi access point — multiple walls can degrade signal strength and introduce packet loss.
• If your Wi-Fi access point is dual-band, use the 5GHz band instead of 2.4GHz, especially if you have many smart home devices on the same network.
• Reduce the number of devices competing on the same Wi-Fi channel.
• Avoid large data transfers or backups over the same network during calling hours.
• Implement QoS rules to prioritize traffic to the IP ranges listed in Network Configuration Requirements.
• Bluetooth headsets can introduce latency or jitter when the connection is poor or the battery is low. A wired headset is more reliable.

Administrators can proactively monitor user network health using the Call Alerts Dashboard, which surfaces users who may be experiencing connectivity issues before they escalate.

For a guided walkthrough of testing your connection and interpreting results, see Running Network Tests and Interpreting Results.