This guide will show how to integrate the alarms from the Azeti Engine to a Cisco Video Surveillance Management server.
Add the Subtypes. The subtypes names have to be the same as the sensor id on the Azeti Site Controller that will send the events. Add as many subtypes as sensors.
No more subtypes can be added after that, so make sure that all sensors are there. |
You will now find the required Trigger URL directly in the camera. Choose the camera -> Streaming, Recording and Events and you see the link at the bottom within Camera Events.
Copy the URL, e.g. http://10.59.14.101/Event/SoftTrigger/primary/1e90a1a9-eb0d-476e-b871-03b420023a96YXpldGlTaXRlQ29udHJvbGxlcg%3D%3D, you can then add your subtype and other meta fields and invoke it in your browser. A successful execution return Status Code 0. With aboves example it would turn out in the URL http://10.59.14.101/Event/SoftTrigger/primary/1e90a1a9-eb0d-476e-b871-03b420023a96YXpldGlTaXRlQ29udHJvbGxlcg%3D%3D?subtype=Vibration%20Alarm with the successful response.
|
You can test the created soft-trigger manually by invoking the created URL in the browser. It must return a Status Code 0, otherwise there might be an issue.
Login to the Cisco Cloud as the organizations Administrator.
You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|