Recently viewed tickets

Log out

SiteManager GUI - GateManager & Alerts

Based on the settings of this menu, the SiteManager can send alerts based on external triggering of its digital Input ports, Serial port or Ethernet ports.

Depending on the SiteManager model and the GateManager configuration, alerts can be sent as SMS or Email directly from the SiteManager or via the GateManager.

When using the GateManager as alert gateway, the SiteManager will queue SMS and email alerts if GateManager connection is lost, but queued alerts will be discarded if the SiteManager is rebooted.

Note: You must have created a GateManager Agent for each of the devices that need to send Alerts triggered by TCP or UDP, as only requests from known devices are accepted by the SiteManager.

Note: Each alert must fit within a single SMS unit, so alert texts should not exceed 70 characters.

The following parameters are available to setup the alerts:

  • Alert Mode
    Here you can enable local management of the Alert logic in addition to the Alert system managed via the GateManager administrator Portal. Note that disabling Alert mode here will not affect the Alert definitions created in the GateManager administrator Portal.

    Also note that if disabling Alert Mode on a SiteManager with integrated modem, the SiteManager will not accept incoming SMSes for reading from the Serial port or the Ethernet port (For details on this topic refer to the separate guide "Working with SMS alerts"). Incoming SMSes related to SMS Wakeup configured under System > Uplink2 will work independent of this parameter.

  • Alert Identification
    By default, the identity of the SiteManager (Appliance name) and the agent (device IP address) is added to the alert text, so that the recipient can easily identify the SiteManager and device that sent the alert, and connect to it from GateManager or LinkManager.
    If you have other means of identifying the device (e.g. if alert text itself identifies the device, or by checking who sent the SMS), you can specify that only some alert triggers should add the device identification: INPUT (for input ports), Agents (using UDP or TCP), Serial (via Serial SMS modem), or any combination of these can be selected here.

  • Email Alert Gateway
    Here you can define if email alerts should be sent directly from the SiteManager or using the GateManager server as a mail relay.

    Selecting SiteManager as gateway does not require a GateManager connection for the alert to be send, but requires the appropriate SMTP settings to be configured via the [SMTP>>] button. Note that you must ensure that the entered SMTP settings correspond to the active Uplink Interface.

    Selecting the GateManager as gateway will use the GateManager as mail service (if the GateManager version supports email alerts). Note that Alerts will have GateManager as sender, so the recipient must determine the sender based on the Alert identification in the email subject or body text.

  • SMS Alert Gateway
    All SiteManagers can use the GateManager as SMS Gateway, provided that SMS services are enabled on the GateManager (Domain > Domain configuration). This will be indicated in the sub-header of the Alerts configuration page in the SiteManager.

    SiteManagers with integrated modems can be configured to send alerts directly via the local modem [ SiteManager ], and will therefore neither depend on an active GateManager connection, nor enabling of SMS services on the GateManager.

    Note that if SMS Alert Gateway is set to GateManager , the SiteManager's integrated modem can still receive SMS messages that can be read on the Serial port or the Ethernet port. For details on this topic refer to the separate guide "Working with SMS alerts".

    Notice: Receiving requests to transmit SMSes in PDU format via the Serial port is not supported when using GateManager as SMS gateway.

