RUTM59 Events Reporting

Main Page > RUTM Routers > RUTM59 > RUTM59 Manual > RUTM59 WebUI > RUTM59 Services section > RUTM59 Events Reporting

The information in this page is updated in accordance with firmware version RUTM_R_00.07.11.3.

Summary

The Events Reporting feature provides the possibility to configure rules that inform via SMS or email when certain trigger events occur.

This page is an overview of the Events Reporting section for RUTM59 devices.

Events Reporting Rules

The Events Reporting Rules section is used to manage existing Events Reporting rules and to add new ones. Events Reporting Rules trigger on certain, user specified events and send an SMS message or email to a specified number informing of the occurred event.

All possible trigger events are listed in the table below.

Event	Event subtype
Config change	Informs on changes to the device's configuration. Possible triggers are: Any config change Specific config change
GPS	Informs on when the device has entered or left a user defined geofence zone. Possible triggers are: Entered geofence Left geofence All
Mobile data	Informs on changes to the state of the device's mobile connection. Possible triggers are: Connected Disconnected All
New DHCP client	Informs on new DHCP lease give outs. Possible triggers are: Connected from LAN Connected from WiFi
Ports state	Informs on Ethernet port state (plugged in or unplugged) or speed (100 Mbps or 1000 Mbps) changes. Possible triggers are: Link speed Link state Unplugged Plugged in LAN1 LAN2 LAN3 LAN4 WAN
Reboot	Informs after device reboot occurrences. Possible triggers are: From button From Input/Output From Ping Reboot From wget Reboot From Reboot Scheduler From WebUI From SMS All
Startup	Informs when device startup completed. Possible triggers are: Device startup completed After unexpected shutdown
Signal strength	Informs on signal strength changes. Possible triggers are: - 121 dBm - 113 dBm - 113 dBm - 98 dBm - 98 dBm - 93 dBm - 93 dBm - 75 dBm - 75 dBm - 60 dBm - 60 dBm - 50 dBm All
SMS	Informs on received SMS messages. Possible triggers are: SMS received
SSH	Informs on successful or unsuccessful SSH login attempts. Possible triggers are: Successful authentication Unsuccessful authentication All
Topology changes	Informs on changes to the device's network topology. Possible triggers are: Topology changes
WAN failover	Informs on WAN failover occurrences. Possible triggers are: Switched to failover Switched to main All
WebUI	Informs on successful or unsuccessful HTTP/HTTPS login attempts. Possible triggers are: Successful authentication Unsuccessful authentication All
New WiFi client	Informs on new WiFi clients. Possible triggers are: Connected Disconnected All
FOTA	Informs about a new Firmware update. Possible triggers are: Firmware update is now available

Events Reporting Configuration

The Events Reporting Rules list is empty by default. Before you can begin configuration you must add at least one new rule. This can be done by clicking the 'Add' button:

After adding a rule you should be redirected to its configuration page.

Send SMS

One of the two Events Reporting types is via SMS messages. When an Events Reporting rule is configured to send SMS, the devices will send out an SMS message from the currently active SIM card to the phone number specified in a rule's configuration.

Field	Value	Description
Enable	off \| on; default: off	Turns the rule on or off.
Event type	Config change \| New DHCP client \| Startup \| Mobile data \| SMS \| Signal Strength \| Reboot \| SSH \| WebUI \| New WiFi client\| Ports state \| Topology changes\| WAN Failover\| GPS \| FOTA; default: Config change	Event that will trigger the rule.
Event subtype	Varies	More specific event type that will trigger the rule.
Action	Send SMS \| Send email; default: Send Email	Selects the method of reporting on the specified event.
Message text on Event	string; default: Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;	Text to be included in the body of the report message.
Recipients	Single \| Group; default: Single	Specifies whether the recipient should be a single number or a group of numbers.
Recipient's phone number	phone number; default: none	Phone number of the recipient. The phone number must be entered in the international format, without spaces or other symbols (for example: +37068163951)

Send email

When an Events Reporting rule is configured to send emails, the device (this RUTM59) will connect to an existing email account when a user specified trigger event occurs and send an email to another email address informing of the occurred event.

In order to send emails, the device requires access to an existing email account. You can configure email accounts in the System → Administration → Recipients page. Allowing access to less secure apps may be required for some email service providers.

Field	Value	Description
Enable	off \| on; default: on	Turns the rule on or off.
Event type	Config change \| Startup \| New DHCP client \| Mobile data \| SMS \| Signal Strength \| Reboot \| SSH \| WebUI \| Ports state \| Topology changes\| WAN Failover\| GPS\| New WiFi client \| FOTA; default: Config change	Event that will trigger the rule.
Event subtype	Varies	More specific event type that will trigger the rule.
Action	Send SMS \|Send email; default: Send email	Selects the method of reporting on the specified event.
Subject	string; default: none	Subject of the sent email.
Message text on Event	string; default: Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;	Text to be included in the body of the report email.
Email account	email account; default: none	The account that will be used to send an email.
Recipient's email address	email address; default: none	Email address of the recipient.
Send test email	- (interactive button)	Sends an email based on the current configuration. This is used to test whether the configuration works as intended.