# Networking

Due to Zoom Contact Center’s cloud-based architecture, configuring your network for the service is relatively simple. Fundamentally, users need two key factors to begin using the service: a working internet connection and open network ports. So long as users can successfully maintain an active connection with Zoom Contact Center data centers and the necessary ports are not blocked, Zoom Contact Center is ready for use within your network.

However, despite the fundamental simplicity, there are additional networking components to consider as business environments may involve more complex components. The following sections outline some of these scenarios.

### Firewall

For a list of firewall ports, protocols, and settings, refer to [Zoom’s support center](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0060548#contact-center).

### Network Segments

When planning your Zoom Contact Center 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](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0060548#contact-center). Failure to grant necessary connectivity from network segments may impact the user, provisioning, or general Zoom Contact Center experience.

### Virtual Private Networks (VPNs)

Zoom Contact Center 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.

{% hint style="warning" %}
**Zoom Recommendation**

For the best 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 quality.
{% endhint %}

### Bandwidth Requirements

The amount of bandwidth required for Zoom Contact Center varies by channel and quality. The following table outlines expected consumption on a per-user basis for video and audio. All values are listed in bits (not bytes) per-second.

| Media                                 | Uplink      | Downlink    |
| ------------------------------------- | ----------- | ----------- |
| High-Quality Video (<720p)            | 1.0 mbps    | 600 kbps    |
| 720P HD Video                         | 2.6 mbps    | 1.8 kbps    |
| 1080p HD Video                        | 3.8 mbps    | 3.0 mbps    |
| Gallery View 25-User (Receiving)      | 2.6 mbps    | 4.0 mbps    |
| Screen Sharing Only (No Video)        | 50-75 kbps  | 50-75 kbps  |
| Screen Sharing only (Video Thumbnail) | 50-150 kbps | 50-150 kbps |
| Audio VoIP                            | 60-100 kbps | 60-100 kbps |

Refer to Zoom’s support center for more information on [bandwidth requirements](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0060748).

### For Wi-Fi-heavy companies, a Wi-Fi site survey might help

Due to the nature of wireless connectivity, factors such as signal interference, coverage limitations, and bandwidth fluctuations can introduce quality issues, leading to potential disruptions or degradation in communication reliability and clarity. For this reason, businesses that are heavily reliant on Wi-Fi connectivity are encouraged to conduct wireless site surveys, as this can help ensure that wireless access points and antennas are optimized for your facilities, reducing the likelihood of quality-related problems.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://library.zoom.com/business-services/zoom-contact-center/zoom-customer-experience/overview/networking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.