Difference between revisions of "Template:Networking rutos manual mobile utilities"
(74 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template: Networking_rutos_manual_fw_disclosure |
− | | | + | | fw_version = {{{series}}}_R_00.02.06.1 |
− | + | | series = {{{series}}} | |
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
− | {{#ifeq: {{{ | + | {{#ifeq: {{{legacy}}} | 1 |<br><i><b>Note</b>: <b>[[{{{name}}} VPN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.2 and earlier) user manual page.</i>|}} |
− | |||
==Summary== | ==Summary== | ||
− | The <b>Mobile Utilities</b> page is used to configure various SMS | + | The <b>Mobile Utilities</b> page is used to configure various SMS and Call related device control options and to read, send and manage SMS messages and SMS storage space. |
This manual page provides an overview of the Mobile Utilities page in {{{name}}} devices. | This manual page provides an overview of the Mobile Utilities page in {{{name}}} devices. | ||
Line 19: | Line 14: | ||
The <b>SMS Utilities</b> section contains a list of rules that perform certain actions when they are activated by SMS messages. | The <b>SMS Utilities</b> section contains a list of rules that perform certain actions when they are activated by SMS messages. | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_sms_rules.png|border|class=tlt-border]] |
The entire list contains more than 20 rules, but it does not include all possible SMS actions. You can also create custom rules or modify existing rules. All possible SMS rule actions, their default SMS texts and descriptions are listed in the table below. | The entire list contains more than 20 rules, but it does not include all possible SMS actions. You can also create custom rules or modify existing rules. All possible SMS rule actions, their default SMS texts and descriptions are listed in the table below. | ||
Line 38: | Line 33: | ||
<td><i>cellular</i></td> | <td><i>cellular</i></td> | ||
<td>Is used to configure the device's mobile data connection. [[#Change_mobile_settings_.28cellular.29_rule|Click here]] for more information on this rule.</td> | <td>Is used to configure the device's mobile data connection. [[#Change_mobile_settings_.28cellular.29_rule|Click here]] for more information on this rule.</td> | ||
− | + | </tr>{{#ifeq: {{{dualsim}}} | 1 | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | </tr>{{#ifeq: {{{dualsim}}} | 1 | ||
<tr> | <tr> | ||
<td><b>Force SIM switch</b></td> | <td><b>Force SIM switch</b></td> | ||
<td><i>switch_sim</i></td> | <td><i>switch_sim</i></td> | ||
<td>Switches from using one SIM card to another.</td> | <td>Switches from using one SIM card to another.</td> | ||
− | </tr>|}} | + | </tr>|}} |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td><b>FW upgrade from server</b></td> | <td><b>FW upgrade from server</b></td> | ||
Line 78: | Line 48: | ||
<td><i>profdisp</i></td> | <td><i>profdisp</i></td> | ||
<td>Sends a list of configuration profiles existing on the device.</td> | <td>Sends a list of configuration profiles existing on the device.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
<td><b>GPS control</b></td> | <td><b>GPS control</b></td> | ||
Line 88: | Line 58: | ||
<td><i>gps</i></td> | <td><i>gps</i></td> | ||
<td>Sends the device's current GPS coordinates.</td> | <td>Sends the device's current GPS coordinates.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
<td><b>IP unblock</b></td> | <td><b>IP unblock</b></td> | ||
Line 123: | Line 93: | ||
</ul> | </ul> | ||
</td> | </td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
<td><b>Mobile Data limit status</b></td> | <td><b>Mobile Data limit status</b></td> | ||
<td><i>no default text</i></td> | <td><i>no default text</i></td> | ||
− | <td>Sends a status report message that includes data limit usage information for mobile network interfaces (that have [[{{{name}}} | + | <td>Sends a status report message that includes data limit usage information for mobile network interfaces (that have [[{{{name}}}_Interfaces#Mobile_Data_Limit|Mobile Data Limit]] enabled) </td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 133: | Line 103: | ||
<td><i>no default text</i></td> | <td><i>no default text</i></td> | ||
<td>Resets mobile data usage for specified interface.</td> | <td>Resets mobile data usage for specified interface.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
<td><b>Monitoring status</b></td> | <td><b>Monitoring status</b></td> | ||
Line 220: | Line 190: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<td><b>Wake on LAN</b></td> | <td><b>Wake on LAN</b></td> | ||
<td><i>wakeup</i></td> | <td><i>wakeup</i></td> | ||
− | <td>Sends a magic packet that "wakes up" a specified device from standby mode. If you have multiple Wake-on-LAN-capable devices, you will have to create a separate rule with a different SMS text for each one. Configuration for each device must include the MAC address of that device.</td> | + | <td>Sends a magic packet that "wakes up" a specified device from standby mode. If you have multiple Wake-on-LAN-capable devices, you will have to create a separate rule with a different SMS text for each one. Configuration for each device must include the MAC address of that device.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 239: | Line 203: | ||
<td><i>weboff</i></td> | <td><i>weboff</i></td> | ||
<td>Turns HTTP and HTTPS access off. This rule can also modified to turn of either HTTP or HTTPS separately.</td> | <td>Turns HTTP and HTTPS access off. This rule can also modified to turn of either HTTP or HTTPS separately.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 254: | Line 213: | ||
<li><b>No authorization</b> - no special keyword required; simply send a rule's <i>SMS Text</i>. For example, to execute the <i>reboot</i> rule without authorization:<pre>reboot</pre></li> | <li><b>No authorization</b> - no special keyword required; simply send a rule's <i>SMS Text</i>. For example, to execute the <i>reboot</i> rule without authorization:<pre>reboot</pre></li> | ||
<li><b>By serial</b> - include the device's serial number before a rule's <i>SMS Text</i>. For example, to execute the <i>iostatus</i> rule with serial authorization:<pre>1111111111 iostatus</pre> <font size="-1"><i>(replace 1111111111 with your device's serial number)</i></font></li> | <li><b>By serial</b> - include the device's serial number before a rule's <i>SMS Text</i>. For example, to execute the <i>iostatus</i> rule with serial authorization:<pre>1111111111 iostatus</pre> <font size="-1"><i>(replace 1111111111 with your device's serial number)</i></font></li> | ||
− | <li><b>By device admin password</b> - include the device's password before a rule's <i>SMS Text</i>. For example, to execute the <i>vpnon</i> rule with | + | <li><b>By device admin password</b> - include the device's password before a rule's <i>SMS Text</i>. For example, to execute the <i>vpnon</i> rule with password authorization:<pre>admin01 vpnon</pre> <font size="-1"><i>(replace admin01 with your device's admin password)</i></font></li> |
− | |||
</ul> | </ul> | ||
===Modify SMS Rule=== | ===Modify SMS Rule=== | ||
---- | ---- | ||
− | Every SMS rule can be edited to your liking. To begin configuring a rule, click the click the 'Edit' button | + | Every SMS rule can be edited to your liking. To begin configuring a rule, click the click the 'Edit' button located next to it: |
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_edit_button.png|border|class=tlt-border]] |
After this you should redirected to configuration page for that rule. Below are examples of what the configuration page for the <i>reboot</i> rule looks like. | After this you should redirected to configuration page for that rule. Below are examples of what the configuration page for the <i>reboot</i> rule looks like. | ||
Line 268: | Line 226: | ||
<b>General settings</b> | <b>General settings</b> | ||
---- | ---- | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general.png|border|class=tlt-border]] |
<ol> | <ol> | ||
<li>The <b>Enable</b> slider turn the rule on or off. In order to use a rule, this slider must be set to 'on'. By default, all existing SMS rules are turned on.</li> | <li>The <b>Enable</b> slider turn the rule on or off. In order to use a rule, this slider must be set to 'on'. By default, all existing SMS rules are turned on.</li> | ||
<li>The <b>Action</b> dropdown selection specifies which action should be performed when the rule is executed.</li> | <li>The <b>Action</b> dropdown selection specifies which action should be performed when the rule is executed.</li> | ||
− | |||
<li>The <b>SMS text</b> field specifies the text that will trigger the rule upon receiving a message.</li> | <li>The <b>SMS text</b> field specifies the text that will trigger the rule upon receiving a message.</li> | ||
<li>The <b>Get status via SMS after reboot</b> slider specifies whether the device should send a status report message after an action is executed. The name of this slider may differ from rule to rule and it is only available for some rules.</li> | <li>The <b>Get status via SMS after reboot</b> slider specifies whether the device should send a status report message after an action is executed. The name of this slider may differ from rule to rule and it is only available for some rules.</li> | ||
− | <li>The <b> | + | <li>The <b>Send status SMS to other number</b> slider specifies whether the device should send a status report message to another number (besides the original sender). Setting this slider to 'on' will prompt you to enter an additional phone number(s) of the status message recipient(s).</li> |
− | |||
<li>The <b>Message text</b> box is used to modify the text that should be included in an SMS rule's response message.</li> | <li>The <b>Message text</b> box is used to modify the text that should be included in an SMS rule's response message.</li> | ||
</ol> | </ol> | ||
Line 283: | Line 239: | ||
<b>Authorization</b> | <b>Authorization</b> | ||
---- | ---- | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_authorization.png|border|class=tlt-border]] |
<ol> | <ol> | ||
− | <li>The <b>Authorization method</b> dropdown selection specifies the type of authorization an SMS rule requires (device admin password, serial number | + | <li>The <b>Authorization method</b> dropdown selection specifies the type of authorization an SMS rule requires (device admin password, serial number or none).</li> |
<li>The <b>Allowed number(s)</b> dropdown selection specifies who can execute an SMS rule (based on phone number).</li> | <li>The <b>Allowed number(s)</b> dropdown selection specifies who can execute an SMS rule (based on phone number).</li> | ||
</ol> | </ol> | ||
Line 296: | Line 252: | ||
The <b>Change mobile settings</b> rule is used to change the configuration settings of the mobile data connection. The usage of this rule is a bit more complex because the SMS text in and of itself does nothing, as you must also specify the parameters and values that you wish to set. For example, you can send a message that will change your APN only or a message that will change multiple parameters at once. | The <b>Change mobile settings</b> rule is used to change the configuration settings of the mobile data connection. The usage of this rule is a bit more complex because the SMS text in and of itself does nothing, as you must also specify the parameters and values that you wish to set. For example, you can send a message that will change your APN only or a message that will change multiple parameters at once. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_cellular_dualsim_{{{dualsim}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_cellular_dualsim_{{{dualsim}}}.png|border|class=tlt-border]] |
Below is the full list of parameters that can be changed with this rule. | Below is the full list of parameters that can be changed with this rule. | ||
Line 336: | Line 292: | ||
<td>Sets the service mode. Possible values are: | <td>Sets the service mode. Possible values are: | ||
<ul> | <ul> | ||
− | + | <li>3gonly</li> | |
− | + | <li>4gonly</li> | |
− | |||
− | |||
− | |||
<li>auto</li> | <li>auto</li> | ||
</ul> | </ul> | ||
Line 365: | Line 318: | ||
</td> | </td> | ||
<td><i>cellular roaming=0</i></td> | <td><i>cellular roaming=0</i></td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 375: | Line 323: | ||
Each example above contains a single parameter but you can also send out multiple parameters in one message. For example: | Each example above contains a single parameter but you can also send out multiple parameters in one message. For example: | ||
− | cellular apn=internet service= | + | cellular apn=internet service=3gonly |
This message would set your APN to "internet" and the service mode of the mobile connection to "3G Only". You can also send a message that would include all of the parameters above: | This message would set your APN to "internet" and the service mode of the mobile connection to "3G Only". You can also send a message that would include all of the parameters above: | ||
− | cellular apn=internet auth_mode=pap service= | + | cellular apn=internet dialnumber=*99***1# auth_mode=pap service=3gonly username=user password=pass roaming=0 |
<b>Note:</b> only "apn=" or "auto_apn=" is required in a message. For example, to set custom APN: | <b>Note:</b> only "apn=" or "auto_apn=" is required in a message. For example, to set custom APN: | ||
Line 393: | Line 341: | ||
The <b>UCI API</b> rule is used to configure any parameters on the device. | The <b>UCI API</b> rule is used to configure any parameters on the device. | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_uci.png|border|class=tlt-border]] |
---- | ---- | ||
The following are syntax examples for the UCI API rule: | The following are syntax examples for the UCI API rule: | ||
Line 401: | Line 349: | ||
<th width=30%>Structure example</th> | <th width=30%>Structure example</th> | ||
<th width=35%>Description</th> | <th width=35%>Description</th> | ||
− | <th width= | + | <th width=35%>SMS text example</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>uci <b>get</b> <config>.<section>.<option_name></td> | <td>uci <b>get</b> <config>.<section>.<option_name></td> | ||
<td>Returns the value of a single configuration option.</td> | <td>Returns the value of a single configuration option.</td> | ||
− | <td | + | <td><li><i>uci get network.wan.ipaddr</i></li>Returns the router's WAN IP address.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>uci <b>set</b> <config>.<section>.<option_name>="value"</td> | <td>uci <b>set</b> <config>.<section>.<option_name>="value"</td> | ||
<td>Sets the value of a specified configuration option.</td> | <td>Sets the value of a specified configuration option.</td> | ||
− | <td | + | <td><li><i>uci set network.mobile.apn=example</i></li>Changes mobile APN value to "example".</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>uci <b>show</b> <config></td> | <td>uci <b>show</b> <config></td> | ||
<td>Returns the contents of a config file</td> | <td>Returns the contents of a config file</td> | ||
− | <td | + | <td><li><i>uci show openvpn</i></li>Returns the contents of the "openvpn" config file.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>uci <b>show</b> <config>.<section></td> | <td>uci <b>show</b> <config>.<section></td> | ||
<td>Returns the exact part (section) of a config file.</td> | <td>Returns the exact part (section) of a config file.</td> | ||
− | <td | + | <td><li><i>uci show network.lan</i></li>Returns the configuration of the "lan" section from the "network" config file.</td> |
</tr> | </tr> | ||
<!-- | <!-- | ||
Line 438: | Line 386: | ||
The UCI rule requires that you know the names of the configuration files and sections and parameters contained within them. You can find the config file list and some examples of the UCI system usage in our <b>[[UCI command usage]]</b> article. | The UCI rule requires that you know the names of the configuration files and sections and parameters contained within them. You can find the config file list and some examples of the UCI system usage in our <b>[[UCI command usage]]</b> article. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Custom Rules=== | ===Custom Rules=== | ||
Line 491: | Line 401: | ||
<b>Post/Get</b> allows you to perform action requests by writing them in the URL after your device’s IP address. | <b>Post/Get</b> allows you to perform action requests by writing them in the URL after your device’s IP address. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_post_get_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_post_get_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 504: | Line 414: | ||
<td>Enable SMS management functionality through POST/GET | <td>Enable SMS management functionality through POST/GET | ||
</td> | </td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
{{#ifeq: {{{dualmodem}}} | 1 | | {{#ifeq: {{{dualmodem}}} | 1 | | ||
Line 551: | Line 456: | ||
<tr> | <tr> | ||
<td>Read mobile message</td> | <td>Read mobile message</td> | ||
− | <td>http://<span | + | <td>http://<span |
+ | style="color: black;">192.168.1.1</span>/cgi-bin/sms_read?username=user1&password=user_pass&number=1 | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Send mobile message to a single number</td> | <td>Send mobile message to a single number</td> | ||
− | <td>http://<span | + | <td>http://<span |
+ | style="color: black;">192.168.1.1</span>/cgi-bin/sms_send?username=user1&password=user_pass&number=0037060000001&text=testmessage | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Send mobile message to a group</td> | <td>Send mobile message to a group</td> | ||
− | <td>http://<span | + | <td>http://<span |
+ | style="color: black;">192.168.1.1</span>/cgi-bin/sms_send?username=user1&password=user_pass&group=group_name&text=testmessage | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 571: | Line 479: | ||
<tr> | <tr> | ||
<td>Delete mobile message</td> | <td>Delete mobile message</td> | ||
− | <td>http://<span | + | <td>http://<span |
+ | style="color: black;">192.168.1.1</span>/cgi-bin/sms_delete?username=user1&password=user_pass&number=1 | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 622: | Line 531: | ||
<b>Auto reply</b> allows you to configure automatic replying to SMS messages that the router receives. | <b>Auto reply</b> allows you to configure automatic replying to SMS messages that the router receives. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_auto_reply_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_auto_reply_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 662: | Line 571: | ||
<td>default: '''Everyone'''</td> | <td>default: '''Everyone'''</td> | ||
<td>Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options: | <td>Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options: | ||
− | + | ||
− | + | <li>Everyone</li> | |
− | + | <li>Listed numbers</li> | |
− | + | <li>From user group</li> | |
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
Line 685: | Line 593: | ||
The SMS Forwarding To HTTP functionality forwards SMS messages to HTTP, using either POST or GET methods. | The SMS Forwarding To HTTP functionality forwards SMS messages to HTTP, using either POST or GET methods. | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_http.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 712: | Line 620: | ||
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
<td>Enable/disable adding original message sender phone number at the end of message text</td> | <td>Enable/disable adding original message sender phone number at the end of message text</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS certificate verification</td> | <td>HTTPS certificate verification</td> | ||
<td>default: '''Ignore'''</td> | <td>default: '''Ignore'''</td> | ||
− | <td>Select whether to ignore or verify server certificate. Available options: | + | <td>Select whether to ignore or verify server certificate. Available options: <li>Ignore</li> <li>Verify</li> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 738: | Line 630: | ||
<td>Method</td> | <td>Method</td> | ||
<td>default: '''Get'''</td> | <td>default: '''Get'''</td> | ||
− | <td>Choose witch HTTP request method will be used. Available options: | + | <td>Choose witch HTTP request method will be used. Available options: <li>Get</li> <li>Post</li> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 765: | Line 657: | ||
<td>default: <b>none</b></td> | <td>default: <b>none</b></td> | ||
<td>Extra html query name/value pair. Enter name to the left field and value to right</td> | <td>Extra html query name/value pair. Enter name to the left field and value to right</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Mode</td> | ||
+ | <td>default: '''All messages'''</td> | ||
+ | <td>Choose which messages are going to be forwarded. Available options: <li>All messages''' | ||
+ | <li>From listed numbers''' | ||
+ | <li>From user group''' | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 772: | Line 672: | ||
The '''SMS Forwarding To SMS''' function forwards SMS messages to one or several recipients. | The '''SMS Forwarding To SMS''' function forwards SMS messages to one or several recipients. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_sms_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_sms_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 814: | Line 714: | ||
<tr> | <tr> | ||
<td>Mode</td> | <td>Mode</td> | ||
− | <td>default: ''' | + | <td>default: '''All messages'''</td> |
− | <td> | + | <td>Choose which messages are going to be forwarded. Available options: <li>All messages''' |
− | + | <li>From listed numbers''' | |
− | + | <li>From user group''' | |
− | |||
− | |||
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
Line 834: | Line 731: | ||
The '''SMS Forwarding To Email''' function forwards SMS messages to email. | The '''SMS Forwarding To Email''' function forwards SMS messages to email. | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_email.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 859: | Line 756: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Add sender's number</td> |
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
<td>Enable/disable adding sender phone number at the end of email text body</td> | <td>Enable/disable adding sender phone number at the end of email text body</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 880: | Line 766: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Email group</td> |
<td>default: <b>none</b></td> | <td>default: <b>none</b></td> | ||
<td>Sender's email configuration</td> | <td>Sender's email configuration</td> | ||
Line 888: | Line 774: | ||
<td>default: <b>none</b></td> | <td>default: <b>none</b></td> | ||
<td>For whom you want to send an email to. Allowed characters (a-zA-Z0-9._%+-)</td> | <td>For whom you want to send an email to. Allowed characters (a-zA-Z0-9._%+-)</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Mode</td> | ||
+ | <td>default: '''All messages'''</td> | ||
+ | <td>Choose which messages are going to be forwarded. Available options: <li>All messages''' | ||
+ | <li>From listed numbers''' | ||
+ | <li>From user group''' | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 897: | Line 791: | ||
<b>Important note</b>: all POP3 server email messages from inbox will be deleted when using this service. | <b>Important note</b>: all POP3 server email messages from inbox will be deleted when using this service. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_email_to_sms_forwarding_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_email_to_sms_forwarding_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 931: | Line 825: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Secure connection ( | + | <td>Secure connection (SSL)</td> |
− | <td> | + | <td>yes | no; default: <b>no</b></td> |
− | <td> | + | <td><b>SSL</b> is a protocol for transmitting private documents via the Internet. SSL uses a cryptographic system that uses two keys to encrypt data − a public key known to everyone and a private or secret key known only to the recipient of the message</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>SMS | + | <td>SMS limit</td> |
<td>integer; default: <b>5</b></td> | <td>integer; default: <b>5</b></td> | ||
− | <td> | + | <td>Limit of SMS count that can be contained in the email body of text, SMS length is limited to 160 seven-bit characters. Emails that contain more symbols than it is specified in this field will not be sent as SMS messages</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 954: | Line 843: | ||
<td>Minutes | Hours| Days; default: <b>Minutes</b></td> | <td>Minutes | Hours| Days; default: <b>Minutes</b></td> | ||
<td>Email inbox check interval</td> | <td>Email inbox check interval</td> | ||
− | </tr>{{#ifeq: {{{ | + | </tr>{{#ifeq: {{{dualsim}}} | 1 | |
<tr> | <tr> | ||
<td>Gateway modem</td> | <td>Gateway modem</td> | ||
Line 972: | Line 861: | ||
For example, a valid number would be <b>0037012345678</b> (370 is country code and 12345678 is the receiver's phone number, all preceded by 00) | For example, a valid number would be <b>0037012345678</b> (370 is country code and 12345678 is the receiver's phone number, all preceded by 00) | ||
+ | {{#ifeq:{{{name}}}| TRB255| | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Call Utilities== | ==Call Utilities== | ||
Just like SMS Utilities, Call Utilities provide you with the possibility to issue certain commands to the router from your mobile phone. The list of possible rules is of course shorter because you can only make one type of call. Keep that in mind when creating Call Utilities rules because one call will trigger all of the enabled rules at once. | Just like SMS Utilities, Call Utilities provide you with the possibility to issue certain commands to the router from your mobile phone. The list of possible rules is of course shorter because you can only make one type of call. Keep that in mind when creating Call Utilities rules because one call will trigger all of the enabled rules at once. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
===Call Rules=== | ===Call Rules=== | ||
---- | ---- | ||
− | To create a new rule, select an 'Action' and click the 'Add' button. | + | To create a new rule, select an 'Action' and click the 'Add' button. The new rule will appear in the 'Call Rules' list. Click the 'Edit' button next to it to configure the rule. |
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_edit_button.png|border|class=tlt-border]] |
− | + | Then you should be redirected to that rule's configuration page. The Call Configuration window is similar to SMS Configuration but less complex. | |
+ | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_general.png|border|class=tlt-border]] | ||
− | + | Call Configuration also has similar Authorization settings. | |
− | |||
− | |||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_authorization.png|border|class=tlt-border]] |
}} | }} | ||
− | |||
==Messages== | ==Messages== | ||
With the help of the <b>Messages</b> window you can read and send SMS messages. | With the help of the <b>Messages</b> window you can read and send SMS messages. | ||
− | ===Read | + | ===Read SMS=== |
---- | ---- | ||
− | In the <b>Read | + | In the <b>Read SMS</b> section you can read and delete received/stored SMS messages. The layout is simple, there is a list of received SMS messages and you can choose how many entries of that list should be visible at one time with SMS per page drop box in the top left corner of the page and there is a Search field to help you navigate more efficiently through the list of messages in the top right corner of the page. |
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_messages_read_messages_dualmodem_1.png|border|class=tlt-border]] |
===Send Messages=== | ===Send Messages=== | ||
Line 1,086: | Line 903: | ||
In the Storage tab you can find settings associated with message storage. | In the Storage tab you can find settings associated with message storage. | ||
− | [[File:Networking_rutos_manual_mobile_utilities_messages_storage_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_messages_storage_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 1,095: | Line 912: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Save messages | + | <td>Save messages on SIM</td> |
− | <td> | + | <td>off | on; default: <b>on</b></td> |
− | <td> | + | <td>If this is enabled, messages from SIM card will not be removed after they have been read</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Delete forwarded messages</td> |
+ | <td>off | on; default: <b>off</b></td> | ||
+ | <td>If enabled, all forwarded messages will be automatically deleted</td> | ||
+ | </tr>{{#ifeq: {{{dualmodem}}} | 1 | | ||
+ | <tr> | ||
+ | <td>Modem</td> | ||
+ | <td> Primary modem {{!}} Secondary modem; default: <b>Primary modem</b></td> | ||
+ | <td>Which modem is used</td> | ||
+ | </tr>|}} | ||
+ | <tr> | ||
+ | <td>SIM card memory</td> | ||
<td>-</td> | <td>-</td> | ||
<td>Information about used/available SIM card memory</td> | <td>Information about used/available SIM card memory</td> | ||
Line 1,111: | Line 938: | ||
</table> | </table> | ||
− | [[Category: {{{name}}} Services section]] | + | [[Category:{{{name}}} Services section]] |
Revision as of 08:14, 4 June 2021
Template:Networking rutos manual fw disclosure
Summary
The Mobile Utilities page is used to configure various SMS and Call related device control options and to read, send and manage SMS messages and SMS storage space.
This manual page provides an overview of the Mobile Utilities page in {{{name}}} devices.
SMS Utilities
The SMS Utilities section contains a list of rules that perform certain actions when they are activated by SMS messages.
The entire list contains more than 20 rules, but it does not include all possible SMS actions. You can also create custom rules or modify existing rules. All possible SMS rule actions, their default SMS texts and descriptions are listed in the table below.
Action | SMS Text | Description |
---|---|---|
Change mobile settings | cellular | Is used to configure the device's mobile data connection. Click here for more information on this rule. |
FW upgrade from server | fw_upgrade | Upgrades the device's firmware (provided a new version is available on the FOTA server). |
Get list of profiles | profdisp | Sends a list of configuration profiles existing on the device. |
GPS control | gpson | Turns GPS on. |
GPS coordinates | gps | Sends the device's current GPS coordinates. |
IP unblock | ipunblock | Unblocks Web/SSH access for devices that were blocked for too many unsuccessful connection attempts. Send the SMS text to unblock all blocked devices or include the IP address of a single blocked device after the SMS text. For example:
|
Manage OpenVPN | vpnon | Turns a selected OpenVPN instance on. Include the name of the OpenVPN instance that you wish to turn on after the rule's SMS text:
|
Manage OpenVPN | vpnoff | Turns a selected OpenVPN instance off. Include the name of the OpenVPN instance that you wish to turn off after the rule's SMS text:
|
Mobile Data limit status | no default text | Sends a status report message that includes data limit usage information for mobile network interfaces (that have [[{{{name}}}_Interfaces#Mobile_Data_Limit|Mobile Data Limit]] enabled) |
Mobile Data usage reset | no default text | Resets mobile data usage for specified interface. |
Monitoring status | monitoring_status | Sends a status report message that includes the RMS connection type, state and the device serial number and MAC address. |
More | more | Displays next part of a composite response message (more than 160 characters). |
OpenVPN status | vpnstatus | Sends a status report message on all OpenVPN connections. |
Reboot | reboot | Reboots the device. |
Restore to default | restore | Restores factory settings on the device. |
RMS action | rms_on | Turns RMS connection on. |
RMS action | rms_off | Turns RMS connection off. |
RMS connect | rms_connect | Forces the device to connect to RMS. This action is analogous to clicking the 'Connect' button in the Cloud Solutions → [[{{{name}}}_Cloud_Solutions#RMS|RMS page]]. |
RMS status | rms_status | Sends a status report message on the state of the connection to RMS. |
Send status | status | Sends a status report message. |
SSH access control | sshon | Turns remote and local (by default) SSH access on. This rule can be modified to only include local SSH access. |
SSH access control | sshoff | Turns SSH access off. |
Switch mobile data | mobileon | Turns mobile data usage on. |
Switch mobile data | mobileoff | Turns mobile data usage off. |
UCI API | uci | Is used to change the configuration settings on the device. Click here for more information on the UCI API rule. |
Wake on LAN | wakeup | Sends a magic packet that "wakes up" a specified device from standby mode. If you have multiple Wake-on-LAN-capable devices, you will have to create a separate rule with a different SMS text for each one. Configuration for each device must include the MAC address of that device. |
Web access control | webon | Turns remote and local (by default) HTTP and HTTPS access on. This rule can be modified to only include local HTTP/HTTPS access. |
Web access control | weboff | Turns HTTP and HTTPS access off. This rule can also modified to turn of either HTTP or HTTPS separately. |
SMS rule execution syntax
To execute an SMS rule, send an SMS message to your device's SIM card number with the rule's SMS Text preceded by the selected authorization keyword, which depends on the selected authorization method:
- No authorization - no special keyword required; simply send a rule's SMS Text. For example, to execute the reboot rule without authorization:
reboot
- By serial - include the device's serial number before a rule's SMS Text. For example, to execute the iostatus rule with serial authorization:
1111111111 iostatus
(replace 1111111111 with your device's serial number) - By device admin password - include the device's password before a rule's SMS Text. For example, to execute the vpnon rule with password authorization:
admin01 vpnon
(replace admin01 with your device's admin password)
Modify SMS Rule
Every SMS rule can be edited to your liking. To begin configuring a rule, click the click the 'Edit' button located next to it:
After this you should redirected to configuration page for that rule. Below are examples of what the configuration page for the reboot rule looks like.
General settings
- The Enable slider turn the rule on or off. In order to use a rule, this slider must be set to 'on'. By default, all existing SMS rules are turned on.
- The Action dropdown selection specifies which action should be performed when the rule is executed.
- The SMS text field specifies the text that will trigger the rule upon receiving a message.
- The Get status via SMS after reboot slider specifies whether the device should send a status report message after an action is executed. The name of this slider may differ from rule to rule and it is only available for some rules.
- The Send status SMS to other number slider specifies whether the device should send a status report message to another number (besides the original sender). Setting this slider to 'on' will prompt you to enter an additional phone number(s) of the status message recipient(s).
- The Message text box is used to modify the text that should be included in an SMS rule's response message.
Authorization
- The Authorization method dropdown selection specifies the type of authorization an SMS rule requires (device admin password, serial number or none).
- The Allowed number(s) dropdown selection specifies who can execute an SMS rule (based on phone number).
Most rules are configured in a similar manner. However, the configuration does differ from rule to rule, depending on a rule's purpose (selected 'Action'). If you run into trouble when configuring a rule, hover your mouse cursor over the name of a field to see a hint that explains what that field does.
Change mobile settings (cellular) rule
The Change mobile settings rule is used to change the configuration settings of the mobile data connection. The usage of this rule is a bit more complex because the SMS text in and of itself does nothing, as you must also specify the parameters and values that you wish to set. For example, you can send a message that will change your APN only or a message that will change multiple parameters at once.
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_cellular_dualsim_{{{dualsim}}}.png|border|class=tlt-border]]
Below is the full list of parameters that can be changed with this rule.
Parameter | Description | SMS text example |
---|---|---|
apn= | Sets APN. | cellular apn=internet |
auto_apn= | Turns auto APN on or off. Possible values are 0/1. | cellular auto_apn=1 |
dialnumber= | Sets Dialing number. | cellular dialnumber=*99***1# |
auth_mode= | Sets the authentication method. Possible values are:
|
cellular auth_method=pap |
service= | Sets the service mode. Possible values are:
|
cellular service=auto |
username= | Sets the user name for PAP or CHAP authentication. | cellular username=user |
password= | Sets the password for PAP or CHAP authentication. | cellular password=pass |
roaming= | Turns mobile data roaming on or off. Possible values are:
|
cellular roaming=0 |
Each example above contains a single parameter but you can also send out multiple parameters in one message. For example:
cellular apn=internet service=3gonly
This message would set your APN to "internet" and the service mode of the mobile connection to "3G Only". You can also send a message that would include all of the parameters above:
cellular apn=internet dialnumber=*99***1# auth_mode=pap service=3gonly username=user password=pass roaming=0
Note: only "apn=" or "auto_apn=" is required in a message. For example, to set custom APN:
cellular apn=internet
or if you want to turn auto APN on:
cellular auto_apn=1
UCI API rule
The UCI API rule is used to configure any parameters on the device.
The following are syntax examples for the UCI API rule:
Structure example | Description | SMS text example |
---|---|---|
uci get <config>.<section>.<option_name> | Returns the value of a single configuration option. | |
uci set <config>.<section>.<option_name>="value" | Sets the value of a specified configuration option. | |
uci show <config> | Returns the contents of a config file | |
uci show <config>.<section> | Returns the exact part (section) of a config file. |
The UCI rule requires that you know the names of the configuration files and sections and parameters contained within them. You can find the config file list and some examples of the UCI system usage in our UCI command usage article.
Custom Rules
If none of the default rules suit your purposes, you can also configure custom ones. To do so, scroll down to the very bottom of the SMS Utilities page, where you will find the Add Rule section. Enter a custom SMS text, select an Action and click the 'Add' button:
SMS Gateway
This section provides a summary of the SMS Gateway functions for {{{name}}} devices.
Post/Get
Post/Get allows you to perform action requests by writing them in the URL after your device’s IP address.
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_post_get_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Enable SMS management functionality through POST/GET |
User name | default: user1 | User name used for authorization (5 characters minimum). Allowed characters (a-zA-Z0-9!@#$%&*+-/=?^_`{|}~. ) |
Password | default: user_pass | Password used for authorization (5 characters minimum). Allowed characters (a-zA-Z0-9!@#$%&*+-/=?^_`{|}~. ) |
Use a web browser or any other compatible software to send HTTP post/get strings to the router. The router must be connected to a GSM network when using the Send SMS feature. Below you will find a table with possible actions and examples on how to use them:
Action | Post/get URL examples |
---|---|
View mobile messages list | http://192.168.1.1/cgi-bin/sms_list?username=user1&password=user_pass |
Read mobile message | http://192.168.1.1/cgi-bin/sms_read?username=user1&password=user_pass&number=1 |
Send mobile message to a single number | http://192.168.1.1/cgi-bin/sms_send?username=user1&password=user_pass&number=0037060000001&text=testmessage |
Send mobile message to a group | http://192.168.1.1/cgi-bin/sms_send?username=user1&password=user_pass&group=group_name&text=testmessage |
View mobile messages total | http://192.168.1.1/cgi-bin/sms_total?username=user1&password=user_pass |
Delete mobile message | http://192.168.1.1/cgi-bin/sms_delete?username=user1&password=user_pass&number=1 |
- 192.168.1.1 - router's IP address. (Replace it with your [[{{{name}}}_LAN#General_Setup|LAN IP]] or [[{{{name}}}_WAN#Operation_Modes|WAN IP]] (when connecting remotely))
- SMS related post/get commands. Possible values are:
- sms_list - view all SMS messages in storage
- sms_read - read a single SMS message by specified SMS index (number)
- sms_send - send an SMS message to specified recipient
- sms_total - display SMS storage statistics
- sms_delete - delete a single SMS message by specified SMS index (number)
- & - separation symbol. After specifying the SMS command, other parameters must be separated by an ampersand (&) symbol
- username - SMS post/get configuration user name
- password - SMS post/get configuration password
- number - SMS message index or (depending on context) recipient's phone number. SMS message indexes can be
viewed with the sms_list command.
Correct phone number format is:- 00 - number must be preceded by two zeros
- <country_code> - the next following element is the number holder's country code
- <receivers_number> - phone number of the recipient
For example, a valid number would be 0037012345678 (370 is country code and 12345678 is the receiver's phone number, all preceded by 00)
- text - SMS message text
To use Post/Get via SSH instead of a browser, you may want to use the curl -X command. Simply add the same URL command in between quotes and specify the HTTP method.
Examples:
- View SMS list:
curl -X GET "http://192.168.1.1/cgi-bin/sms_list?username=user1&password=user_pass"
- Send SMS:
curl -X GET "http://192.168.1.1/cgi-bin/sms_send?username=user1&password=user_pass&number=0037000000000&text=testmessage"
Auto Reply
Auto reply allows you to configure automatic replying to SMS messages that the router receives.
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_auto_reply_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Toggles Auto Reply ON or OFF |
Reply SMS-Utilities rules | off | on; default: off | It will reply to sms rules, from SMS-Utilities |
Don't save received messages | off | on; default: off | If enabled, the router will delete received SMS messages |
Mode | default: Everyone | Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options:
|
Message text | default: none | The message that will be sent in reply |
SMS Forwarding
This section is a summary of the SMS Forwarding function in {{{name}}} routers.
SMS Forwarding To HTTP
The SMS Forwarding To HTTP functionality forwards SMS messages to HTTP, using either POST or GET methods.
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Enable/disable SMS forwarding to HTTP |
Forward SMS-Utilities rules | off | on; default: off | Enable/disable sms-utilities rules forwarding |
Don't save received message | off | on; default: off | Select whether you want to save forwarded messages or not |
Include sender's number | off | on; default: off | Enable/disable adding original message sender phone number at the end of message text |
HTTPS certificate verification | default: Ignore | Select whether to ignore or verify server certificate. Available options: |
Method | default: Get | Choose witch HTTP request method will be used. Available options: |
URL | default: none | URL to which message is going to be forwarded |
Number value name | default: none | Sender phone number code name for query string name/value pair |
Message value name | default: none | Message code name for query string name/value pair |
Extra data pair 1 | default: none | Extra html query name/value pair. Enter name to the left field and value to right |
Extra data pair 2 | default: none | Extra html query name/value pair. Enter name to the left field and value to right |
Mode | default: All messages | Choose which messages are going to be forwarded. Available options: |
SMS Forwarding To SMS
The SMS Forwarding To SMS function forwards SMS messages to one or several recipients.
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_sms_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Enables/disables SMS forwarding to SMS |
Forward SMS-Utilities rules | off | on; default: off | Enable/disable sms-utilities rules forwarding |
Don't save received message | off | on; default: off | Select whether you want to save forwarded messages or not |
Add sender's number | off | on; default: off | Enable/disable adding original message sender phone number at the end of message text. Only added if total message length is up to 480 characters |
Mode | default: All messages | Choose which messages are going to be forwarded. Available options: |
Recipients phone numbers | default: none | Number(s) to which received messages will be forwarded to |
SMS Forwarding To Email
The SMS Forwarding To Email function forwards SMS messages to email.
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Enables/disables SMS forwarding to Email |
Forward SMS-Utilities rules | off | on; default: off | Enables/disables sms-utilities rules forwarding |
Don't save received message | off | on; default: off | Select whether you want to save forwarded messages or not |
Add sender's number | off | on; default: off | Enable/disable adding sender phone number at the end of email text body |
Subject | default: none | Subject of an email. Allowed characters (a-zA-Z0-9!@#$%&*+-/=?^_`{|}~. ) |
Email group | default: none | Sender's email configuration |
Recipient's email address | default: none | For whom you want to send an email to. Allowed characters (a-zA-Z0-9._%+-) |
Mode | default: All messages | Choose which messages are going to be forwarded. Available options: |
Email To SMS Forwarding
Email to SMS Forwarding is a function that connects to your email account and checks its inbox at the specified frequency. If it finds any new received emails with a specific subject (phone number in email subject), it sends the body of the email as an SMS message(s) to the recipient specified in the email subject field.
Important note: all POP3 server email messages from inbox will be deleted when using this service.
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_email_to_sms_forwarding_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns Email to SMS Forwarding ON or OFF |
POP3 server | host | ip; default: none | Email service provider's POP3 server address (can be looked up online) |
Server port | integer [0..65535]; default: none | Email service provider's POP3 server port (can be looked up online) |
User name | string; default: none | Email account user name. This is information is used by router in order to atuhenticate itself when connecting to the email client |
Password | string; default: none | Email account password. This is information is used by router in order to atuhenticate itself when connecting to the email client |
Secure connection (SSL) | yes | no; default: no | SSL is a protocol for transmitting private documents via the Internet. SSL uses a cryptographic system that uses two keys to encrypt data − a public key known to everyone and a private or secret key known only to the recipient of the message |
SMS limit | integer; default: 5 | Limit of SMS count that can be contained in the email body of text, SMS length is limited to 160 seven-bit characters. Emails that contain more symbols than it is specified in this field will not be sent as SMS messages |
Check email every | time; default: 1 minute | Email inbox check interval |
Interval | Minutes | Hours| Days; default: Minutes | Email inbox check interval |
Additional note: you may have noticed that there is no option where you can specify the recipient's phone number. As mentioned earlier, Email to SMS doesn't forward all emails, only the ones that are meant to be forwarded. Only emails with the recipient's phone number in the subject will be forwarded to SMS
Correct phone number format is:
- 00 - number must be preceded by two zeros
- <country_code> - the next following element is the number holder's country code
- <receivers_number> - phone number of the recipient
For example, a valid number would be 0037012345678 (370 is country code and 12345678 is the receiver's phone number, all preceded by 00)
Call Utilities
Just like SMS Utilities, Call Utilities provide you with the possibility to issue certain commands to the router from your mobile phone. The list of possible rules is of course shorter because you can only make one type of call. Keep that in mind when creating Call Utilities rules because one call will trigger all of the enabled rules at once.
Call Rules
To create a new rule, select an 'Action' and click the 'Add' button. The new rule will appear in the 'Call Rules' list. Click the 'Edit' button next to it to configure the rule.
Then you should be redirected to that rule's configuration page. The Call Configuration window is similar to SMS Configuration but less complex.
Call Configuration also has similar Authorization settings.
Messages
With the help of the Messages window you can read and send SMS messages.
Read SMS
In the Read SMS section you can read and delete received/stored SMS messages. The layout is simple, there is a list of received SMS messages and you can choose how many entries of that list should be visible at one time with SMS per page drop box in the top left corner of the page and there is a Search field to help you navigate more efficiently through the list of messages in the top right corner of the page.
Send Messages
The Send Messages section lets you send SMS messages from the router‘s SIM card.
[[File:Networking_rutos_manual_mobile_utilities_messages_send_messages_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
All you have to do is enter the recipient’s phone number, type in your message and hit the Send button.
Storage
In the Storage tab you can find settings associated with message storage.
[[File:Networking_rutos_manual_mobile_utilities_messages_storage_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Save messages on SIM | off | on; default: on | If this is enabled, messages from SIM card will not be removed after they have been read |
Delete forwarded messages | off | on; default: off | If enabled, all forwarded messages will be automatically deleted |
SIM card memory | - | Information about used/available SIM card memory |
Leave free space | integer; default: 5 | How much memory (number of messages) should be left free |
[[Category:{{{name}}} Services section]]