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, to set you up for success.
To ensure the best possible voice quality, we recommend using either any high-speed DSL, Broadband, or Fiber-optic connection. With a minimum dedicated upload and download bandwidth of 100 kilobits/sec for each voice line, you plan to run.
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, the Network hardware should have the following capabilities:
- Bandwidth Limiting
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:
- Deep Packet Inspection (DPI)
- Stateful Packet Inspection (SPI)
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.
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.
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:
- 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:
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 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
|Product features (images, social profiles etc)||HTTPS (TCP)||
|Call Signaling||WSS (TCP)
|Call Media||SRTP (UDP)||16384 to 32768|
|STUN||UDP||stun.l.google.com||19301 to 19302|
|TURN||UDP and TCP||turn.ubervoip.net||443|
|Server Discovery||DNS (SRV records)||
Poly Desk Phones (Obi-Edition & UCS)
|Call Signaling||SIP/TLS (TCP)||*.dialpad.com
|Call Media||STRP (UDP)||16384 to 32768|
|Poly Device Management System (PDMS)||TCP/UDP||*.obihai.com
|443, 10000 to 20000|
|Network Time Service||NTP (UDP)||pool.ntp.org||123|
Dialpad does not support using our services through any of the following tools:
- Virtual Machines (VMs)
- Virtual Desktop Interfaces (VDIs)
- Remote Desktop Clients (RDPs)
For running the network tests, please follow the instructions noted on this Help Center article.