Jump to content
  • EN

Template:Networking rutos manual mobile utilities: Difference between revisions

Template:Networking rutos manual mobile utilities (view source)

Revision as of 12:59, 22 January 2024

9,589 bytes added ,  22 January
no edit summary
VisualWikitext
No edit summary
No edit summary
(92 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{Template:Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05.1
| series = {{{series}}}
| series     = {{{series}}}
| name  = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| 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: 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: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
==Summary==


{{{name}}} routers have an extensive amount of various SMS control utilities. SMS Utilities can be used to set/get
The <b>Mobile Utilities</b> page is used to configure various SMS{{#switch:{{{name}}}| TRB255 | TRB256= | #default=&nbsp;and Call}} related device control options and to read, send and manage SMS messages and SMS storage space.
configurations, monitor and issue commands to the router.
 
This manual page provides an overview of the Mobile Utilities page in {{{name}}} devices.


==SMS Utilities==
==SMS Utilities==
Line 14: Line 21:
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_sms_rules.png|border|class=tlt-border]]
[[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 all possible SMS action. 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.


<table class="nd-othertables_2" style="width: 100%;">
<table class="nd-othertables_2" style="width: 100%;">
Line 24: Line 31:
     <tr>
     <tr>
         <td><b>Change I/O state</b></td>
         <td><b>Change I/O state</b></td>
         <td>ioset</td>
         <td><i>ioset</i></td>
         <td>Changes the state of a selected output.</td>
         <td>Changes the state of a selected output.</td>
     </tr>|}}
     </tr>|}}
     <tr>
     <tr>
         <td><b>Change mobile settings</b></td>
         <td><b>Change mobile settings</b></td>
         <td>cellular</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>
        <td><b>Change profile</b></td>
        <td><i>no default text</i></td>
        <td>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 <i>changeprof</i>:
            <ul>
                <li><i>changeprof default</i></li>
                <li><i>changeprof custom</i></li>
            </ul>
        </td>
    </tr>
    <tr>
        <td><b>Execute custom script</b></td>
        <td><i>-</i></td>
        <td>Executes a custom shell script.</td>
    </tr>
     </tr>{{#ifeq: {{{dualsim}}} | 1 |{{#ifeq: {{{dualmodem}}} | 0 |
     <tr>
     <tr>
         <td><b>Force SIM switch</b></td>
         <td><b>Force SIM switch</b></td>
         <td>switch_sim</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>
        <td><b>Reset moble connection</b></td>
        <td><i>reset_conn</i></td>
        <td>Resets mobile connection. Useful when you want to reconnect to the best available operator.</td>
    </tr>
    <tr>
        <td><b>Reload config</b></td>
        <td><i>config_reload</i></td>
        <td>Reloads the config and all affected services.</td>
    </tr>
     <tr>
     <tr>
         <td><b>FW upgrade from server</b></td>
         <td><b>FW upgrade from server</b></td>
         <td>fw_upgrade</td>
         <td><i>fw_upgrade</i></td>
         <td>Upgrades the device's firmware (provided a new version is available on the FOTA server).</td>
         <td>Upgrades the device's firmware (provided a new version is available on the FOTA server).</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Get list of profiles</b></td>
         <td><b>Get list of profiles</b></td>
         <td>profdisp</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>{{#ifeq: {{{gps}}} | 1 |
     <tr>
     <tr>
         <td><b>GPS control</b></td>
         <td><b>GPS control</b></td>
         <td>gpson</td>
         <td><i>gpson</i></td>
         <td>Turns GPS on.</td>
         <td>Turns GPS on.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>GPS coordinates</b></td>
         <td><b>GPS coordinates</b></td>
         <td>gps</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>
         <td>ipunblock</td>
         <td><i>ipunblock</i></td>
         <td>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:
         <td>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:
             <ul>
             <ul>
                 <li><i>ipunblock</i> - clears the block list (unblocks Web/SSH access for all previously blocked devices).</li>
                 <li><i>ipunblock</i> - clears the block list (unblocks Web/SSH access for all previously blocked devices).</li>
                 <li><i>ipunblock 192.168.1.2</i> - removes this IP address from the block list (unblock Web/SSH access for that device).</li>
                 <li><i>ipunblock 192.168.1.2</i> - removes this IP address from the block list (unblocks Web/SSH access for that device).</li>
             </ul>
             </ul>
         </td>
         </td>
Line 69: Line 101:
     <tr>
     <tr>
         <td><b>I/O status</b></td>
         <td><b>I/O status</b></td>
         <td>iostatus</td>
         <td><i>iostatus</i></td>
         <td>Sends a status report message on the state of the device's inputs and outputs.</td>
         <td>Sends a status report message on the state of the device's inputs and outputs.</td>
     </tr>|}}
     </tr>|}}
     <tr>
     <tr>
         <td><b>Manage OpenVPN</b></td>
         <td><b>Manage OpenVPN</b></td>
         <td>vpnon</td>
         <td><i>vpnon</i></td>
         <td>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:
         <td>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:
             <ul>
             <ul>
