Changes

<!-- Template uses {{{name}}}, {{{series}}}, {{{mobile}}} (0), {{{gps}}} (1), {{{wifi}}} (1) -->

<!-- Template uses {{{name}}}, {{{series}}}, {{{mobile}}} (0), {{{gps}}} (1), {{{wifi}}} (1) -->

{{Template:Networking_rutos_manual_fw_disclosure

{{Template: Networking_rutos_manual_fw_disclosure

| fw_version = {{{series}}}_R_00.02.05.1

| fw_version = {{{series}}}_R_00.02.06.1

| series    = {{{series}}}

| series    = {{{series}}}

}}

}}

==Summary==

==Summary==

The <b>Events Reporting</b> feature provides the possibility to configure rules that inform of via {{#ifeq:{{{mobile}}}|0||SMS or }}email when certain trigger events occur.

The <b>Events Reporting</b> feature provides the possibility to configure rules that inform via {{#ifeq:{{{mobile}}}|0||SMS or }} email when certain trigger events occur.

This page is an overview of the Events Reporting section for {{{name}}} devices.

This page is an overview of the Events Reporting section for {{{name}}} devices.

==Events Reporting Rules==

==Events Reporting Rules==

The <b>Events Reporting Rules</b> window 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 {{#ifeq:{{{mobile}}}|0||SMS message or }}email to a specified number informing of the occurred event.

The <b>Events Reporting Rules</b> 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 {{#ifeq:{{{mobile}}}|0||SMS message or}} email to a specified number informing of the occurred event.

All possible trigger events are listed in the table below.  

All possible trigger events are listed in the table below.  

     </tr>|}}{{#ifeq: {{{mobile}}} | 1 |

     </tr>|}}{{#ifeq: {{{mobile}}} | 1 |

     <tr>

     <tr>

         <td><b>Mobile</b></td>

         <td><b>Mobile data</b></td>

         <td>Informs on changes to the state of the device's mobile connection. Possible triggers are:

         <td>Informs on changes to the state of the device's mobile connection. Possible triggers are:

             <ul>

             <ul>

         <td>Message text on Event</td>

         <td>Message text on Event</td>

         <td>string; default: <b>Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;</b></td>

         <td>string; default: <b>Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;</b></td>

         <td>Text to be included in the body of report message.</td>

         <td>Text to be included in the body of the report message.</td>

     </tr>

     </tr>

     <tr>

     <tr>

In order to send emails, the device requires access to an existing email account. You can configure email accounts in the <b>System → Administration → [[{{{name}}} Administration#Recipients|Recipients]]</b> page. Allowing access to less secure apps may be required for some email service providers.

In order to send emails, the device requires access to an existing email account. You can configure email accounts in the <b>System → Administration → [[{{{name}}} Administration#Recipients|Recipients]]</b> page. Allowing access to less secure apps may be required for some email service providers.

[[File:Networking_rutos_manual_events_reporting_events_reporting_rules_send_emai.png|border|class=tlt-border]]

[[File:Networking_rutos_manual_events_reporting_events_reporting_rules_send_email.png|border|class=tlt-border]]

<table class="nd-mantable">

<table class="nd-mantable">

         <td>Message text on Event</td>

         <td>Message text on Event</td>

         <td>string; default: <b>Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;</b></td>

         <td>string; default: <b>Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;</b></td>

         <td>Text to be included in the body of report email.</td>

         <td>Text to be included in the body of the report email.</td>

     </tr>

     </tr>

     <tr>

     <tr>