Line 1: |
Line 1: |
| <!-- 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}}} |
| }} | | }} |
Line 7: |
Line 7: |
| ==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. |
Line 13: |
Line 13: |
| ==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. |
Line 42: |
Line 42: |
| </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> |
Line 153: |
Line 153: |
| | | |
| After adding a rule you should be redirected to its configuration page. | | After adding a rule you should be redirected to its configuration page. |
− | {{#ifeq: {{{mobile}}} | 1 | <h3>Send SMS</h3> | + | {{#ifeq: {{{mobile}}} | 1 | ===Send SMS=== |
| ---- | | ---- |
| One of the two Events Reporting types is <b>via SMS messages</b>. 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. | | One of the two Events Reporting types is <b>via SMS messages</b>. 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. |
Line 172: |
Line 172: |
| <tr> | | <tr> |
| <td>Event</td> | | <td>Event</td> |
− | <td>Config change {{!}} New DHCP client {{#ifeq:{{{mobile}}}|1|{{!}} Mobile data {{!}} SMS}} {{!}} Signal Strength {{!}}|}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failvoer}}}|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1| {{!}} GPS|}}; default: <b>Config change</b></td> | + | <td>Config change {{!}} New DHCP client {{!}} Mobile data {{!}} Send SMS {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}; default: <b>Config change</b></td> |
| <td>The event that you wish to receive notifications on.</td> | | <td>The event that you wish to receive notifications on.</td> |
| </tr> | | </tr> |
Line 188: |
Line 188: |
| <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> |
Line 206: |
Line 206: |
| When an Events Reporting rule is configured to <b>send emails</b>, the device (this {{{name}}}) 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. | | When an Events Reporting rule is configured to <b>send emails</b>, the device (this {{{name}}}) 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 <b>System → Administration → [[{{{name}}} Administration#Recipients|Recipients]] 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_email.png|border|class=tlt-border]] |
| | | |
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 221: |
Line 223: |
| <tr> | | <tr> |
| <td>Event</td> | | <td>Event</td> |
− | <td>Config change {{!}} New DHCP client {{!}} Mobile data {{!}} SMS}} {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}; default: <b>Config change</b></td> | + | <td>Config change {{!}} New DHCP client {{#ifeq:{{{mobile}}}|1|{{!}} Mobile data {{!}} Send SMS {{!}} Signal Strength {{!}}|{{!}}}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}; default: <b>Config change</b></td> |
| <td>The event that you wish to receive notifications on.</td> | | <td>The event that you wish to receive notifications on.</td> |
| </tr> | | </tr> |
Line 231: |
Line 233: |
| <tr> | | <tr> |
| <td>Action</td> | | <td>Action</td> |
− | <td>Send SMS {{!}} Send email; default: <b>Send SMS</b></td> | + | <td>{{#ifeq:{{{mobile}}}|1|Send SMS {{!}} |}}Send email; default: <b>{{#ifeq:{{{mobile}}}|1|Send SMS|Send email}}</b></td> |
| <td>Selects the method of reporting on the specified event.</td> | | <td>Selects the method of reporting on the specified event.</td> |
| </tr> | | </tr> |
Line 242: |
Line 244: |
| <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> |