- 05 Nov 2024
- 4 Minutes to read
- Print
- DarkLight
- PDF
Network Setup Recommendations
- Updated on 05 Nov 2024
- 4 Minutes to read
- Print
- DarkLight
- PDF
Dialpad is a cloud-based business phone system that allows you to make and receive calls from anywhere in the world, as well as manage contacts, get call logs and voicemails, transfer calls, and more.
We know you are on the move, and we're pleased to confirm that Dialpad is operable on any device with a reliable internet connection!
Let's dive into the details of network settings.
Bandwidth calculations
To ensure the best possible voice quality, we recommend using a high-speed DSL, broadband, or fiber-optic connection for all services. This applies to desk phones, Dialpad Desktop software, Dialpad Web App, and any CTI/mini dialer (ie: Salesforce CTI, Chrome CTI Extension, etc)
Calculate for each concurrent instance you plan to run:
- Voice: minimum 100kb/sec up/down
- Mobile Voice: minimum 4G (or equivalent wifi access)
- Video 1:1 Calls: minimum of 1.2-1.5Mbps up/down
- Video Meetings: minimum 1.2-1.5Mbps up and 3Mbps down
- Mobile Video (any): 4G+ (or equivalent wifi access)
Routers, switches, and firewalls
Dialpad does not require a specific brand or mode router, switch or firewall — however, to achieve the best possible quality of service, network hardware should have the following capabilities:
- QoS
- Bandwidth Limiting
- SNMP
We also require that the following features to be turned off for Dialpad traffic (as they can interfere with the service).
Please contact our Support Team if you are unable to turn off these features:
- SIP-ALG
- Deep Packet Inspection (DPI)
- Stateful Packet Inspection (SPI)
No. A stateful firewall is a type, while a stateful packet inspection is a firewall and/or router setting (which we recommend disabling).
VPN
Dialpad is not designed to function over a VPN. If your company uses a VPN, please utilize a split tunnel and direct Dialpad traffic outside of the VPN.
VLAN
A virtual LAN (VLAN) can be used to put your hard-wired phone devices into separate networks, and to manage security and routing policies separately. If you plan to deploy IP phones, they can be placed in a "voice VLAN".
A voice VLAN is not a network requirement for Dialpad service but best practices for setting security, DHCP, routing, QoS/CoS a voice VLAN may be used.
Setting a voice VLAN is required when Workstations are daisy-chained through IP Phones.
DHCP option 66
For each Voice VLAN there are phones configured on, you'll need to set up the DHCP server with the following URL: https://prov10.dialpad.com
Once the URL has been configured, the phones will need to be attached to the correct Voice VLAN and support:
- CDP
- LLDP
- Auto VLAN Discover
- Static Assignment
Multiple internet circuits
If you are utilizing multiple internet circuits, the best practice is to set them up as Primary/Failover.
Please contact our Support Team for any questions.
FQDNs
Routing to a Fully Qualified Domain Name (FQDN), allows modern cloud networks flexibility for routing, security, system maintenance and remote device management.
Dialpad uses FQDNs for managing:
- Registrations
- SIP requests to set up a call
- Device Firmware
- Device Configurations
- Remote Devices
Dialpad recommends allowing traffic to and from each of the following FQDNs:
- dialpad.com
- devpfs.obitalk.com
- storage.googleapis.com
- ubervoice.ubervoip.net
- turn.ubervoip.net
- stun.l.google.com
- uvwss.ubervoip.net
- legacy.dialpad.com
- dialpadcdn.com
- static.dialpadcdn.com
- prov*.dialpad.com
- google-public-dns-a.google.com
- google-public-dns-b.google.com
- *pusher.com
- *googleusercontent.com
- *.ymcs.yealink.com
- *.yealink.com
- realtime.push.dialpad.com
- realtime2.push.dialpad.com
Ports & protocols
Port and protocols used by Dialpad phones and applications residing in a private network are listed below. Outbound port configurations are needed on the firewall to allow traffic to the destination ports listed in the right-hand side column of the tables. Stateful firewalls (not to be confused with stateful packet inspection!) are recommended for Dialpad deployments. For a stateful firewall, inbound port configurations are not needed as they are automatically opened as a reply to the outbound traffic.
Desktop Native, Mobile, & Browser Applications
Traffic Type | Protocol | Domain | Port |
---|---|---|---|
Product features (images, social profiles etc) | HTTPS (TCP) | *.dialpad.com *.dialpadcdn.com | 443 |
Messaging | HTTPS (TCP) WSS (TCP) | *.dialpad.com *.ubervoip.net *.pusher.com | 443 |
Transport | UDP and TCP | *.dialpad.com *.ubervoip.net | 5060, 7060 |
Call Signaling | WSS (TCP) SIP/TLS (TCP) | *.dialpad.com *.ubervoip.net | 443, 5061 |
Call Media | SRTP (UDP) | No specific domain or IP | 16384 to 32768 |
Customer Media (contact, avatar, MMS images) | HTTP (TCP) | No specific domain or IP | 443 |
STUN | UDP | stun.l.google.com | 19301 to 19302 |
TURN | UDP and TCP | turn.ubervoip.net | 443 |
Server Discovery | DNS (SRV records) | google-public-dns-a.google.com google-public-dns-b.google.com | 53 |
Desk Phones - Poly, Obi-Edition & UCS, Yealink and Grandstream
Traffic Type | Protocol | Domain | Port |
---|---|---|---|
Provisioning | HTTPS (TCP) | *.dialpad.com | 443 |
Transport | UDP and TCP | *.dialpad.com *.ubervoip.net | 5060, 7060 |
Call Signaling | SIP/TLS (TCP) | *.dialpad.com *.ubervoip.net | 5061 |
Call Media | STRP (UDP) | No specific domain or IP | 16384 to 32768 |
Poly Device Management System (PDMS) | TCP/UDP | *.obihai.com *.obitalk.com *.polycom.com | 443, 10000 to 20000 |
Firmware Downloads | TCP | *.dialpad.com downloads.polycom.com storage.googleapis.com | 80, 443 |
Network Time Service | NTP (UDP) | pool.ntp.org | 123 |
Directory Services (LDAP) | TCP | *.dialpad.com | 389 |
Yealink Remote Provisioning Services (RPS) | TCP/UDP | *.yealink.com | 443 |
Yealink Management Cloud Service | DM and HTTPS | *.ymcs.yealink.com | 443, 8110, 8443, 8445, 8446 |
Grandstream Device Management Service | TCP | firmware.grandstream.com | 443, 8443 |
Jitter, Packet Loss & Latency
In order to maintain high quality audio on voice and video calls, Dialpad recommends the following jitter, packet loss, and latency (round trip) values.
Optimal values
- Jitter: Less than 40 milliseconds
- Packet Loss: Less than 2%
- Latency (round trip): Less than 125 milliseconds
Acceptable values
- Jitter: Less than 100 milliseconds
- Packet Loss: Less than 5%
- Latency (round trip): Less than 200 milliseconds
For more information on performing network tests and analyzing results, be sure to read this Help Center article.
Virtual environment
Virtual desktop infrastructure (VDI) is a server-based computing model that separates the desktop environment and associated application software from the physical client device that is used to access it.
Dialpad supports users on our Native or Web App. While our Customer Support team is dedicated to helping resolve any issues, it's important to note that if you're using a virtual environment, we'll need to replicate the problem in a non-VDI environment for troubleshooting.
If the issue cannot be replicated in a non-VDI environment, Dialpad Support may request that you report the issue to the appropriate virtualization vendor's product support team.
If you experience performance issues with the Dialpad Desktop or Web App as a result of running it in a VDI environment, Dialpad will not consider those issues to be product- or platform-related.
Unsupported configurations
Dialpad does not support using our services through the following tools:
- Remote Desktop Clients (RDPs)
For running the network tests, please follow the instructions noted in this Help Center article.