*****************************************************
* MTR-X Firmware 4.1.0 Release Notes                *
*****************************************************
Contents:
1) Models Covered By This Firmware.
2) Firmware Upgrade Procedure.
3) Engineering Release Notes for Customer.
4) Support Information.

****************************************************
*    Models Covered By This Firmware               *
****************************************************
- MTR-EV3-x
- MTR-H5-x
- MTR-H6-x
- MTR-LAT1-x
- MTR-LEU1-x
- MTR-LVW2-x

Not tested due to 2G Sunset:
- MTR-C2-x
- MTR-G3-x

****************************************************
*    Firmware Upgrade Procedure                    *
****************************************************
Upgrading to 4.1.0.

Note: Backup your configuration before performing this upgrade. If the firmware
upgrade fails, or it does not show the login page again, wait an additional 5
minutes. Power off and on the MTR and web to the MTR to check the version. If
the version does not show the latest, then the upgrade was not successful. Try
to perform the firmware upgrade again by repeating all the steps.

NOTE:
To upgrade using the MTR Web UI to MTR 4.1.0 you must be running at least MTR 3.4.5
firmware.
To upgrade from a previous firmware, upgrading to MTR 3.4.5 is necessary before
upgrading to MTR 4.1.0.

1) Save the firmware binary file to a directory on your workstation.
2) Using the workstation browser, enter the IP address of the MTR
   (i.e. http://192.168.2.1).
3) Login as admin and enter the admin password.
4) Click "Administration" tab on left side menu bar.
5) Click "Save/Restore".
6) Click "Save Configuration to File" to save a backup file. A popup window will
   appear.
7) Select "Save File" and click "OK" button.
8) Now click "Firmware Upgrade" tab on left side menu.
9) Click the Browse button and select the latest version of BIN file,
   rcell-mtr-upgrade_4.1.0.bin (non-LTE) or rcell-mtrv1-upgrade_4.1.0.bin (LTE).
10) Click the "Start Upgrade" button. Confirm the 5 minute "OK" button.
11) Wait for the unit to upgrade and reboot automatically.
12) Again, browse to the IP address and verify the Main or Home Page indicates the
    correct version, 4.1.0.

****************************************************
*    Engineering Release Notes for Customer        *
****************************************************
-----------------------------------------------------
MTR firmware 4.1.0 - September 2018
-----------------------------------------------------
Changes made since release 4.0.5:
- New Feature: Support for uploading CA Certificates.
- Add 24 bit (/24 mask) support in PPP-IP-Passthrough to support more than one
  client device.
- IPSec: add certificate-based authentication support.
- Updated supported ciphers in multiple features (SSH, HTTPS, Serial-IP,
  Bluetooth-IP, Mobdbus Gateway, OpenVPN, etc...).
- New Feature: Trusted IP.
- Beta Feature: Self-Diagnostics (Flash Memory Checksum, MAC – Mandatory Access
  Control, Resource Usage, Notifications based on events from these Diagnostic
  functions).
- New Feature: Signed Firmware support.
- SNMPv3 advanced security settings enhancements and support for multiple trap
  destinations. Extended SNMP read parameters.
- Usage Policy implementation in the Web UI.
- New Feature: display Notifications sent via Email, SMS, or SNMP.
- RADIUS – Message-Authenticator Attribute was added to all PAP requests.

Bug Fixes since release 4.0.5:
- Fix: GPS Map is not displayed when all GPS data is retrieved.
- Fix: SMS Command #cellular eliminating Uptime leading 0's.
- Fix: IPSec Tunnel does not work with SHA2-384 settings
- Fix: Upgrading from 3.7.3 to 4.0.5 had the following IPSec-related issue: "ALL
  AES" option cannot be applied in the IPSec configuration, Data Loss happens when
  upgrading from MTR 3.7.3 to 4.0.5.
- Fix: Information messages are not displayed during firmware upgrade process if
  the firmware process was initiated from DeviceHQ.
- Fix: Wi-Fi as WAN: IP address is not changed when switching between WiFi Networks.
- Fix: Device position on GPS page map no longer depends on NMEA configuration.
- Fix: Remote Network Route is not displayed properly on GRE Tunnels.
- Fix: Generate Certificate: The City value was lost and set to empty when generating
  a new Web server certificate.

Known Differences since 4.0.5:
- On WiFi models, the Dashboard WiFi MAC address now matches the WiFi hardware instead
  of matching the Ethernet MAC Address. This was improper reporting on the Dashboard
  only, the WiFi hardware was correct.
- The Dashboard Signal switched from a –dBm value back to a Bar graph. A hover over the
  icon will display the –dBm value.
- If modifying the Signed Firmware Validation checkbox, the Save and Restart takes a
  few seconds to illuminate. A Save and Restart is still required.
- Occasionally, the Dashboard Signal bars go all gray with a value of -65 dBm when the
  rCell still has signal. This is a Dashboard reporting problem and may not be related
  to a Cellular connection issue.

Known Issues in 4.1.0:
- User must be at version 3.4.5 (or later) before upgrading to 4.1.0.
- Although not recommended, downgrading from 4.1.0 to a previous version will require
  a hard reset back to default settings.
- A Hard Reset (or Factory Default) will force 4.1.0.firmware into Commissioning Mode
  to create a new Administrative Username and Password.
- Serial Modem Mode:
    In Serial Modem Mode, there is a known issue with data loss when using the AT+FTP
    command for large files greater than 2 MB.
    In Serial Modem Mode, the DCD and DSR LED’s do not work properly. The CD LED may
    not reflect the DCD correctly.
- On MTR-EV3, continuous ringing of Wake On Call prevents cellular wake up.
- On MTR-LVW2, certain newer Verizon SIM’s do not support SMS.
- On MTR-LVW2, received SMS’s greater than 140 characters may be truncated to 140.
- Command AT+WS46 reverts to default after a power cycle which may affect a user that
  sets a non-default value.
- Adding SNMP IP Address requires a Save and Restart but does not illuminate.
- SMS Command API ignores 6 character password limit, does not fail if SMS is
  longer than 160 characters, has issues depending on location of spaces and can
  not view view/delete inbox/outbox.
- Nofications API can delete existing alerts, add new alerts, modify with
  non-existing group, add two groups with same name and generate email with
  bad characters.
- DHCP API can set invalid Gateway.
- With SMS Commands, the Whitelisted numbers may need to be updated to include a + or
  full phone number because of the International Number fix.
- Certain version 1 API (/api/v1) calls do not work.
- Connecting OpenVPN Tunnels, user is unable to open WebUI of remote MTR.

****************************************************
*      Support Information                         *
****************************************************
Multi-Tech provides free technical support for your product. To obtain this
support, we suggest you create a support case on our Support Portal at:
https://support.multitech.com

If internet is not available, try one of our numbers:
U.S. & Canada number: 763-717-5863
Answered Monday - Friday
8:00 am to 5:00 pm Central Time (Daylight savings observed when in effect)

International number: +763-717-5863
Answered Monday - Friday
8:00 am to 5:00 pm Central Time (Daylight savings observed when in effect)

EMEA    support@multitech.co.uk         +(44) 118 959 7774
U.S.    support@multitech.com           800-972-2439 or
(and Rest of World)                     +763-717-5863

Replacement Parts and Accessories
For replacement parts and accessories, contact Multi-Tech at:
(888) 288-5470, option 3 or +1 (763) 785-3500

US Mail Address:
  Multi-Tech Systems, Inc.
  2205 Woodale Drive
  Mounds View, MN 55112
  USA

::Form Version R2014-03-27::