695
edits
Changes
RMS Product Change Notifications (view source)
Revision as of 13:00, 11 April 2023
, 13:00, 11 April 2023no edit summary
__TOC__
__TOC__
==2023.04.04 Changes to adding RMS devices==
On April 18th, 2023 Teltonika's '''[[RMS|Remote Management System]]''' ('''[[RMS]]''') will receive an update that will change how Teltonika devices connect to RMS.
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Devices now have to reach an additional port to connect to RMS.<br>
|-
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 908px; text-align: left; background: white;" |Devices will additionally need to reach a new port for the device to successfully connect to the RMS platform. This port will be necessary every time the device attempts to connect to the RMS, e.g. after a reboot, a connection disruption, or any other reason why the device disconnected from the platform.
Before the update, for the device to successfully connect to the RMS, it had to reach the IP address '''18.196.62.30''' and ports:
* 15009
* 15010
After the update - the same address '''18.196.62.30''' and ports:
* 15009
* 15010
* '''15011 (new)'''
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
RMS security improvements
|-
| style="text-align: left; background: white;" |Change implementation date
| colspan="2" style="text-align: left; background: white;" |April 18th, 2023
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |This update will make it easier and more convenient to add devices to the RMS platform.
|-
|-
| style="width: 221px; text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="width: 908px; text-align: left; background: white;" |Please contact your sales representative concerning any issues in regard to these changes.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
|-
|}
==2023.03.20 Changes to adding RMS devices==
==2023.03.20 Changes to adding RMS devices==
|-
|-
| style="text-align: left; background: white;" |Change type
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Changes to how devices are validated in the platform the first time they connect to an RMS Company.<br>
| colspan="2" style="text-align: left; background: white;" |Changes to how devices are validated in the platform the first time they connect to an RMS Company.<br>
|-
|-
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 221px; text-align: left; background: white;" |Detailed description
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
| colspan="3" style="text-align: left; background: white;" | If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
|-
|-
|}
|}
{| class="wikitable"
{| class="wikitable"
|+
|+
! colspan="3" style="text-align: left; background: white;" |Change description
! colspan="3" style="text-align: left; background: white;" | Change description
|-
|-
| style="text-align: left; background: white;" |Change type
| style="text-align: left; background: white;" |Change type
4. Devices will not be able to be added to RMS via Android and iOS applications. '''Important''': The ability to add devices via Android and iOS applications will be reintroduced with future application updates.
4. Devices will not be able to be added to RMS via Android and iOS applications. '''Important''': The ability to add devices via Android and iOS applications will be reintroduced with future application updates.
|-
|-
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 221px; text-align: left; background: white;" | Detailed description
| style="width: 908px; text-align: left; background: white;" |
| style="width: 908px; text-align: left; background: white;" |
'''Summary''':<br>
'''Summary''':<br>
* Teltonika device must have a "First login" done, i.e. a WebUI login and password change must have been made.<br>
*Teltonika device must have a "First login" done, i.e. a WebUI login and password change must have been made.<br>
* RMS will ask for the device's password before the device can be added.
*RMS will ask for the device's password before the device can be added.
-----
-----
'''Extended description''':<br><br>
'''Extended description''':<br><br>
'''2.1. Adding singular devices via RMS UI'''<br>
'''2.1. Adding singular devices via RMS UI'''<br>
'''Today:'''<br>
'''Today:'''<br>
* For RUT/TCR devices - You must input the [Serial number] and [MAC address].
*For RUT/TCR devices - You must input the [Serial number] and [MAC address].
* For TRB devices - You must input the [Serial number] and [IMEI].
*For TRB devices - You must input the [Serial number] and [IMEI].
'''After these changes:'''<br>
'''After these changes:'''<br>
* For RUT/TCR devices - You must input the [Serial number], [MAC address] and the '''[Device's current password]''' (of the "admin" user)
*For RUT/TCR devices - You must input the [Serial number], [MAC address] and the '''[Device's current password]''' (of the "admin" user)
* For TRB devices - You must input the [Serial number], [IMEI], and the '''[Device's current password]''' (of the "admin" user).<br><br>
*For TRB devices - You must input the [Serial number], [IMEI], and the '''[Device's current password]''' (of the "admin" user).<br><br>
'''2.2. Adding devices via CSV file'''<br>
'''2.2. Adding devices via CSV file'''<br>
In order to add a device to RMS using a CSV file, the file must contain the following columns of information:<br>
In order to add a device to RMS using a CSV file, the file must contain the following columns of information:<br>
'''Today:'''<br>
'''Today:'''<br>
* Serial number
*Serial number
* MAC address (or IMEI when adding TRB devices)
*MAC address (or IMEI when adding TRB devices)
* Name (optional)
*Name (optional)
'''After these changes:'''<br>
'''After these changes:'''<br>
* Serial number
*Serial number
* MAC address (or IMEI when adding TRB devices)
*MAC address (or IMEI when adding TRB devices)
* '''Password'''
*'''Password'''
* Name (optional)
*Name (optional)
----
----
3. Adding a device through the RMS API will require additional information in the request body of the API call. <br>
3. Adding a device through the RMS API will require additional information in the request body of the API call. <br>
| colspan="2" style="text-align: left; background: white;" |1. WebUI and CLI access functionality, additional IP and Ports.<br>2. RMS Proxy (access to HTTP(s) devices behind the router) will be moved to the RMS Connect section.<br>
| colspan="2" style="text-align: left; background: white;" |1. WebUI and CLI access functionality, additional IP and Ports.<br>2. RMS Proxy (access to HTTP(s) devices behind the router) will be moved to the RMS Connect section.<br>
|-
|-
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 221px; text-align: left; background: white;" | Detailed description
| style="width: 908px; text-align: left; background: white;" |1. In order to continue using WebUI access and CLI access functionality the following IP address and ports must be made accessible for the router:<br>IP: 18.192.27.240<br>Ports: 20022, 20080, 23389.<br>If you are using a Private network, these must be whitelisted by the Internet Service Provider.<br>This change comes in order to greatly enhance and speed up the functionality by utilizing reverse SSH tunneling.<br>2. RMS Proxy functionality becomes a part of the RMS Connect package, which allows RDP, VNC or SSH access to devices behind routers via RMS. It will be monetized based on traffic usage.
| style="width: 908px; text-align: left; background: white;" |1. In order to continue using WebUI access and CLI access functionality the following IP address and ports must be made accessible for the router:<br>IP: 18.192.27.240<br>Ports: 20022, 20080, 23389.<br>If you are using a Private network, these must be whitelisted by the Internet Service Provider.<br>This change comes in order to greatly enhance and speed up the functionality by utilizing reverse SSH tunneling.<br>2. RMS Proxy functionality becomes a part of the RMS Connect package, which allows RDP, VNC or SSH access to devices behind routers via RMS. It will be monetized based on traffic usage.
|-
|-
|-
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change. We recommend to change any services using previous DNS address ('''rms.teltonika.lt''') to the new DNS address ('''rms.teltonika-networks.com''').
| colspan="2" style="width: 908px; text-align: left; background: white;" | No risk factors encountered with this change. We recommend to change any services using previous DNS address ('''rms.teltonika.lt''') to the new DNS address ('''rms.teltonika-networks.com''').
|-
|-
|}
|}
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
| colspan="3" style="text-align: left; background: white;" | If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
|-
|-
|}
|}
! colspan="2" style="width: 1154px; text-align: left; background: white;" |Affected products information
! colspan="2" style="width: 1154px; text-align: left; background: white;" |Affected products information
|-
|-
| colspan="2" style="text-align: left; background: white;" |All licenses will be activated for a 30 day period starting from August, 2019 with the exception of already active ones.
| colspan="2" style="text-align: left; background: white;" | All licenses will be activated for a 30 day period starting from August, 2019 with the exception of already active ones.
|-
|-
| style="width: 221px; text-align: left; background: white;" |Change implementation date
| style="width: 221px; text-align: left; background: white;" |Change implementation date
{| class="wikitable"
{| class="wikitable"
|+
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
! colspan="3" style="text-align: left; background: white;" | Change impact
|-
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| style="width: 221px; text-align: left; background: white;" |Risk assessment