In ntopng you can now see the flow nature (e.g. The UDP stream can also carry encapsulated RTCP traffic, that on non-Zoom communications is usually reported on a separate UDP flow. Both audio and video sessions use a Zoom-proprietary header before encapsulating real data over RTP. For a single call multiple UDP flows can be active from your system to the Zoom servers. you start with audio, then share the screen), the same UDP flow can carry audio, video and screen sharing. Video, audio and screen sharing data is transported on UDP port 8081.TLS is used to communicate with the Zoom servers for connection setup, char, lifecycle and everything not related to multimedia data.Before we continue this discussion, let’s see how Zoom traffic looks like (you can use this Wireshark): In addition to existing metrics such as bandwidth or latency, interpret correctly Zoom traffic hence to compute traffic quality metrics.įor this reason we have enhanced nDPI, ntopng and nProbe to report comprehensive Zoom traffic statistics and thus be able to better evaluate the traffic quality.Recognise Zoom video, audio, and screen sharing streams (previously they were classified just with a generic Zoom label).Recently we have took advantage of this research work to improve Zoom protocol dissection in order to

DPI toolkits such as nDPI are useful for identifying Zoom traffic for supervising the network bandwidth used by your Zoom calls. As many other cloud services, network administrators need to supervise Zoom network traffic usage. Zoom is a popular platform for video communications and team collaboration.

Zoom video conferencing filter