Direct Streaming
Direct streaming within the YourSixOS platform is an important aspect to optimize a user’s experience. Direct streaming allows the user to communicate with the devices on the local network instead of communicating out to the internet and back again. Direct streaming allows for a very large reduction in bandwidth consumption leading to a better experience for all users on the network.
YourSix also automatically issues SSL/TLS certificates from a globally trusted source every 12 months. This allows a user to stream video directly from a camera without manually issuing certificates and allows for streaming if the internet (WAN) connection is lost.
How
A direct stream in the YourSixOS platform is established once a user can reach the device utilizing the devices local DNS name. The local DNS name is obtained by the platform from the YourSixOS servers.
Value
Direct streaming allows for two main values. First, direct streaming reduces bandwidth by allowing local users to stay on the LAN and still utilize the platform. Second, in the event of a lost internet (WAN) connection, local users are still able to stream live footage and view local recordings. When utilized with a local SD card, YourSixOS allows remote users to access footage that was recorded during the outage.
How to identify whether you are direct streaming
Users can confirm they are streaming directly vs cloud streaming by hovering over the video thumbnail on the player canvas and looking for the green direct streaming icon. The icon will appear beside the camera name and site name in the top left corner of the video tile. If no icon appears then user is streaming via the cloud.
Troubleshooting
Users that expect to see the direct streaming icon but do not should ensure the below item:
- Confirm port 443 is open on the LAN to allow communication between the user and device. If port 443 is closed, then users will not be able to stream direct and the platform will revert to cloud streaming.
- Ensure camera and the user are accessing the platform using the same public IP address. This issue commonly effects networks utilizing SD-WAN.