The following parameters control how INPUT signals can be used to send alerts.
These settings operates completely independent of the INPUT port assignments on the GateManager > General page.

  • Input N Alert
    Here you can enable sending an alert when an INPUT port changes state, either to ON, to OFF, or both (ON/OFF).

    IMPORTANT: If the status table shows "Toggle GateManager Access" for IN 1, it is not recommended to also define a local Alert action for this Input port, as the GateManager access toggling will have presendence over the local alert action, If defining it as "Alert when ON" and setting the GateManager as Alert Gateway, the alert will not be sent until the GateManager connection is restored. If your intention is to receive an alert when GateManager connection is lost, you should instead create an Alert in the GateManager Portal and associate it for Input 1 for this SiteManager, or define the SiteManager itself as Alert Gateway. If you want to use Input1 for a specific purpose and not for GateManager Access signaling, you can disable "Toggle GateManager Access" under GateManager > General > [More>>].

  • Alert Recipients ( )
    Here you specify the mobile number(s) - or <>-bracketed email address(es) - to receive the alert message. Each email address must be encapsulated in <...> brackets. Multiple recipients can be specified by separating them with spaces, comma, or semicolon.

    If you specify multiple recipients, you may even control who receives the alert based on time of day and day of week. See the section on alert schedules below.

  • Alert ON Text
    Here you can specify the alert text sent when the INPUT goes ON (and you have requested an alert for "ON" state).
  • Alert OFF Text
    Here you can specify the alert text sent when the INPUT goes OFF (and you have requested an alert for "OFF" state).

As mentioned above, it is possible to define an Alert Schedule to control which mobile numbers will receive an alert at different times of day and week.
For example, if you have a day-time number 11223344, a night-time number 55667788, and a weekend number 99009900, you can enter the following schedule in the relevant Alert Recipient field. Each of the {...} blocks specify a time frame for the following recipient(s):
{m-f 6:30-17} 11223344 {m-th 17-6:30, fr 17-24} 55667788 {} 99009900
You read this from left to right as follows: From monday (m) to friday (f) at 6:30 to 17:00, call 11223344; or from monday to thursday (th) at 17 to 6:30 next morning, and on friday from 17 to midnight, call 55667788; if no preceding numbers are called, then call 99009900.
As you can see the last {} form specifies "the remaining periods".

Some details:
• Time-of-day is specified as hour or hour:minute, using 1 or 2 digits: H, HH, H:MM, HH:MM
• 24 hour clocks are used, 24:00 equals 0:00 the next day.
• Weekdays are specified as one or two letters: m mo tu w we th f fr sa su
• Ranges are specified as m-f and lists as m,w,f-su
• Times and dates follows the UTC timezone (unless you specify otherwise on System > Time).

The following parameters control how Ethernet attached devices (with a defined GateManager Agent) can send Alerts:

  • Agent Alerts TCP Port
    The TCP port at which the SiteManager receives TCP requests from Agents to send an Alert. Enter 0 to disable TCP alerts.
  • Agent Alerts UDP Port
    The UDP port at which the SiteManager receives UDP requests from Agents to send an Alert. Enter 0 to disable UDP alerts.
  • Agent Alerts Recipients
    The default mobile number(s) and email address(es) to which Agent requested alerts are sent - if a request does not itself contain a mobile number or email, or specifies mobile number 0.
  • Agent Alerts User Name
    If non-empty, the Agent Alert request must include this user name. If empty, any user name is accepted.
  • Agent Alerts Password
    If non-empty, the Agent Alert request must include this password. If empty, any password is accepted.

The following data formats are accepted to send an Alert:

  • /UserName/Password/Recipient/AlertText
    Send AlertText to the specified Recipient, a mobile number or a <>-bracketed email address. UserName and Password must match the configured settings above.
  • /Recipient/AlertText
    Send AlertText to the specified recipient (mobile number or bracketed <email> address - works only if the configured UserName and Password settings are empty.
  • Compatibility formats
    In addition to the native formats defined above, a number of complatibility formats are also supported. Please contact Secomea for information about compatibility with a specific type of equipment.

Serial Port Alerts
You can also send an SMS or Email via the serial port by setting it to use the "SMS Modem" protocol (see Serial Port ).
Then you can use a standard "AT+CMGS= recipient CR message ctrl-Z" command to send an SMS.
You can also use a custom "AT+SMS= recipient / message CR" command; use \<CR> to insert a linebreak in the message.
The recipient can be a mobile number or a <>-bracketed email address.

Creation date: 11/12/2019 13:23 (skr@secomea.com)      Updated: 16/01/2020 10:37 (skr@secomea.com)