Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This article will walk you through how to use Generic Alarms. These types of alarms are created based on the incident number or device that gets passed to the API that triggers the alarm. An example of when these alarms could be useful would be for stolen device alerts from Cisco Prime software, or ITS-NetworkingAlerts system. 

If you call an alarm with the same incident within 30 minutes of the first alarm, it will be rolled up into a dispatch log. 



Setting up Alarm Permissions 

Before admins can use alarms in the system they will need to have the proper dispatch permissions added to their administrative role. 



Select the permissions you wish to add to the role and click Save Permissions at the bottom when you are finished. 


How Generic Alarm Get Pushed to the System

Unknown Student/Staff Number

One way for a generic alarm to hit the system would be if a people alarm was sent in with a student or staff number that is not in the system, the message will be provided from the access point as well as any other provided details.

Cisco Prime or IT_NetworkingAlerts Systems

The second way would be to utilize systems such as the Cisco Prime or ITS-NetworkingAlerts system which push email to our system that will get parsed and sent out as a generic alert. Some of our clients are utilizing these systems for stolen devices which have the systems push us the incident and MAC Address. Just like people and plate alarms, if you submit an alert on the same MAC address or Incident within a 30 minute time frame they will all be rolled up into a single dispatch log that can then be acted on. If a valid incident is pushed along to the system the incident will be associated to the dispatch log. 


Dispatch Logs 

Once you have received the alert the system automatically create the dispatch report and link the provided incident if there was a valid incident passed to our system. See more on 

  • No labels