REST v3 WebRTC via relay/proxy
In Progress
Hi,
We are trying to open a WebRTC Tracker WebSocket connection to play a camera stream in a webpage with as low latency as possible. We are doing this through the cloud proxy, as the webpage will be accessed by users from outside the LAN of the NxWitness server
The WebSocket URI looks like this:
wss://{systemId}.relay.vmsproxy.com/rest/v3/devices/{deviceId}/webrtc
What we need to know is, does each websocket connection created this way incur additional upload bandwidth on our PC running NxWitness server? Or is the video data only streamed up to NxCloud once, and then each WebSocket connection gets video stream data from NxCloud?
The reason we need to know is because our NxWitness server has bandwidth constraints, so if each concurrent viewer on our webpage incurs additional bandwidth, then this isn't a viable solution for us
Thank you
-
Each WebRTC stream generates a new connection/request, which means the bandwidth usage on the MediaServer will accumulate accordingly. This is the design of the Nx MediaServer, and you may need to address this scenario.
If the customer prefers to access the footage in their own way from anywhere, likely this is a challenge or trade-off that users must consider and manage.
Thank you for your understanding
-
Hi Nathan Sibai,
Yes, it is the same case.
Please sign in to leave a comment.
Comments
3 comments