Avigilon Hirsch Velocity Integration - Manual (Page 16)

Avigilon Control Center System Integration Guide with Hirsch Velocity
13
Troubleshooting
This section contains solutions to issues that may appear in the Avigilon Hirsch integration. If the
suggested solutions do not resolve your issue, contact Avigilon Support at [email protected] .
Alarms are Not Mapping Correctly
Avigilon alarms are mapped to the wrong Velocity alarms, even though the names for both
alarms are correct.
Check the following:
• Are you expecting Velocity alarms to display their customized descriptions or their
predefined names?
• If you are expecting to see the alarms’ customized descriptions, make sure the
Velocity software is set to display event level description customizations and the
Gateway configuration application is set to use customized descriptions. See
Velocity Alarm Configuration on page 6 and Mapping Alarms on page 9 for
more information.
• If you are expecting to see the alarm’s predefined names, make sure the
customized description options have not been enabled.
• Are there any typos in the parameter names?
• If you had to specify parameters for the alarm mappings, check if the
parameters contain any spelling errors or typos and remember that the values
are case sensitive. The alarms would map if the parameters were entered
incorrectly but the alarm may not be triggered because the alarms will be
looking for a device that may not exist.