FAQs on Zoom Phone Support for Web Proxy Server

Many organization plans for the web proxies aloof of the corporate environment which assists them in outbound internet traffic maintenance. Associated with the corporate workloads, these administrators can have workers remotely which they can use as a web proxy for securing the work terminal.

What are web proxies? 

These web proxies are characterized as extra components for testing performance-related issues and checking the traffic for real-time apps such as jitter, introducing latency in exceptional network congested situations. 

Zoom suggests the acceptance of real-time traffic on the web proxy ensuring direct traffic flow to the zoom data center by the client via the corporate firewall. In case you fail to permit the zoom traffic then it is suggested to permit the UDP traffic via the web browser. But in that situation, it would lead to the introduction of jitter and latency and would erode the user experience. 

 

While using Zoom Phone, will I require the web proxy server? 

 

Based on the real-time of the zoom phone, do the end-user these web proxies can provide the sub-optimal experience. For the zoom Phone since all traffic gets encrypted therefore the web proxies would fail to have it more secure. Considering this, the reasonable way would be while using or deploying the zoom phone to avoid the web proxies. 

When should you ignore the web proxy servers while using the zoom phone? 

Using the VoIP or standard-based Voice over Internet Protocol would produce the best in class voice services. To the conventional on-premise PBX solutions, Zoom Phone would provide a safe and trusted option. Through the encrypted usage of the PKI certificate and TLS.2 and SIP or Session Initiation Protocol, the call setup signaling and other In-call features can be served. ( Those PKI certificates are issued by the trusted commercial certificate authority). Zoom utilizes the UDP for routing the voice traffic that has been encrypted for SRTP usage along the AES  Advanced Encryption Standard 256-GCM profiles. It would make sure that the unknown parties won’t eavesdrop on phone conversations. 

Way of securing the zoom phone traffic in the absence of a web proxy server. 

Zoom would suggest permitting the destined traffic to the data centers of zoom for guaranteeing the zoom users with an optimal experience. This means without having a web proxy, directly routing. 

For ensuring that the allowed data has been protected, Zoom would take the following steps-

• Three broad kinds of traffic can be generated by zoom clients- 

• • Media– It comprises the original voice stream about which the conversation is included. 

• Configuration– for provisioning files or downloading the firmware. 

• Signaling– can be utilized for teardown and the call setups. 

 

• The secure real usually encrypts the media traffic: The confidentiality, RTP traffic replay protection, and message authentication has been maintained by the transport protocol. 
• The industry-standard encrypted technology efforts for encrypting comprehensive traffic from the zoom clients. For maintaining traffic privacy with TLS version 1.2 then it would restrict the probability of tampering, eavesdropping, or data forging. 
• To the IP addresses and ports, the traffic from the zoom client would be permitted. Traffic generally begins from outbound zoom clients to the data center of the zoom. It restricts firewall ports that would be required to get opened for the inbound zoom traffic. 
• From the HTTPS channel, you can download the firmware and configuration files. As this traffic is not real-time traffic therefore these would get transverse as a web proxy. 
• Within the range of the datacenter, zoom ensures high-security standards. Based on the requests, postural security is stored in Zoom reports (SOC2). there are initiatives like third-party audits, for guaranteeing the zoom team’s promise of high-security postures.