[KBA-00921] Cannot acknowledge alarms triggered by Pelco ASCII commands in Omnicast™
This article explains why you are unable to acknowledge Omnicast™ alarms triggered by Pelco ASCII commands sent on a serial port.
If an alarm is triggered by a Pelco ASCII command sent on a serial port, you are unable to acknowledge it using Omnicast™ or other Pelco ASCII commands.
When an alarm is triggered by a Pelco ASCII command, the source GUID is incorrectly set and causes corruption in the database.
Restarting the Directory service will acknowledge currently activated alarms, but the issue will return the next time an alarm is triggered by a Pelco ASCII command.
A hotfix is available for Omnicast™ 4.7 SR1 HIP2 (HF1188). Contact the Genetec™ Technical Assistance Center to obtain it.
This issue is fixed in Omnicast™ 4.8 SR2.