Alertus Technologies is a third-party vendor that provides beacons, signage, and other delivery options for your alerts. A connector for Alertus can be added upon request through your Omnilert Account Manager. This connector will allow Omnilert to push messages to your local Alertus server using Alertus' built-in API.
Basic Alertus Configuration
When added, Alertus will appear on the Endpoints >> Inactive list.
Before completing this portion of the setup, you may need to whitelist Omnilert's IPs. (See bottom of this article for info.)
Click on Alertus and then click the Configuration tab. need to enter your Alertus server's "MiddlewareBasic" URL into Omnilert's configuration screen.
The URL usually looks similar to this example:
Of course, your Alertus server's URL will vary depending on your Alertus server's setup. If no FQDN name is assigned to your Alertus server, Omnilert can connect via an IP address, as well.
The "Include Subject" option can be enabled to include the "subject" portion of alerts being sent to Alertus. Typically, the message subject is not needed for Alertus' message displays, but this setting can be adjusted to meet your preference.
Alertus Settings once connected: Setting Default Profile and Duration
Once your Omnilert service can connect to the Alertus box, it will pull your "Alertus profiles" which can be selected and need to be set in Omnilert's configuration.
Reload the saved configuration screen and you'll see new settings for a "Default Profile" and "Duration".
Set the proper profile (usually "Emergency") and an appropriate duration for the alerts on alertus (usually "10") according to your needs.
Then click Update configuration and make the service active.
IMPORTANT! Firewall Whitelisting and Alertus allowed IPs:
In order to connect Omnilert to Alertus, you will need to whitelist Omnilert's IPs. Please contact firstname.lastname@example.org or your Omnilert account manager for the latest IP listings regarding delivery to Alertus.
On the Alertus server*:
There is a line in the
c:\Alertus\conf\AlertusMiddleware.impl.properties file that restricts the Alertus API based on IP addresses.
It is the line:
soap.alertusMiddlewareBasic.allowableIPs = 127.0.0.1;x.x.x.x;y.y.y.y;z.z.z.z
...where the x's, y's, and z's are a semicolon separated list of allowed IPs
Please verify that this list includes the Omnilert IPs and then restart the Alertus Tomcat service on the Alertus server.
*These instructions are provided for convenience to help you configure Omnilert to connect to Alertus and deliver alerts to your Alertus server.
Please contact Alertus directly at https://www.alertus.com/support/ for the latest documentation and support regarding Alertus itself.