Line 1: |
Line 1: |
| + | <p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.4'''] firmware version .</p> |
| ==Introduction== | | ==Introduction== |
− | <span style="color: red;">The information in this page is updated in accordance with the <span style="color: #0054A6;"><b>RUTXXX_R_00.07.04</b></span> firmware version.</span>
| |
| | | |
| '''JSON-RPC''' is a remote procedure call protocol encoded in JSON. It is a very simple protocol (and very similar to XML-RPC), defining only a few data types and commands. JSON-RPC allows for notifications (data sent to the server that does not require a response) and for multiple calls to be sent to the server which may be answered out of order. | | '''JSON-RPC''' is a remote procedure call protocol encoded in JSON. It is a very simple protocol (and very similar to XML-RPC), defining only a few data types and commands. JSON-RPC allows for notifications (data sent to the server that does not require a response) and for multiple calls to be sent to the server which may be answered out of order. |
Line 27: |
Line 27: |
| ---- | | ---- |
| First, you must obtain a '''Session ID'''. In order to do so, you must send a HTTP POST request to the router asking for it. | | First, you must obtain a '''Session ID'''. In order to do so, you must send a HTTP POST request to the router asking for it. |
− | <ul>
| + | |
− | <li>Enter the router's IP address into the URL field '''http://192.168.1.1/ubus''' (''use LAN IP for local access, WAN IP for remote access'').</li>
| + | 1. Enter the router's IP address into the URL field '''http://192.168.1.1/ubus''' (''use LAN IP for local access, WAN IP for remote access''),<br> |
− | <li>Change the orange code fields with router's username and password (''Or change it into the '''Postman User Auth.''' field.'')</li>
| + | 2. Open the '''Body''' section,<br> |
− | <li>Then paste the following command into the '''Body or Content to send''' field:</li>
| + | 3. Select '''raw''',<br> |
− | </ul>
| + | 4. Then paste the following command into the '''Body or Content to send''' field: |
| | | |
| { | | { |
Line 43: |
Line 43: |
| } | | } |
| | | |
− | ''The section highlighted in orange is the router's admin password which by default is admin01. Replace this part with your own router's password.''<br> | + | '''Note''': The section highlighted in orange is the router's admin password which by default is admin01. Replace this part with your own router's password. |
− | <ul>
| + | |
− | <li>Once you have everything in order, click '''Send''':</li>
| + | 5. Once you have everything in order, click '''Send''',<br> |
− | </ul>
| + | 6. The output should contain the '''Session ID'''. |
− | [[File:GETTING ID.jpg|border|class=tlt-border]] | + | [[File:Postman login.png|border|center|class=tlt-border|697x621px]] |
− | <br>
| + | |
− | <ul>
| + | |
− | Here's what the response should look like (The Session ID is shown in the sixth red rectangle):
| + | Copy the Session ID since you'll be needing it when issuing other commands to the router. |
| | | |
− | <li>Copy the Session ID since you'll be needing it when issuing other commands to the router.</li>
| |
− | </ul>
| |
| '''NOTE:''' if later on your commands stop working and you get a Response like this: <br> | | '''NOTE:''' if later on your commands stop working and you get a Response like this: <br> |
| | | |
Line 70: |
Line 68: |
| ---- | | ---- |
| Now that you have obtained a Session ID, you can issue commands to the router. Let's start with commands that return information about the router. | | Now that you have obtained a Session ID, you can issue commands to the router. Let's start with commands that return information about the router. |
− | ====Getting '''[[RSSI]]'''==== | + | ====Getting signal levels==== |
| ---- | | ---- |
| { | | { |
Line 86: |
Line 84: |
| } | | } |
| | | |
− | The test highlighted in red is your Session ID, and highlighted in orange are the command and the parameter. In this example, we're using a '''gsmctl -q''' command that returns the router's RSSI (signal strength) value. | + | The test highlighted in red is your Session ID, and highlighted in orange are the command and the parameter. In this example, we're using a '''gsmctl -q''' command that returns the router's signal levels. |
| | | |
− | [[File:GETTING RSSI3.jpg|border|class=tlt-border]] | + | [[File:Postman gsmct signal.png|border|center|class=tlt-border|730x662px]] |
| | | |
− | Look for '''stdout''' in the post response: <span style="color:green">'''"stdout":"-69\n'''</span>". This tells us that the router's current signal strength is <span style="color:green">'''-69 dBm'''</span>. | + | Look for '''stdout''' in the post response: <span style="color:green">'''"stdout": "RSSI: -54\nRSRP: -87\nSINR: 8\nRSRQ: -12\n"'''</span>. This tells us that the router's current signal strength levels. |
| ---- | | ---- |
| | | |
Line 112: |
Line 110: |
| Again the command and the parameter are highlighted in orange. In this case the '''cat''' command is used to view the contents of the '''/etc/config/network''' file. The Response is: | | Again the command and the parameter are highlighted in orange. In this case the '''cat''' command is used to view the contents of the '''/etc/config/network''' file. The Response is: |
| | | |
− | [[File:GETTING NETWORK.jpg|border|class=tlt-border]] | + | [[File:Postman network config.png|border|center|class=tlt-border|732x660px]] |
| | | |
| ===Setting router parameters=== | | ===Setting router parameters=== |
Line 159: |
Line 157: |
| If the issued command was a success, you should see a Response like this:<br> | | If the issued command was a success, you should see a Response like this:<br> |
| | | |
− | [[File:CHANGING SSID.jpg|border|class=tlt-border]] | + | [[File:Postman uci set wireless.png|border|center|class=tlt-border|724x689px]] |
| | | |
| ====UCI COMMIT==== | | ====UCI COMMIT==== |
Line 178: |
Line 176: |
| If the commit was successful, you should see the same message as before: | | If the commit was successful, you should see the same message as before: |
| | | |
− | [[File:COMMIT.jpg|border|class=tlt-border]] | + | [[File:Postman uci commit.png|border|center|class=tlt-border|729x532px]] |
| | | |
| ====RELOAD_CONFIG==== | | ====RELOAD_CONFIG==== |
Line 194: |
Line 192: |
| } | | } |
| The command itself is highlighted in orange.<br> | | The command itself is highlighted in orange.<br> |
− | [[File:Networking_rutos_configuration_example_Monitoring_via_JSON-RPC_windows_RELOAD_CONFIG.png|border|class=tlt-border]]<br> | + | [[File:Postman uci reload.png|border|center|class=tlt-border|730x586px]] |
| + | |
| + | Navigate to the router's WebUI → Network → Wireless and see if the SSID has changed. |
| + | |
| + | [[File:Webui ssid changed.png|border|center|class=tlt-border|778x156px]] |
| | | |
| ====Setting Multiple Parameters==== | | ====Setting Multiple Parameters==== |