The Ensura Command & Control platform (http://www.ensuracc.com/) manages live and recorded video, audio, and data flows, and shows simultaneous live and recorded views in a single window. The system provides server-side and sensor-side Video Content Analytics for all video channels, displaying triggered alerts from any 3rd party end-element.

The system supports biometric and face recognition modules, ANPR systems, Access Control solutions, Security and Failsafe platforms. Open-ended and integration-agnostic, additional systems can be rapidly and effectively integrated into an Ensura deployment.

Ensura supports event-driven triggering of activities throughout the system, and supports definition of predefined scenarios for management of routine and emergency events.

Ensura enables users to manage multiple remote sites using a single client interface, displaying real-time and archived data of all monitored sites concurrently.

Ensura uses its Sensor Server to receive data from the Meshlium devices over HTTP requests.


  • Server: The IP address or the URL of your Ensura Sensor Server.

  • Port: The port number on which the Ensura Sensor Server is listening for connections.

  • Client Key: The identifier that the Ensura Sensor Server is configured to accept information from.

  • Log Level: This is the log level used by the cloud connector within the Meshlium device. Should be 0, except for debugging purposes.

This data will be provided by the administrators of the Ensura platform.

Controlling synchronization

The synchronization will be done for all data that has not been synchronized in the Sensor Parser table each time. You can start and stop the data synchronization to the Ensura Sensor Server. In the interface you can see an indicator of whether the status service is running or not. If you click on "Start", the synchronization will begin.

You can stop the synchronization at any moment clicking on the "Stop" button.

Last updated