WebRTC is not loading when viewing live video streams. You can check this by hovering over the red live button when viewing live streams, there will be a cross by low latency if WebRTC has failed to load:
This can be caused by the following:
-
Firewall ports are blocked
-
The network's NAT device does not support Endpoint-Independent Mapping or does not have it enabled.
-
Keyframe interval of the camera is too high.
-
Bitrate of the camera is too high.
-
Check the required access has been permitted on the firewall (include link to firewall doc):
Table 1. Web RTC/Twilio Stun Servers
US1
US East Coast (Virginia)
34.203.254.0 - 34.203.254.255, 54.172.60.0 - 54.172.61.255, 34.203.250.0 - 34.203.251.255, 3.235.111.128 - 3.235.111.255
US2
US West Coast (Oregon)
34.216.110.128 - 34.216.110.159, 54.244.51.0 - 54.244.51.255, 44.234.69.0 - 44.234.69.127
Ports: 443, 3478 (TCP/UDP), 5349 (TCP/UDP), 10000-60000 (UDP)
Note
A client's IP requires the same port and IP access to utilize WebRTC.
-
Check that your network’s NAT device supports Endpoint-Independent Mapping.
-
Check the keyframe interval on the camera. This should be ~1 second.
-
Lower the bitrate of the camera to 1Mbps or as near as you can without impacting picture quality.