Line 84: Line 116:
     <tr>
     <tr>
         <td><b>Manage OpenVPN</b></td>
         <td><b>Manage OpenVPN</b></td>
         <td>vpnoff</td>
         <td><i>vpnoff</i></td>
         <td>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:
         <td>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:
             <ul>
             <ul>
Line 91: Line 123:
             </ul>
             </ul>
         </td>
         </td>
    </tr>{{#ifeq:{{{series}}}|TRB5||
    <tr>
        <td><b>Mobile Data limit status</b></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}}}_WAN#Mobile_Data_Limit|Mobile Data Limit]] enabled) </td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Mobile data limit status</b></td>
         <td><b>Mobile Data usage reset</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}}}_Interfaces#Mobile_Data_Limit|Mobile Data Limit]] enabled) </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>
         <td>monitoring_status</td>
         <td><i>monitoring_status</i></td>
         <td>Sends a status report message that includes the RMS connection type, state and the device serial number and MAC address.</td>
         <td>Sends a status report message that includes the RMS connection type, state and the device serial number and MAC address.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>More</b></td>
         <td><b>More</b></td>
         <td>more</td>
         <td><i>more</i></td>
         <td>Displays next part of a composite response message (more than 160 characters).</td>
         <td>Displays next part of a composite response message (more than 160 characters).</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>OpenVPN status</b></td>
         <td><b>OpenVPN status</b></td>
         <td>vpnstatus</td>
         <td><i>vpnstatus</i></td>
         <td>Sends a status report message on all OpenVPN connections.</td>
         <td>Sends a status report message on all OpenVPN connections.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Reboot</b></td>
         <td><b>Reboot</b></td>
         <td>reboot</td>
         <td><i>reboot</i></td>
         <td>Reboots the device.</td>
         <td>Reboots the device.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Restore to default</b></td>
         <td><b>Restore to default</b></td>
         <td>restore</td>
         <td><i>restore</i></td>
         <td>Restores factory settings on the device.</td>
         <td>Restores factory settings on the device.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>RMS action</b></td>
         <td><b>RMS action</b></td>
         <td>rms_on</td>
         <td><i>rms_on</i></td>
         <td>Turns RMS connection on.</td>
         <td>Turns RMS connection on.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>RMS action</b></td>
         <td><b>RMS action</b></td>
         <td>rms_off</td>
         <td><i>rms_off</i></td>
         <td>Turns RMS connection off.</td>
         <td>Turns RMS connection off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>RMS connect</b></td>
         <td><b>RMS connect</b></td>
         <td>rms_connect</td>
         <td><i>rms_connect</i></td>
         <td>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]].</td>
         <td>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]].</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>RMS status</b></td>
         <td><b>RMS status</b></td>
         <td>rms_status</td>
         <td><i>rms_status</i></td>
         <td>Sends a status report message on the state of the connection to RMS.</td>
         <td>Sends a status report message on the state of the connection to RMS.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Send status</b></td>
         <td><b>Send status</b></td>
         <td>status</td>
         <td><i>status</i></td>
         <td>Sends a status report message.</td>
         <td>Sends a status report message.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>SSH access control</b></td>
         <td><b>SSH access control</b></td>
         <td>sshon</td>
         <td><i>sshon</i></td>
         <td>Turns remote and local (by default) SSH access on. This rule can be modified to only include local SSH access.</td>
         <td>Turns remote and local (by default) SSH access on. This rule can be modified to only include local SSH access.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>SSH access control</b></td>
         <td><b>SSH access control</b></td>
         <td>sshoff</td>
         <td><i>sshoff</i></td>
         <td>Turns SSH access off.</td>
         <td>Turns SSH access off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Switch mobile data</b></td>
         <td><b>Switch mobile data</b></td>
         <td>mobileon</td>
         <td><i>mobileon</i></td>
         <td>Turns mobile data usage on.</td>
         <td>Turns mobile data usage on.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Switch mobile data</b></td>
         <td><b>Switch mobile data</b></td>
         <td>mobileoff</td>
         <td><i>mobileoff</i></td>
         <td>Turns mobile data usage off.</td>
         <td>Turns mobile data usage off.</td>
     </tr>{{#ifeq: {{{wifi}}} | 1 |
     </tr>{{#ifeq: {{{wifi}}} | 1 |
     <tr>
     <tr>
         <td><b>Switch WiFi</b></td>
         <td><b>Switch WiFi</b></td>
         <td>wifion</td>
         <td><i>wifion</i></td>
         <td>Turns the WiFi radio on.</td>
         <td>Turns the WiFi radio on.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Switch WiFi</b></td>
         <td><b>Switch WiFi</b></td>
         <td>wifioff</td>
         <td><i>wifioff</i></td>
         <td>Turns the WiFi radio off.</td>
         <td>Turns the WiFi radio off.</td>
     </tr>|}}
     </tr>|}}
     <tr>
     <tr>
         <td><b>UCI API</b></td>
         <td><b>UCI API</b></td>
         <td>uci</td>
         <td><i>uci</i></td>
         <td>Is used to change the configuration settings on the device. [[Click here|#UCI_API_rule]] for more information on the UCI API rule.</td>
         <td>Is used to change the configuration settings on the device. [[#UCI_API_rule|Click here]] for more information on the UCI API rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
        <td><b>Restore to user's defaults</b></td>
        <td><i>userdefaults</i></td>
        <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}}}
| TRB141|TRB142|TRB145=
| #default=<tr>
         <td><b>Wake on LAN</b></td>
         <td><b>Wake on LAN</b></td>
         <td>wakeup</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>
         <td><b>Web access control</b></td>
         <td><b>Web access control</b></td>
         <td>webon</td>
         <td><i>webon</i></td>
         <td>Turns remote and local (by default) HTTP and HTTPS access on. This rule can be modified to only include local HTTP/HTTPS access.</td>
         <td>Turns remote and local (by default) HTTP and HTTPS access on. This rule can be modified to only include local HTTP/HTTPS access.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>Web access control</b></td>
         <td><b>Web access control</b></td>
         <td>weboff</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>
        <td><b>API</b></td>
        <td><i>api</i></td>
        <td>Is used to change the configuration settings on the device. [[#API_rule|Click here]] for more information on the UCI API rule.</td>
     </tr>
     </tr>
</table>
</table>
Line 206: Line 254:
     <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 password authorization:<pre>admin01 vpnon</pre> <font size="-1"><i>(replace admin01 with your device's admin password)</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 admin password authorization:<pre>admin01 vpnon</pre> <font size="-1"><i>(replace admin01 with your device's admin password)</i></font></li>
    <li><b>By password</b> - include the configured custom password before a rule's <i>SMS Text</i>. For example, to execute the <i>sshon</i> rule with password authorization:<pre>Custompw1 sshon</pre> <font size="-1"><i>(replace Custompw1 with your configured custom password)</i></font></li>
</ul>
</ul>


Line 219: Line 268:
<b>General settings</b>
<b>General settings</b>
----
----
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_general_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]


<ol>
<ol>
Line 226: Line 275:
     <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>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 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 text</b> box is used to modify the text that should be included in an SMS rule's response message.</li>
    {{#ifeq: {{{dualmodem}}} | 1 |<li>The <b>Modem</b> option is used to specify which modem to get<nowiki>/</nowiki>set information to<nowiki>/</nowiki>from.</li>
    <li>The <b>Gateway modem</b> option is used to specify which modem to use for sending SMS.</li>|}}
     <li>The <b>Text messagetext</b> box is used to modify the text that should be included in an SMS rule's response message.</li>
</ol>
</ol>


Line 235: Line 286:


<ol>
<ol>
     <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>Authorization method</b> dropdown selection specifies the type of authorization an SMS rule requires (device admin password, serial number, password or none). If <b>By password</b> is selected a <b>Password</b> 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. </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 245: 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}}}.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_cellular_dualsim_{{{dualsim}}}_{{{dualmodem}}}.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 257: Line 308:
     <tr>
     <tr>
         <td><b>apn=</b></td>
         <td><b>apn=</b></td>
         <td>Sets APN</td>
         <td>Sets APN.</td>
         <td><i>cellular apn=internet</i></td>
         <td><i>cellular apn=internet</i></td>
    </tr>
    <tr>
        <td><b>auto_apn=</b></td>
        <td>Turns auto APN on or off. Possible values are 0/1.</td>
        <td><i>cellular auto_apn=1</i></td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><b>dialnumber=</b></td>
         <td><b>dialnumber=</b></td>
        <td>e.g., *99***1#</td>
         <td>Sets Dialing number.</td>
         <td>Sets Dialing number</td>
         <td><i>cellular dialnumber=*99***1#</i></td>
         <td><i>cellular dialnumber=*99***1#</i></td>
     </tr>
     </tr>
