Configure general event handling, Generate alarms based on analytics events, Test a generic event – Milestone M50 User Manual

Page 114

Advertising
background image

Milestone Husky M30/M50

Administrator's Manual

www.milestonesys.com

114

Advanced configuration

3. Click OK.

4. Save your configuration changes by clicking Save in the yellow notification bar in the upper-

right corner of the Management Application.

You can use a single event for activating more than one output. You cannot delete associations, but
you can change your selections or select None in both columns as required.

Configure general event handling

Before configuring events of any type, configure general event handling, such as which ports
Milestone Husky product should use for event data. Normally, you can just use the default values, but
it is a good idea to verify that your organization is not already using the ports for other purposes.

1. In the Management Application's navigation pane, expand Advanced Configuration, right-

click Events and Output, and select Properties.

2. Specify required properties (see "Ports and polling" on page 116). Your system comes with

two simple schedule profiles, Always on and Always off, which you cannot edit or delete. If
these do not meet your needs, you can create any number of customized schedule profiles for
each camera. You can reuse a customized schedule profile for more than one purpose if you
want to.

3. Save your configuration changes by clicking Save in the yellow notification bar in the upper-

right corner of the Management Application.

Generate alarms based on analytics events

Generating alarms based on analytics events is normally a three-step process:

1. Enable the analytics events feature and set up its security. A list of allowed addresses can be

used to control who can send event data to the system and on which port the server listens.

2. Create the analytics event, possibly with a description of the event, and test it.

3. Use the analytics event as the source of an alarm definition (see "Alarms definition" on page

182).

As indicated, to use VCA-based events (see "VCA" on page 204), most often a third-party VCA tool is
required for supplying data to Milestone Husky product. Which VCA tool to use is entirely up to you, as
long as the data supplied by the tool adheres to the applied formatting rules described in the Milestone
Analytics Events Developers Manual. Contact Milestone for more details.

Test a generic event

If you have added a generic event, a quick and easy way to test your generic event is to first set up an
event notification and then use Telnet to send a small amount of data which triggers the generic event
and in turn the event notification.

For this example, we have created a generic event called Video. Our generic event specifies that if the
term video appears in a received TCP data package, this should trigger the generic event. Your
generic event may be different, but you can still use the principles outlined in the following:

Advertising
This manual is related to the following products:

M30