The CP52-E PTZ camera uses WebRTC (Web Real-Time Communications) to achieve ultra-low latency for both streaming and camera controls, from anywhere in the world. The expected latency should be around 0.5 seconds when the camera has properly established a WebRTC connection. However, there are some instances where the WebRTC connection might fail due to networking issues or firewall configurations. Below is a guide explaining how to achieve the best performance and lowest latency for the CP52-E PTZ camera through the use of WebRTC.
How do I know if WebRTC is not working?
If you are experiencing a latency of around ~2 seconds, WebRTC has most likely failed. You will be able to easily determine this by looking at the video feed’s layover UI in Command. If you notice an orange exclamation mark (see image below) at the top of the CP52-E’s video feed, this indicates that the camera was unable to establish a WebRTC connection.
Verkada devices need to communicate with specific domains to provide you with a full-featured experience. For the CP52-E PTZ, the following domains will need to be accessible by the camera in order to establish a WebRTC connection:
*.control.verkada.com - TCP+UDP/443
*.pyramid.verkada.com - TCP+UDP/443
*.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
*:4100 - TCP/UDP on LAN (only required for local streaming)
*.kinesisvideo.us-west-2.amazonaws.com - TCP/443
*.kinesisvideo.us-west-2.amazonaws.com - UDP/443
*.us-west-2.compute.amazonaws.com - TCP/443
*.us-west-2.compute.amazonaws.com - UDP/443