RC-E User Manual
Management Client (RC-E Manager)
0
, you should therefore carefully consider whether you want to use the notification profile in rules which
are likely to be triggered frequently.
Number of images:
Specify the maximum number of still images you want to include in each of the notification
profile's e-mail notifications. Default is five images.
Time btw. images (ms):
Specify the number of milliseconds you want between the recordings presented on the
included images. Example: With the default value of 500 milliseconds, the included images will show recordings
with half a second between them.
Embed images in e-mail:
If selected (default), images will be inserted in the body of e-mail notifications. If not,
images will be included in e-mail notifications as attached files.
Example
Example of e-mail notification with embedded images. Note that the size of the embedded images will
depend on individual camera settings.
Time before event (secs.):
This setting is used to specify the start of the AVI file. By default the AVI file will
contain recordings from 2 seconds before the notification profile is triggered; you are able to change this to the
number of seconds you require.
Time after event (secs.):
This setting is used to specify the end of the AVI file. By default the AVI file will end 4
seconds after the notification profile is triggered; you are able to change this to the number of seconds you
require.
Frame rate:
Specify the number of frames per second you want the AVI file to contain. Default is five frames per
second. The higher the frame rate, the higher the image quality and AVI file size.
Manage User-defined Events
User-defined events are events which are custom made to suit your system. Like other events, user-defined events
can be used in rules (see "Manage Rules" on page 133) in order to trigger actions. Thus, when a user-defined event
occurs, a rule can trigger that one or more actions should take place on the RC-E system.
Example:
When user-defined event 37 occurs, PTZ camera 224 should stop patrolling and go to preset
position 18.
Through roles (see "Manage Roles" on page 147), you define which of your users should be able to trigger the user-
defined events; see Specify Rights of a Role (on page 150) for more information.
User-defined events can be used in two ways, simultaneously if required:
For Providing the Ability to Manually Trigger Events in the Ocularis Client
In this case, user-defined events make it possible for end users to manually trigger events while viewing live
video in the Ocularis Client. Thus, when a user-defined event occurs because it is manually triggered by an
Ocularis Client user, a rule can trigger that one or more actions should take place on the OnSSI RC-E
system.
For Providing the Ability to Trigger Events through API
In this case, user-defined events can be triggered from outside the surveillance system. Using user-defined
events this way requires that a separate API (Application Program Interface; a set of building blocks for
creating or customizing software applications) is used when triggering the user-defined event. Authentication
through Active Directory is required for using user-defined events this way. This ensures that even though the
user-defined events can be triggered from outside the surveillance system, only authorized users will be able
to do it.
Also, user-defined events can via API be associated with meta-data, defining certain devices or device
groups. This is highly usable when using user-defined events to trigger rules: you avoid having a rule for each
On-Net Surveillance Systems, Inc.
143
