Difference between revisions of "Template:Networking rutos manual mobile utilities"
(20 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template: Networking_device_manual_fw_disclosure |
− | | fw_version ={{Template: | + | | series = {{{series}}} |
+ | | name = {{{name}}} | ||
+ | | fw_version ={{Template: Networking_device_manual_latest_fw | ||
| series = {{{series}}} | | series = {{{series}}} | ||
| name = {{{name}}} | | name = {{{name}}} | ||
}} | }} | ||
}} | }} | ||
− | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} SMS Utilities (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: | + | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} SMS Utilities (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} |
− | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} SMS Utilities (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: | + | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} SMS Utilities (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} 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{{#switch:{{{name}}}| TRB255 | TRB256= | #default= 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 17: | Line 19: | ||
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_v1.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 96: | Line 98: | ||
</ul> | </ul> | ||
</td> | </td> | ||
− | </tr> | + | </tr>{{#ifeq: {{{io}}} | 1 | |
+ | <tr> | ||
+ | <td><b>I/O status</b></td> | ||
+ | <td><i>iostatus</i></td> | ||
+ | <td>Sends a status report message on the state of the device's inputs and outputs.</td> | ||
+ | </tr>|}} | ||
<tr> | <tr> | ||
<td><b>Manage OpenVPN</b></td> | <td><b>Manage OpenVPN</b></td> | ||
Line 120: | Line 127: | ||
<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}}}_WAN#Mobile_Data_Limit|Mobile Data Limit]] enabled) </td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 175: | Line 182: | ||
<td><b>Send status</b></td> | <td><b>Send status</b></td> | ||
<td><i>status</i></td> | <td><i>status</i></td> | ||
− | <td>Sends a status message | + | <td>Sends a status report message.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 195: | Line 202: | ||
<td><b>Switch mobile data</b></td> | <td><b>Switch mobile data</b></td> | ||
<td><i>mobileoff</i></td> | <td><i>mobileoff</i></td> | ||
− | <td>Turns mobile data usage off | + | <td>Turns mobile data usage off.</td> |
</tr>{{#ifeq: {{{wifi}}} | 1 | | </tr>{{#ifeq: {{{wifi}}} | 1 | | ||
<tr> | <tr> | ||
Line 215: | Line 222: | ||
<td><b>Restore to user's defaults</b></td> | <td><b>Restore to user's defaults</b></td> | ||
<td><i>userdefaults</i></td> | <td><i>userdefaults</i></td> | ||
− | <td>Restores user's default configuration on the device. [[{{{name}}} | + | <td>Restores user's default configuration on the device. [[{{{name}}}_Maintenance#Create_default_configuration|Click here]] for more information on User's default configuration.</td> |
</tr>{{#switch:{{{name}}} | </tr>{{#switch:{{{name}}} | ||
| TRB141|TRB142|TRB145= | | TRB141|TRB142|TRB145= | ||
Line 253: | Line 260: | ||
===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 under "Actions" column: |
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_edit_button_v1.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 261: | Line 268: | ||
<b>General settings</b> | <b>General settings</b> | ||
---- | ---- | ||
− | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general_dualmodem_{{{dualmodem}}}_v3.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> | ||
+ | {{#ifeq: {{{dualmodem}}} | 1 |<li>The <b>Receiving modem</b>, which is used to receive the 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>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>Message forwarding</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 forwarding</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> | ||
− | {{#ifeq: {{{dualmodem}}} | 1 |<li>The <b>Modem</b> | + | {{#ifeq: {{{dualmodem}}} | 1 |<li>The <b>Modem</b>, which is used to get information from or managed for change mobile settings action.</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> | ||
</ol> | </ol> | ||
<b>Authorization</b> | <b>Authorization</b> | ||
---- | ---- | ||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_authorization_v1.png|border|class=tlt-border]] |
<ol> | <ol> | ||
Line 289: | Line 296: | ||
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}}}_{{{dualmodem}}}.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_cellular_dualsim_{{{dualsim}}}_{{{dualmodem}}}_v2.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 381: | Line 388: | ||
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_{{{dualmodem}}}_v4.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 394: | Line 401: | ||
<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><li><i>uci get network.wan.ipaddr</i></li>Returns the router's WAN IP address.</td> | + | <td><ul><li><i>uci get network.wan.ipaddr</i></li></ul>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><li><i>uci set network.mobile.apn=example</i></li>Changes mobile APN value to "example".</td> | + | <td><ul><li><i>uci set network.mobile.apn=example</i></li></ul>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><li><i>uci show openvpn</i></li>Returns the contents of the "openvpn" config file.</td> | + | <td><ul><li><i>uci show openvpn</i></li></ul>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><li><i>uci show network.lan</i></li>Returns the configuration of the "lan" section from the "network" config file.</td> | + | <td><ul><li><i>uci show network.lan</i></li></ul>Returns the configuration of the "lan" section from the "network" config file.</td> |
</tr> | </tr> | ||
<!-- | <!-- | ||
Line 431: | Line 438: | ||
===API rule=== | ===API rule=== | ||
---- | ---- | ||
− | + | API allows creating, reading, updating, or deleting configurations using the allowed API endpoints from a list. | |
− | [[File:Networking rutos manual mobile utilities sms utilities modify sms rule api | + | [[File:Networking rutos manual mobile utilities sms utilities modify sms rule api {{{dualmodem}}}_v3.png|border|class=tlt-border]] |
---- | ---- | ||
The following are syntax examples for the API rule: | The following are syntax examples for the API rule: | ||
Line 444: | Line 451: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>api <b>get</b> < | + | <td>api <b>get</b> <method>.<config>.<section></td> |
− | <td>Returns | + | <td>Returns specified config options.</td> |
− | <td><li><i> | + | <td><ul><li><i>api get /auto_reboot/periodic/config</i></li></ul>Returns periodic reboot options.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>api <b>post</b><method> <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><li><i> | + | <td><ul><li><i>api post /auto_reboot/periodic/config {"data": {"action": "1", "period": "week", "days": ["mon"], "time": ["12:00"]}}</i></li></ul>Creates a periodic reboot configuration with options to reboot device every monday on 12:00.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>api <b>put</b> <method> <config>.<section>.<option_name>="value"</td> |
− | <td> | + | <td>Edits a specified config options.</td> |
− | <td><li><i> | + | <td><ul><li><i>api put /auto_reboot/periodic/config/{id} {"data": { "enable": "1"}}</i></li></ul>Sets a specified periodic reboot config to enabled.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>api <b>delete</b> <method> <config>.<section>.<config_id></td> |
− | <td> | + | <td>Deletes a specified configuration.</td> |
− | <td>< | + | <td><ul><li><i>api delete /auto_reboot/periodic/config/{id}</i></li></ul>Deletes a specified periodic reboot configuration.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> | ||
− | |||
− | |||
===Custom Rules=== | ===Custom Rules=== | ||
Line 493: | Line 486: | ||
<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}}}_v3.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 509: | Line 502: | ||
<tr> | <tr> | ||
<td>Access</td> | <td>Access</td> | ||
− | <td>mobile_data | sms_delete | sms_list | sms_read | sms_send | sms_total; default: <b>mobile_data, sms_delete, sms_list, sms_read, sms_send, sms_total</b></td> | + | <td>mobile_data | mobile_sim_pin | sms_delete | sms_list | sms_read | sms_send | sms_total; default: <b>mobile_data, sms_delete, sms_list, sms_read, sms_send, sms_total</b></td> |
<td>Methods available for Post/Get. All methods are allowed if this list is left empty.</td> | <td>Methods available for Post/Get. All methods are allowed if this list is left empty.</td> | ||
</tr> | </tr> | ||
Line 553: | Line 546: | ||
<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 576: | Line 566: | ||
<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 628: | Line 617: | ||
<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}}}.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_auto_reply_dualmodem_{{{dualmodem}}}_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 668: | Line 657: | ||
<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: | ||
− | + | <ul> | |
− | + | <li>Everyone</li> | |
− | + | <li>Listed numbers</li> | |
− | + | <li>From user group</li> | |
+ | </ul> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 690: | Line 680: | ||
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_v2.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 717: | Line 707: | ||
<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> | ||
+ | <td>Mode</td> | ||
+ | <td>default: '''Everyone'''</td> | ||
+ | <td>Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options: | ||
+ | <ul> | ||
+ | <li>Everyone</li> | ||
+ | <li>Listed numbers</li> | ||
+ | <li>From phone group</li> | ||
+ | </ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Encode message text to Base64</td> | ||
+ | <td>off | on; default: <b>off</b></td> | ||
+ | <td>Message text will be encoded to a Base64 string. Enable this to preserve Unicode characters in the 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: <li>Ignore</li> <li>Verify</li> | + | <td>Select whether to ignore or verify server certificate. Available options: <ul><li>Ignore</li> <li>Verify</li></ul> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 727: | Line 733: | ||
<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: <li>Get</li> <li>Post</li> | + | <td>Choose witch HTTP request method will be used. Available options: <ul><li>Get</li> <li>Post</li></ul> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 754: | Line 760: | ||
<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> | ||
</table> | </table> | ||
Line 815: | Line 811: | ||
<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: | ||
− | + | <ul> | |
− | + | <li>Everyone</li> | |
− | + | <li>Listed numbers</li> | |
− | + | <li>From user group</li> | |
+ | </ul> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 832: | Line 829: | ||
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_v2.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 857: | Line 854: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Include 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> | ||
+ | <td>Mode</td> | ||
+ | <td>default: '''Everyone'''</td> | ||
+ | <td>Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options: | ||
+ | <ul> | ||
+ | <li>Everyone</li> | ||
+ | <li>Listed numbers</li> | ||
+ | <li>From user group</li> | ||
+ | </ul> | ||
+ | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 867: | Line 875: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Sender's email account</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 875: | Line 883: | ||
<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> | ||
</table> | </table> | ||
Line 894: | Line 892: | ||
<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}}}_v2.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 938: | Line 936: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>SMS limit</td> | + | <td>SMS PDU limit</td> |
<td>integer; default: <b>5</b></td> | <td>integer; default: <b>5</b></td> | ||
− | <td> | + | <td>Longer email text will be sent in multiple PDUs (Protocol Data Units), each of them is approximately 130 characters. Specify maximum allowed PDU count</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 979: | Line 977: | ||
===SMPP=== | ===SMPP=== | ||
---- | ---- | ||
− | <b>Short Message Peer-to-Peer</b> (<b>SMPP</b>) is a protocol used for exchanging SMS messages between Short Message Service Centers (SMSC) and/or External Short Messaging Entities (ESME). The figure below is an example of the SMPP section and the table below provides information on the configuration fields contained in that section: | + | <b>Short Message Peer-to-Peer</b> (<b>SMPP</b>) is a protocol used for exchanging SMS messages between Short Message Service Centers (SMSC) and/or External Short Messaging Entities (ESME). It supports both IPv4 and IPv6 addresses. The figure below is an example of the SMPP section and the table below provides information on the configuration fields contained in that section: |
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_smpp_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_mobile_utilities_sms_gateway_smpp_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] | ||
Line 1,015: | Line 1,013: | ||
</tr>|}} | </tr>|}} | ||
</table> | </table> | ||
− | {{# | + | {{#switch:{{{name}}}| TRB255 | TRB256 = | #default = |
==Call Utilities== | ==Call Utilities== | ||
Line 1,028: | Line 1,026: | ||
---- | ---- | ||
To create a new rule, select an 'Action' and click the 'Add' button. After this, a new configuration window should appear. | To create a new rule, select an 'Action' and click the 'Add' button. After this, a new configuration window should appear. | ||
− | |||
− | |||
− | |||
− | [[File: | + | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_general_{{{dualmodem}}}_v4.png|border|class=tlt-border]] |
+ | |||
+ | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_authorization_v1.png|border|class=tlt-border]] | ||
Line 1,041: | Line 1,038: | ||
[[File:Networking_rutos_manual_mobile_utilities_call_utilities_incoming_calls.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_mobile_utilities_call_utilities_incoming_calls.png|border|class=tlt-border]] | ||
}} | }} | ||
+ | |||
==Messages== | ==Messages== | ||
Line 1,049: | Line 1,047: | ||
In the <b>Read Messages</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. | In the <b>Read Messages</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:Networking_rutos_manual_mobile_utilities_messages_read_messages_dualmodem_{{{dualmodem}}} | + | [[File:Networking_rutos_manual_mobile_utilities_messages_read_messages_dualmodem_{{{dualmodem}}}_v3.png|border|class=tlt-border]] |
===Send Messages=== | ===Send Messages=== |
Revision as of 11:58, 22 April 2024
The information in this page is updated in accordance with firmware version .
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. |
Change profile | no default text | Is used to change profiles on the device. Include the name of the profile that you wish to change to after the rule's SMS text, for example if SMS text is set to changeprof:
|
Execute custom script | - | Executes a custom shell script. |
Reset moble connection | reset_conn | Resets mobile connection. Useful when you want to reconnect to the best available operator. |
Reload config | config_reload | Reloads the config and all affected services. |
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. |
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}}}_WAN#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. |
Restore to user's defaults | userdefaults | Restores user's default configuration on the device. [[{{{name}}}_Maintenance#Create_default_configuration|Click here]] for more information on User's default configuration. |
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. |
API | api | Is used to change the configuration settings on the device. Click here for more information on the UCI API rule. |
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 admin password authorization:
admin01 vpnon
(replace admin01 with your device's admin password) - By password - include the configured custom password before a rule's SMS Text. For example, to execute the sshon rule with password authorization:
Custompw1 sshon
(replace Custompw1 with your configured custom password)
Modify SMS Rule
Every SMS rule can be edited to your liking. To begin configuring a rule, click the click the 'Edit' button under "Actions" column:
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
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general_dualmodem_{{{dualmodem}}}_v3.png|border|class=tlt-border]]
- 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 Message forwarding 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, password or none). If By password is selected a Password field will appear and a custom password will be required. A custom password must have at least one uppercase letter, one lowercase letter, one number and must be from a minimum of 8 to a maximum of 80 characters in length.
- 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}}}_{{{dualmodem}}}_v2.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=3g
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=3g 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.
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_uci_{{{dualmodem}}}_v4.png|border|class=tlt-border]]
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.
Disclaimer: do not enclose values in escape characters like you would when executing UCI commands via CLI. For example: uci set network.mobile.apn="example" will cause an error in SMS API and your value will be altered, as a result, UCI commands execution will fail. Instead, simply write uci set network.mobile.apn=example without any escape characters or quotes.
API rule
API allows creating, reading, updating, or deleting configurations using the allowed API endpoints from a list.
[[File:Networking rutos manual mobile utilities sms utilities modify sms rule api {{{dualmodem}}}_v3.png|border|class=tlt-border]]
The following are syntax examples for the API rule:
Structure example | Description | SMS text example |
---|---|---|
api get <method>.<config>.<section> | Returns specified config options. |
|
api post<method> <config>.<section>.<option_name>="value" | Sets the value of a specified configuration option. |
|
api put <method> <config>.<section>.<option_name>="value" | Edits a specified config options. |
|
api delete <method> <config>.<section>.<config_id> | Deletes a specified configuration. |
|
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}}}_v3.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Enable SMS management functionality through POST/GET |
Access | mobile_data | mobile_sim_pin | sms_delete | sms_list | sms_read | sms_send | sms_total; default: mobile_data, sms_delete, sms_list, sms_read, sms_send, sms_total | Methods available for Post/Get. All methods are allowed if this list is left empty. |
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://style="color: black;">192.168.1.1/cgi-bin/sms_read?username=user1&password=user_pass&number=1 |
Send mobile message to a single number | http://style="color: black;">192.168.1.1/cgi-bin/sms_send?username=user1&password=user_pass&number=0037060000001&text=testmessage |
Send mobile message to a group | http://style="color: black;">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://style="color: black;">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}}}_v1.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 |
Mode | default: Everyone | Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options:
|
Encode message text to Base64 | off | on; default: off | Message text will be encoded to a Base64 string. Enable this to preserve Unicode characters in the 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 |
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}}}_v1.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: Everyone | Specifies whether to auto reply to every phone number or just just specified phone numbers. 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 |
Include sender's number | off | on; default: off | Enable/disable adding sender phone number at the end of email text body |
Mode | default: Everyone | Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options:
|
Subject | default: none | Subject of an email. Allowed characters (a-zA-Z0-9!@#$%&*+-/=?^_`{|}~. ) |
Sender's email account | 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._%+-) |
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}}}_v2.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 (TLS) | off | on; default: off | Enables/diables secure connection (TLS 1.2 and up). TLS (Transport Layer Security) is a cryptographic protocol designed to provide communications security over a computer network. TLS uses a combination of symmetric cryptography (sigle secret key known to both sender and receiver to encrypt data) and asymmetric cryptography (a public key known to everyone and a private or secret key known only to the recipient of the message) to encrypt data. |
Verify TLS certificate validity | off | on; default: off | Enables/disables TLS certificate validation. When enabled verifies the validity of the POP3 server certificate |
SMS PDU limit | integer; default: 5 | Longer email text will be sent in multiple PDUs (Protocol Data Units), each of them is approximately 130 characters. Specify maximum allowed PDU count |
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)
Recommendations note:
- Email to SMS application can't guarantee best results when working with flooded email inbox. It is recommended to have less than 100 emails in the inbox.
- Less emails - better performance.
- In most cases it is best to use dedicated inbox.
SMPP
Short Message Peer-to-Peer (SMPP) is a protocol used for exchanging SMS messages between Short Message Service Centers (SMSC) and/or External Short Messaging Entities (ESME). It supports both IPv4 and IPv6 addresses. The figure below is an example of the SMPP section and the table below provides information on the configuration fields contained in that section:
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_smpp_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns SMPP on or off. |
User name | string; default: admin | User name used for authentication on the SMPP server. |
Password | string; default: admin01 | Password used for authentication on the SMPP server. |
Server port | integer [0..65535]; default: 2775 | SMPP server port. |
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. After this, a new configuration window should appear.
[[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_general_{{{dualmodem}}}_v4.png|border|class=tlt-border]]
Incoming Calls
This option specifies the action to be performed on incoming calls. Call utilities rules will keep getting executed while the call is active.
Messages
With the help of the Messages window you can read and send SMS messages.
Read Messages
In the Read Messages 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:Networking_rutos_manual_mobile_utilities_messages_read_messages_dualmodem_{{{dualmodem}}}_v3.png|border|class=tlt-border]]
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}}}_v2.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Save messages to | SIM card | Modem storage; default: SIM card | Specify location where to save messages |
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]]