Page History

...

Connect to ws://[user_name]:[password]@[IP - address]:[port]/[prefix]/events.
Send a JSON command to subscribe on events generated by to event notification from the specified cameras cameras (see Get list of video cameras and information about themtelemetry devices for specified video source). This This subscription allows you to receive all the events shown listed in the table below.
Code Block
{ "include": ["hosts/Server1/DeviceIpint.1/SourceEndpoint.video:0:0", "hosts/Server1/DeviceIpint.6/SourceEndpoint.video:0:0"], "exclude":[] }
include – —subscribe to the events receivingevent notification;
exclude – —disable the events receivingnotification.

The response will contain the following JSON:

...

List of event types and camera states:

Event type	Description	States
devicestatechanged	Camera state	signal restored

–

—connected, signal restored

signal lost

–

—signal lost
alert	Alarm	No states
alert_state	Alarm state	processing

–

—the alarm is being processed
closed

–

—alarm is processed
reaction

–

—alarm is initiated
detector_event	Detection tool triggering	No states
camera_record_state

Archive record state

State of recording to archive

on

–

—the camera is recording to the archive
off

–

—the camera

is not

isn't linked to the archive
gray

–

—the camera is linked to the archive, but

is not

isn't recording

Info

title	Note

If the camera is disabled in Axxon One, no events are received from it using WebSocket, including the signal lost event.

Example of a message:

Code Block

objects: [{name: "hosts/Server1/DeviceIpint.1/SourceEndpoint.video:0:0", state: "signal restored",…},…]
0: {name: "hosts/Server1/DeviceIpint.1/SourceEndpoint.video:0:0", state: "signal restored",…}
name: "hosts/Server1/DeviceIpint.1/SourceEndpoint.video:0:0"
state: "signal restored"
type: "devicestatechanged"

Managing the subscription to event notification about changes in camera configuration

Using WebSocket, you can subscribe and unsubscribe to event notification about changes in camera configuration using the track and untrack commands.

Example of subscription to event notification about changes in camera configuration:

Code Block
{ "track": ["hosts/Server/DeviceIpint.1"] }

Example of a message after subscription:

Code Block

{
   "objects" : [
      {
         "name" : "hosts/Server/DeviceIpint.1",
         "type" : "itemstatuschanged"
      }
   ]
}
{
   "objects" : [
      {
         "source" : "hosts/Server/DeviceIpint.1/SourceEndpoint.video:0:0",
         "state" : "off",
         "type" : "camera_record_state"
      }
   ]
}
{
   "objects" : [
      {
         "name" : "hosts/Server/DeviceIpint.1",
         "type" : "itemstatuschanged"
      }
   ]
}
{
   "objects" : [
      {
         "source" : "hosts/Server/DeviceIpint.1/SourceEndpoint.video:0:0",
         "state" : "off",
         "type" : "camera_record_state"
      }
   ]
}

where the type parameter will display the itemstatuschanged value when the configuration is changed.

Example of unsubscription to event notification about changes in camera configuration:

Code Block
{ "untrack": ["hosts/Server/DeviceIpint.1"] }

Example of a response message:

Code Block

{
   "objects" : [
      {
         "source" : "hosts/Server/DeviceIpint.1/SourceEndpoint.video:0:0",
         "state" : "off",
         "type" : "camera_record_state"
      }
   ]
}
{
   "objects" : [
      {
         "source" : "hosts/Server/DeviceIpint.1/SourceEndpoint.video:0:0",
         "state" : "off",
         "type" : "camera_record_state"
      }
   ]
}

Page tree

Versions Compared

Old Version 1

New Version 2

Key

Managing the subscription to event notification about changes in camera configuration