Network Configuration
Due to Zoom Phone's cloud-based architecture, configuring Zoom Phone for your network is substantially easier in comparison to legacy, on-premises phone systems. From the simplest of perspectives, users need two key factors to begin successful calling: a working internet connection and open network ports. So long as users can successfully maintain an active connection with Zoom Phone data centers and the necessary ports are not blocked, Zoom Phone is ready for use within your network.
However, despite the fundamental simplicity, there are additional networking components to consider as customer environments become increasingly complex.
Firewall
For a list of firewall ports, protocols, and settings, refer to Zoom's support center.
For customers using zero-touch provisioning, also refer to the Poly and Yealink support sites to confirm your devices can communicate with the manufacturer's provisioning servers.
Network Segments
When planning your Zoom Phone environment, be sure to confirm all network segments (e.g., load balancers, firewalls, custom VLANs, etc.) have sufficient network access as defined in our firewall documentation. Failure to grant necessary connectivity from network segments may impact the user, provisioning, or general Zoom Phone experience.
Quality of Service (QoS)
For Quality of Service (QoS) configurations, Zoom supports two approaches for DSCP tagging: Zoom's built-in application-layer DSCP marking and manual DSCP marking.
Zoom's Application-Layer DSCP Marking
Customers can enable Zoom's built-in DSCP marking feature from the Zoom web portal. Once enabled, Zoom Workplace desktop, mobile, and Zoom Rooms apps (version 6.0+), and most Zoom-certified Cisco, Yealink, and Poly IP phones will transmit Zoom Phone audio packets with configured DSCP markings at the application-layer.
Refer to Zoom’s support center for more information on using QoS DSCP markings.
Manual DSCP Markings
For customers using manual DSCP markings, Zoom recommends the following settings, depending on your organization's QoS strategy.
4-Queue QoS Strategy:
Real-Time Flows
EF
46
Transactional / Mission-Critical Data
AF41
26
Signaling (for Real-Time Flows)
CS3
24
Best Effort
DF
0
12-Queue QoS Strategy:
Network Control
CS6
48
Real-Time Telephony
EF
46
Broadcast Video
CS5
40
Multimedia Conferencing
AF41
34
Real-Time Interactive
CS4
32
Multimedia Streaming
AF31
26
Signaling (for Real-Time Flows)
CS3
24
Transactional / Mission-Critical Data
AF21
18
Management / OAM Traffic
CS2
16
Bulk Data
AF11
10
Scavenger Class
CS1
8
Best Effort
DF
0
Virtual Private Networks (VPNs)
Zoom Phone is supported over a Virtual Private Network (VPN) connection; however, it is important to note that these connections can reduce call quality, extend latency time, and significantly impact your VPN's bandwidth utilization.
Zoom Recommendation
For the best user experience and call quality, split tunnel all Zoom-related traffic outside your company's VPN. Failure to split-tunnel traffic may overwhelm your VPN's bandwidth and impact the user experience.
DHCP Options
DHCP options 66 and 161, if enabled, can interfere with zero-touch provisioning (ZTP) on some devices. Customers are encouraged to leave these options unconfigured if using ZTP extensively, or if using multiple phone device manufacturers within the network.
Last updated
Was this helpful?