Native Integration Available

This is a Sureview Enterprise only integration requires a Class 1 License and a Device Server. Please contact your account manager for more details.

Supported Features

• Live  Video
• Output Control
• Get Config
• Alarms

Requirements

Package Requirements

The following packages will be deployed by your SureView Engineer

• Dynamic Integration 1.5.2.6036 (or above)
• SureViewEnterpriseHTTPReceiver
• CC-DEVICE-AxisDynamicIntegration

Important: This integration is for SureView Enterprise only. SureView Response SaaS is currently not supported.

Model/Version Tested against:

AXIS P3277-LV Dome Camera
AXIS OS version 12.5.68

Manufacturer License Requirements

N/A - No additional manufacturer license required

Network Requirements

Note: If using HTTPS you must set the Axis Extra Value in Sureview to protocol=https; 

This option only works if the camera presents a certificate the device server trusts. A self-signed certificate fails outright and doesn’t fall back to HTTP

Permission Requirements

At least Operator permission group with access to all Cameras and Outputs that are needed.

Sureview Device Setup

The following Device Setup can be used with Get Config. 

Configuration (ExtraValue) options

Multiple ExtraValue options can be included by using a ; separator e.g.

protocol=https;rtspport=5559;output_pulse_ms=500;virtual_inputs=1

Cameras

Camera fields will be automatically populated by Get Config. There is only ever one camera per Axis device (IP camera)

Outputs

Output fields will be automatically populated by Get Config
 

Note: Get Config can’t detect whether an output drives a door, or which actions it supports. After Get Config, set the Relay Type (Output or Door) and tick On/Off and/or Pulse as required.

Alarm Points

Alarm points need to be added manually. These are not returned by Get Config

Axis Alarm Setup

Step 1 - Set up the HTTP Alarm Recipient 

Log in to the Axis Camera administrator interface and navigate

1. System
2. Events
3. Recipients
4. Add Recipient

From here enter the following fields

<receiverhost> is the host address (IP or DNS address) of your Sureview Server(s)

<ServerID> can be found on the Device Setup page in SureView.

Step 2- Set up your Alarm Rules

Log in to the Axis Camera administrator interface and navigate

1. System
2. Events
3. Rules
4. Add Rule

What to enter in the Body

The body is a short message in JSON format that tells SureView which alarm point has been triggered, and what text to show the operator.

Example: an alarm point in SureView has the Extra Value 3f2b9c1e-8d4a-4e7b-9a61-2c5d0f7e1b43. The body for its rule would be:

{"eventType":"MotionDetected","source":"3f2b9c1e-8d4a-4e7b-9a61-2c5d0f7e1b43","name":"Gate 1 line crossing","description":"Object Analytics"}

When writing the body, check the following:

• Copy the Extra Value from SureView rather than retyping it. If source doesn’t match exactly, the alarm still arrives, but it isn’t linked to the alarm point and none of its automations run.
• Use straight double quotes ("), not curly quotes. Text pasted from Word or email often converts them, and the message then can’t be read.
• Each rule needs its own alarm point with a different Extra Value. Two rules with the same source both raise alarms on the same alarm point.

When the rule is saved, check Full recipient URL on the action. It should end in /receiver/<ServerID>, where <ServerID> is the ID of this camera’s server in SureView.

Sureview Alarm Event Types

Axis does not have any pre-loaded Alarm Event Types but you can add your own in the "Event Configuration" setup in Sureview.

Ensure that any Event Types that you configure have the "Event Code" set to match exactly with what you are sending in the Axis alarm

Sureview Alarm Text

Axis alarms being received in sureview will use the format below 

[Sureview Event Type] - [Alarm Point Title] - {name} | {description} |

e.g.

Motion - Gate 1 - Gate 1 line crossing | Object Analytics |

Troubleshooting

Outputs

Device worker log:

A healthy request:

Requesting... OutputPulse
Replaced URL: http://<camera>/axis-cgi/io/port.cgi?action=2%3A%2F1000%5C
Status Code: (OK) OK
Authentication-Info: rspauth="..."
rspauth is worth looking for specifically — Apache only returns it when the client's digest response verified, so it distinguishes real authentication from a 200 that happened for some other reason.

Poll the port to confirm it physically moved; a 1-second pulse is too brief to catch otherwise:

curl -s --digest -u <user> 'http://<camera>/axis-cgi/io/port.cgi?checkactive=2'

HTTP Alarms