Zoom Video Communications operates a distributed, cloud-native video conferencing application where real-time meetings are managed across 17 co-located data centers. In addition, non-real time services are hosted in Azure and AWS.
If you are using the Zoom public cloud, from an end-user perspective the point of presence you will use depends on the location you are connecting from and the availability of the application in the closest POP. Therefore, before you get started, we recommend you collect and examine a packet capture of clients from different regions in your organization when they first connect to a zoom meeting to identify the most common IP subnets you are directed to. In the packet capture, look for DNS queries and responses with “mmr” in the name. (multimedia router)
Optional: The Zoom BGP ASN is AS30103 https://bgp.he.net/AS30103#_asinfo
You can optionally examine the IPv4 prefixes and look up the DNS records to identify other “mmr” DNS records in the subnet.
Using the VoIP MOS template:
Once you have identified a multimedia router DNS record or IP, you will use this in your test configuration. You can test either port TCP Port 443 or TCP Port 8801.
You may decide to create more than one test for the various locations your users are connecting from.
The MOS Score will be computed according to the ITU-T G.107 model as described here - https://help.capenetworks.com/en/articles/1927416-skype-mos
In addition to end-user monitoring, you can also subscribe for status updates from Zoom directly - https://status.zoom.us/