SmartSights Feature Requests
Control Center installed on a remote system (for the purposes of the Announcer function) should reconnect automatically if it's connection to the Win911 system(s) is lost. For example, if the system hosting the Win911 system is rebooted or services restarted. Currently it does not, and you need to remember to manually go to every remote install of Announcer (Control Center) and shutdown and restart Control Center. This is problematic as even with Active and Standby Win911 system and automatic failover it requires manual intervention on the remote Announcer system to recover in the event a Win911 system is lost or restarted.
As an example:
Win911 System 1 - Active
Win911 System 2 - Standby
Remote Announcer configured with a connection to both Win911 systems (Primary/Secondary - only announce from Active system)
Say System 1 is lost or restarted (patches, failure, or ...). Failover Utility will set System 2 Active and the Remote Announcer will use System 2 as the alarm source.
When System 1 is restored and becomes Active again the remote Control Center (Announcer) will never restore a connection to System 1 or pick up that System 1 is now the Active system again unless the remote control center is restarted manually.
If at any point in the future System 2 is lost, the remote Announcer will have no active connection to an alarm source.
Oddly, this behavior of the remotely installed Control Center differs from the behavior of the Control Center instance installed locally on the Win911 system which will re-establish the connection automatically.
This was submitted as a support request thinking this was a bug or an issue with our setup, but the response was that this is by design, and I should post here as a feature request.