Line 281: Line 336:
         <td>Sets the service mode. Possible values are:
         <td>Sets the service mode. Possible values are:
             <ul>
             <ul>
                 <li>3gonly</li>
                 {{#ifeq:{{{2g}}}|1|<li>2g</li>|}}
                 <li>4gonly</li>
                 {{#ifeq:{{{3g}}}|1|<li>3g</li>|}}
                {{#ifeq:{{{4g}}}|1|<li>lte</li>|}}
                {{#ifeq:{{{5g}}}|1|<li>nr5g</li>|}}
                <li>mixture of any two modes (ex.: 3g_lte)</li>
                 <li>auto</li>
                 <li>auto</li>
             </ul>
             </ul>
Line 312: Line 370:
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=3gonly
  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:
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
  cellular apn=internet auth_mode=pap service=3g 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:
 
cellular apn=internet
 
or if you want to turn auto APN on:
 
cellular auto_apn=1


===UCI API rule===
===UCI API rule===
----
----
The <b>UCI API</b> rule is used to configure any parameters on the device. The following are syntax examples for the UCI API rule:
The <b>UCI API</b> rule is used to configure any parameters on the device.
 
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_modify_sms_rule_uci_v2.png|border|class=tlt-border]]
----
The following are syntax examples for the UCI API rule:


<table class="nd-othertables_2" style="width: 100%;">
<table class="nd-othertables_2" style="width: 100%;">
     <tr>
     <tr>
         <th width=25%>Example structure</th>
         <th width=30%>Structure example</th>
         <th width=25%>Description</th>
         <th width=35%>Description</th>
         <th width=50%>Example SMS text</th>
         <th width=30%>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><i>uci get network.wan.ipaddr</i> - 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><i>uci set network.mobile.apn=example</i> - 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><i>uci show openvpn</i> - 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><i>uci show network.lan</i> - 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>
<!--
     <tr>
     <tr>
         <td>uci <b>delete</b> <config>.<section></td>
         <td>uci <b>delete</b> <config>.<section></td>
         <td>Deletes the specified section in a configuration file. To avoid operation issues, please use this command to delete optional configuration sections only (not mandatory ones).</td>
         <td>Deletes the specified section in a configuration file. To avoid operation issues, please use this command to delete optional configuration sections only (not mandatory ones).</td>
         <td><i>uci delete network.lan4</i> - deletes a network interface called "lan4".</td>
         <td><li><i>uci delete network.lan4</i></li>Deletes a network interface called "lan4".</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>uci <b>delete</b> <config>.<section>.<option_name></td>
         <td>uci <b>delete</b> <config>.<section>.<option_name></td>
         <td>Deletes the specified configuration option. To avoid operation issues, please use this command to delete optional configuration options only (not mandatory ones).</td>
         <td>Deletes the specified configuration option. To avoid operation issues, please use this command to delete optional configuration options only (not mandatory ones).</td>
         <td><i>uci delete dhcp.lan.force</i> - deletes the "force" option for DHCP server of the "lan" interface (which in turn disables the "Force DHCP" function of that DHCP server).</td>
         <td><li><i>uci delete dhcp.lan.force</i></li>Deletes the "force" option for DHCP server of the "lan" interface (which in turn disables the "Force DHCP" function of that DHCP server).</td>
     </tr>
     </tr>
-->
</table>
</table>


As you can see, the UCI rule requires that you know the names of the configuration files and the names of the sections and parameters that they hold. You can find the config file list and some examples of UCI usage in general in our '''[[UCI command usage]]''' 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.
 
'''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 v1.png|border|class=tlt-border]]
----
The following are syntax examples for the API rule:
 
<table class="nd-othertables_2" style="width: 100%;">
    <tr>
        <th width=30%>Structure example</th>
        <th width=35%>Description</th>
        <th width=30%>SMS text example</th>
    </tr>
    <tr>
        <td>api <b>get</b> <method>.<config>.<section></td>
        <td>Returns specified config options.</td>
        <td><ul><li><i>api get /auto_reboot/periodic/config</i></li></ul>Returns periodic reboot options.</td>
    </tr>
    <tr>
        <td>api <b>post</b><method> <config>.<section>.<option_name>="value"</td>
        <td>Sets the value of a specified configuration option.</td>
        <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>
        <td>api <b>put</b> <method> <config>.<section>.<option_name>="value"</td>
        <td>Edits a specified config options.</td>
        <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>
        <td>api <b>delete</b> <method> <config>.<section>.<config_id></td>
        <td>Deletes a specified configuration.</td>
        <td><ul><li><i>api delete /auto_reboot/periodic/config/{id}</i></li></ul>Deletes a specified periodic reboot configuration.</td>
    </tr>
</table>


===Custom Rules===
===Custom Rules===
----
----
If default rules do not suit your purposes, you can also configure custom SMS rules. To do so, go to the bottom of the
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 <b>Add Rule</b> section. Enter a custom SMS text, select an Action and click the 'Add' button:
SMS Utilities page, where you will find the '''Add Rule''' tab. Write SMS text, select an Action and press the '''Add'''
button located next to it.


[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_add_rule.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_sms_utilities_add_rule.png|border|class=tlt-border]]
Configuring a new rule is very similar to editing default rules: you are provided with a list of '''Actions''', other
fields are generated in accordance with which '''Action''' you choose.


==SMS Gateway==
==SMS Gateway==
Line 381: 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}}}.png]]
[[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 394: Line 499:
         <td>Enable SMS management functionality through POST/GET
         <td>Enable SMS management functionality through POST/GET
         </td>
         </td>
    </tr>
    <tr>
        <td>Access</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>
     </tr>
     </tr>
{{#ifeq: {{{dualmodem}}} | 1 |
{{#ifeq: {{{dualmodem}}} | 1 |
Line 436: 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
                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</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
                 style="color: black;">192.168.1.1</span>/cgi-bin/sms_send?username=user1&password=user_pass&number=0037060000001&text=testmessage
        </td>
</tr>
<tr>
        <td>Send mobile message to a group</td>
         <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 453: Line 567:
<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
                 style="color: black;">192.168.1.1</span>/cgi-bin/sms_delete?username=user1&password=user_pass&number=1
         </td>
         </td>
Line 505: Line 619:
<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]]
[[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 545: Line 659:
         <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>Everyone</li>
            <li>Listed numbers</li>
                <li>Listed numbers</li>
            <li>From user group</li>
                <li>From user group</li>
            </ul>
         </td>
         </td>
</tr>
</tr>
Line 567: Line 682:
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:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_http.png|border|class=tlt-border]]
[[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 594: Line 709:
         <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 604: Line 735:
         <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 631: Line 762:
         <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 646: Line 769:
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}}}.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_sms_dualmodem_{{{dualmodem}}}_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 688: Line 811:
     <tr>
     <tr>
         <td>Mode</td>
         <td>Mode</td>
         <td>default: '''All messages'''</td>
         <td>default: '''Everyone'''</td>
         <td>Choose which messages are going to be forwarded. Available options: <li>All messages'''
         <td>Specifies whether to auto reply to every phone number or just just specified phone numbers. Available options:
            <li>From listed numbers'''
            <ul>
            <li>From user group'''
                <li>Everyone</li>
                <li>Listed numbers</li>
                <li>From user group</li>
            </ul>
         </td>
         </td>
     </tr>
     </tr>
Line 705: Line 831:
The '''SMS Forwarding To Email''' function forwards SMS messages to email.
The '''SMS Forwarding To Email''' function forwards SMS messages to email.


[[File:Networking_rutos_manual_mobile_utilities_sms_gateway_sms_forwarding_to_email.png|border|class=tlt-border]]
[[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 730: Line 856:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Add sender's number</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 740: Line 877:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Email group</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 748: Line 885:
         <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 765: Line 894:
<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}}}.png|border|class=tlt-border]]
[[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">
     <tr>
     <tr>
         <th>Field name</th>
         <th>Field</th>
       <th>Value</th>
       <th>Value</th>
       <th>Description</th>
       <th>Description</th>
Line 799: Line 928:
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Secure connection (SSL)</td>
     <td>Secure connection (TLS)</td>
         <td>yes | no; default: <b>no</b></td>
         <td>off | on; default: <b>off</b></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>
         <td>Enables/diables secure connection (TLS 1.2 and up). <b>TLS</b> (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.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>SMS limit</td>
    <td>Verify TLS certificate validity</td>
        <td>off | on; default: <b>off</b></td>
        <td>Enables/disables TLS certificate validation. When enabled verifies the validity of the POP3 server certificate</td>
    </tr>
    <tr>
     <td>SMS PDU limit</td>
         <td>integer; default: <b>5</b></td>
         <td>integer; default: <b>5</b></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>
         <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 817: Line 951:
         <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: {{{dualsim}}} | 1 |
     </tr>{{#ifeq: {{{dualmodem}}} | 1 |
     <tr>
     <tr>
         <td>Gateway modem</td>
         <td>Gateway modem</td>
Line 835: Line 969:


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| |
 
<b>Recommendations note</b>:
<ul>
<li>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.</li>
<li>Less emails - better performance.</li>
<li>In most cases it is best to use dedicated inbox. </li>
</ul>
 
===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). 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]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>off | on; default: <b>off</b></td>
      <td>Turns SMPP on or off.</td>
    </tr>
    <tr>
      <td>User name</td>
      <td>string; default: <b>admin</b></td>
      <td>User name used for authentication on the SMPP server.</td>
    </tr>
    <tr>
    <td>Password</td>
        <td>string; default: <b>admin01</b></td>
        <td>Password used for authentication on the SMPP server.</td>
    </tr>
    <tr>
    <td>Server port</td>
        <td>integer [0..65535]; default: <b>2775</b></td>
        <td>SMPP server port.</td>
    </tr>{{#ifeq: {{{dualmodem}}} | 1 |
    <tr>
    <td>Modem</td>
        <td>Primary modem <nowiki>|</nowiki> Secondary modem; default: <b>Primary modem</b></td>
        <td>Modem that will be used for SMPP server communications.</td>
    </tr>|}}
</table>
{{#switch:{{{name}}}| TRB255 | TRB256 = | #default =
==Call Utilities==
==Call Utilities==


Just like SMS Utilities, Call Utilities provide you with the possibility to issue certain commands to the router from
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.
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.
{{#switch: {{{series}}}
| RUT9|RUT2=<b>Note:</b> Devices with <i>EC25-AFxD</i> (where <i>x</i> is any character) modem do not support voice calls. <b>Call Utilities</b> section is not present on devices with these modems. You can find the module present on your device in [[{{{name}}} System]] page.
| #default=
}}


===Call Rules===
===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.
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_edit_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_general_{{{dualmodem}}}_v4.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_authorization_v1.png|border|class=tlt-border]]


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


Call Configuration also has similar Authorization settings.
===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.


[[File:Networking_rutos_manual_mobile_utilities_call_utilities_call_configuration_authorization.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_call_utilities_incoming_calls.png|border|class=tlt-border]]
}}


==Messages==
==Messages==
      
      
With the help of the '''Messages''' 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 SMS===
===Read Messages===
----
----
In the '''Read SMS''' tab 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_1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_messages_read_messages_dualmodem_{{{dualmodem}}}_v3.png|border|class=tlt-border]]


===Send Messages===
===Send Messages===
----
----
The Send Messages tab let's you send SMS messages from the router‘s SIM card.
The <b>Send Messages</b> 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]]
[[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.
All you have to do is enter the recipient’s phone number, type in your message and hit the <b>Send</b> button.


===Storage===
===Storage===
Line 878: Line 1,063:
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}}}.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mobile_utilities_messages_storage_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 887: Line 1,072:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Save messages on SIM</td>
         <td>Save messages to</td>
         <td>off | on; default: <b>on</b></td>
         <td>SIM card | Modem storage; default: <b>SIM card</b></td>
         <td>If this is enabled, messages from SIM card will not be removed after they have been read</td>
         <td>Specify location where to save messages</td>
     </tr>
     </tr>
     <tr>
     <tr>
        <td>Delete forwarded messages</td>
         <td>Memory</td>
        <td>off | on; default: <b>off</b></td>
         <td>-</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: '''Primary modem'''</td>
        <td>Which modem is used</td>
    </tr>|}}
    <tr>
         <td>SIM card memory</td>
         <td> -</td>
         <td>Information about used/available SIM card memory</td>
         <td>Information about used/available SIM card memory</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Leave free space</td>
         <td>Leave free space</td>
         <td>default: '''5'''</td>
         <td>integer; default: <b>5</b></td>
         <td>How much memory (number of messages) should be left free</td>
         <td>How much memory (number of messages) should be left free</td>
     </tr>
     </tr>
</table>
</table>


[[Category:{{{name}}} Services section]]
[[Category: {{{name}}} Services section]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/73115...119537"