Changes

11 bytes removed ,  13:57, 2 May 2018
no edit summary
Line 2: Line 2:  
|+
 
|+
 
| style="border:1px solid white; width: 300px" | [[File:Rms representative.png|250px]]
 
| style="border:1px solid white; width: 300px" | [[File:Rms representative.png|250px]]
| style="border:1px solid white; width: 500px" | <font size="+1">Centralized system</font> <br> Access, monitor and control whole router fleet from within a single, web browser-based interface. Compatible with browsers across all platforms, requires no installation or additional plug-ins.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Centralized system</font> <br> Access, monitor and control whole router fleet from within a single, web browser-based interface. Compatible with browsers across all platforms, requires no installation or additional plug-ins.
 
|-
 
|-
 
|}
 
|}
Line 8: Line 8:  
{| class="wikitable" style="border:2px solid white; background: white"
 
{| class="wikitable" style="border:2px solid white; background: white"
 
|+
 
|+
| style="border:1px solid white; width: 500px" | <font size="+1">Firmware and configuration updates</font> <br> Deploy your desired con­figuration ­template or new ­firmware version to multiple units or groups of units at the same time. Over-the-air bulk upgrade and con­figuration signif­icantly reduces the costs of system maintenance.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Firmware and configuration updates</font> <br> Deploy your desired con­figuration ­template or new ­firmware version to multiple units or groups of units at the same time. Over-the-air bulk upgrade and con­figuration signif­icantly reduces the costs of system maintenance.
 
| style="border:1px solid white; width: 300px" | [[File:Firmware2.png|220px]]
 
| style="border:1px solid white; width: 300px" | [[File:Firmware2.png|220px]]
 
|-
 
|-
Line 16: Line 16:  
|+
 
|+
 
| style="border:1px solid white; width: 300px" | [[File:Accessibility-and-security.png|220px]]
 
| style="border:1px solid white; width: 300px" | [[File:Accessibility-and-security.png|220px]]
| style="border:1px solid white; width: 500px" | <font size="+1">Accessibility and security</font> <br> Your routers will not be dependent on having a public IP address for remote access, decreasing maintenance costs and increasing effectiveness. Communication between routers and main server is secured by a hardcoded OpenVPN connection, which requires no configuration and protects the communication channel from tampering.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Accessibility and security</font> <br> Your routers will not be dependent on having a public IP address for remote access, decreasing maintenance costs and increasing effectiveness. Communication between routers and main server is secured by a hardcoded OpenVPN connection, which requires no configuration and protects the communication channel from tampering.
 
|-
 
|-
 
|}
 
|}
Line 22: Line 22:  
{| class="wikitable" style="border:2px solid white; background: white"
 
{| class="wikitable" style="border:2px solid white; background: white"
 
|+
 
|+
| style="border:1px solid white; width: 500px" | <font size="+1">Maintenance and Diagnostics</font> <br> Users receive information that helps them to visualize the unit’s location and check performance indicators like temperature, signal strength and all device details. For proactive diagnostics – remotely reboot devices, download troubleshooting or system event files for in-depth health analysis.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Maintenance and Diagnostics</font> <br> Users receive information that helps them to visualize the unit’s location and check performance indicators like temperature, signal strength and all device details. For proactive diagnostics – remotely reboot devices, download troubleshooting or system event files for in-depth health analysis.
 
| style="border:1px solid white; width: 300px" | [[File:Maintenance-and-Diagnostics.png|220px]]
 
| style="border:1px solid white; width: 300px" | [[File:Maintenance-and-Diagnostics.png|220px]]
 
|-
 
|-
Line 30: Line 30:  
|+
 
|+
 
| style="border:1px solid white; width: 300px" | [[File:Statistics.png|220px]]
 
| style="border:1px solid white; width: 300px" | [[File:Statistics.png|220px]]
| style="border:1px solid white; width: 500px" | <font size="+1">Statistics</font> <br> Improve overall performance and efficiency of your whole network based on conclusions of reporting tools that allow creation of custom reports related to device availability, performance and exceptions. Actively know how your network is behaving.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Statistics</font> <br> Improve overall performance and efficiency of your whole network based on conclusions of reporting tools that allow creation of custom reports related to device availability, performance and exceptions. Actively know how your network is behaving.
 
|-
 
|-
 
|}
 
|}
Line 36: Line 36:  
{| class="wikitable" style="border:2px solid white; background: white"
 
{| class="wikitable" style="border:2px solid white; background: white"
 
|+
 
|+
| style="border:1px solid white; width: 500px" | <font size="+1">Android Application</font> <br> The best way to use RMS on your phone is by downloading the '''[https://play.google.com/store/apps/details?id=com.teltonika.rms RMS Android app]'''.
+
| style="border:1px solid white; width: 1000px" | <font size="+1">Android Application</font> <br> The best way to use RMS on your phone is by downloading the '''[https://play.google.com/store/apps/details?id=com.teltonika.rms RMS Android app]'''.
 
| style="border:1px solid white; width: 300px" | [[File:RMSphone.png|150px]]
 
| style="border:1px solid white; width: 300px" | [[File:RMSphone.png|150px]]
 
|-
 
|-
 
|}
 
|}
  −
  −
  −
  −
  −
  −
RMS phone
 

Navigation menu