Network configuration is vital for video calls! Dialpad Meetings has a few requirements and recommendations to help keep your clients happy, and your presentations clear and visible to all participants, regardless of their joining location.
Let's dive into the details of network infrastructure for Dialpad Meetings.
Who can use this
This article is for network administrators, specifically those managing their company’s firewall and proxy security settings.
Ports for Dialpad Meetings
Specific ports and protocols must be enabled to use Dialpad Meetings.
Stateful firewalls (not the same as stateful packet inspection!) are recommended for Dialpad Meetings deployments. Stateful firewalls do not need inbound port configurations as they automatically open as a reply to the outbound traffic.
Traffic Type | Protocol | Domain | Port |
|---|---|---|---|
Product features (images, social profiles etc) | HTTPS (TCP) | *.dialpad.com *.dialpadcdn.com | 443 |
Messaging | HTTPS (TCP) | *.dialpad.com | 443 |
Transport | UDP and TCP | *.dialpad.com *.ubervoip.net | 5060, 7060 |
Call Signaling | WSS (TCP) | *.dialpad.com | 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 |
FQDNs for Dialpad Meetings
Routing to a Fully Qualified Domain Name (FQDN), allows modern cloud networks flexibility for routing, security, system maintenance and remote device management.
Dialpad recommends allowing traffic to and from each of the following FQDNs:
dialpad.com
www.obitalk.com
www1.obitalk.com
prov.obitalk.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
Firewalls for Dialpad Meetings
We also require that the following features 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)
Aren't Stateful Firewalls the same as a Stateful Packet Inspection?
No. A stateful firewall is a type, while a stateful packet inspection is a firewall and/or router setting (which, we recommend disabling).
Test your meeting configuration
Before joining a meeting, we recommend testing your setup.
Test your setup anytime from https://videotest.dialpad.com/
You'll also find the test link in email and Google Calendar invitations.
Joining a meeting if ports are blocked
When ports (webRTC or firewalls) are blocked, you can join a meeting as an audio participant. You won’t have full meeting permissions, but you can still view screenshares.
Dial-Out to join a meeting
If you experience a network connection issue when trying to join a meeting (or even during a meeting), you’ll be prompted to check your network settings, and given the Dial-Out option. Dial the number listed on the screen, or enter your phone number so that we can call you..png)
Limited connection screenshare
If a user is connected to the Internet and encounters a blocked WebRTC or firewall port, they will not be able to view screenshares initially.
Dialpad provides a secondary screenshare option — if your connection is blocked, all you need to do is select View screenshare from the pop-up message..png)