RUTX11 Events Reporting

From Wiki Knowledge Base | Teltonika Networks
This is the approved revision of this page, as well as being the most recent.
Main Page > RUTX Routers > RUTX11 > RUTX11 Manual > RUTX11 WebUI > RUTX11 Services section > RUTX11 Events Reporting

The information in this page is updated in accordance with firmware version RUTX_R_00.02.05.1.

Summary[edit | edit source]

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 RUTX11 devices.

Events Reporting Rules[edit | edit source]

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 Description
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 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
  • All
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
  • All
Reboot Informs after device reboot occurrences. Possible triggers are:
  • From button
  • From Input/Output
  • From Ping Reboot
  • From Reboot Scheduler
  • From WebUI
  • All
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 state 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

Events Reporting Configuration[edit | edit source]

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:

Networking rutos manual events reporting events reporting rules add button.png

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.

Networking rutos manual events reporting events reporting rules send sms.png

Field Value Description
Enable off | on; default: on Turns the rule on or off.
Event Config change | New DHCP client | Mobile data | Send SMS | Signal Strength | Reboot | SSH | WebUI | Ports state | Topology changes| WAN Failover| GPS; default: Config change The event that you wish to receive notifications on.
Event type Varies Specific event sub-type that will trigger the rule. The value of this field changes in accordance with the selection of the 'Event' field.
Action Send SMS | Send email; default: Send SMS 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 number | Group; default: Single number 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 RUTX11) 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.

Networking rutos manual events reporting events reporting rules send email.png

Field Value Description
Enable off | on; default: on Turns the rule on or off.
Event Config change | New DHCP client | Mobile data | Send SMS | Signal Strength | Reboot | SSH | WebUI | Ports state | Topology changes| WAN Failover| GPS; default: Config change The event that you wish to receive notifications on.
Event type Varies Specific event sub-type that will trigger the rule. The value of this field changes in accordance with the selection of the 'Event' field.
Action Send SMS |Send email; default: Send SMS 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.