Allow servers to cache/proxy camera streams added to a different server
We have created a template to assist users in providing complete and structured information in the Feature Feedback. The template can be copied/pasted and edited by adding the required information before submitting Feature Feedback.
Please keep the bold text in your request and replace the non-bold text between the <> with the information you want to share. This makes it easy to find information for the support teams.
Summary
Server ability to proxy/cache streams locally when cameras are added to a different server
Description
Is there a way to proxy video on a server which is different to the server that has the cameras added to it?
My scenario is
A group of servers at location A have all the cameras added to it. This is due those cameras terminating their network connections here.
A group of servers at location B (this is dynamic and can change) where clients login to view the cameras. The connection between location A and B is metered and low bandwidth.
The servers are within the same NXWitness system.
Is there a way for the servers at location B to pull the video streams once from location A to then distribute to multiple clients at location B. Rather than multiple streams being pulled from location A when 2 clients at location B request the same camera.
Multicast from the camera to location A is not possible.
Business impact of the limitation or the missing feature
Having to plan for high capacity point to point links from Location A to Location B-Z. This is expensive.
Really limits rolling out NXWitness to remote locations which may have low bandwidth.
Restricting the amount of videos that can be watched at one time to less than users can watch currently on the existing VMS
-
this should be addressed in 6.1, you should see public announcements of it soon.
Also see https://nxvms.com/download/betas0 -
Thanks for the update!
Will this be available on both Standard and Enterprise?
0
Please sign in to leave a comment.
Comments
2 comments