The SecAst executable has started, but a critical connection to Asterisk has not been successful. This in turn is preventing SecAst from protecting the Asterisk server.
A delay in starting Asterisk, or a delay in Asterisk responding to SecAst may be the root cause, and no action is needed as the connection will succeed momentarily. Depending on the alert settings, a successful start email may be forthcoming. If not, examine the secast.log file for clues as to what Asterisk connection has been unsuccessful. The most common cause is that the AMI is unavailable because either the Asterisk is not started (yet), or the AMI connection settings mismatch.
