The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page
Alarm configuration
- Chad Fay
- Jim Staples
How to set up Alarms for Alarm Management in the Avigilon Alta Access system.
Note: Alarm configurations are part of the Alarm Management FAQ, we recommend starting there.
Note: Because of the number of options for configuring alarms, we recommend reviewing them to see which works best for your situation.
Go to Configurations > Alarms
Click the (+) in the top right corner to create a new alarm.
Info: Give your alarm a Name and description, choose your Severity, instructions to the User or Role handling and acknowledging the alarms, and choose if you want your alarm Enabled (default) and/or Silenced.
Â
Assignment: Assign the alarm to a User or Role, and select User or Role. Chech the box if you want to require notes for acknowledgment of alarm.
Â
Camera: Choose the Camera(s) or leave blank if there is no associated camera.
Â
Trigger: Select your Trigger Type. These are based on the Rules Engine.
Â
In the example below I choose Entry, and then pick what Event I want to happen that will trigger the alarm.
I added a filter (optional) so I can filter the event by a user and I select the user because the alarm is specifically set up to see when a user shows up at the office.
You can add more than one filter to narrow down the event.
Schedules (optional): Select the type of schedule you want to create either a one-time event or a repeating event and select your Start time, End time, and Time zone. If a repeating event select the Repeating days, Start date, and the Repeat Until date. You can set up more than one schedule.
Actions: Select the action or actions you want the alarm to take when it is triggered. Relay, Email/SMS, On-screen notification, Webhook, or Lockdown. Then follow the steps for every type you choose. In my example, I selected On-screen notification. Then select the Notification Option(s) and the Send To.
Note: The Action type of webhook in the Alarm Configuration can only be sent to internet-accessible resources.
If your target webhook URL is restricted to the local intranet, you can use Rules Engine to send a webhook using the same triggering criteria as the Alarm Configuration and your webhook URL would point to the intranet resource. As Rules Engine items are executed at the ACU, the webhook will be executed within the context of the ACU’s on-premise local network.
You can set up more than one action for example on-screen notification AND an SMS notification by clicking Add action to configure additional action types.
Â
Related: