*****************************************************
* MTR-X Firmware 4.0.5 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.0.5.

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.0.5 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.0.5.

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.0.5.bin (non-LTE) or rcell-mtrv1-upgrade_4.0.5.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.0.5.

****************************************************
*    Engineering Release Notes for Customer        *
****************************************************
-----------------------------------------------------
MTR firmware 4.0.5 - February 2018
-----------------------------------------------------
Changes made since release 3.7.3:
- Support for Yocto 2.2.
- Migration of Web UI to vueJS. Look and Layout has changed.
- Added RADIUS support.
- DHCP Lease Time displays expiration date and time.
- Firewall display/layout aligns more with AEP and Linux layout.
- Implement X.509 Certificate support.
- Eliminate Default Username and Password. User prompted to set up a Username and
  secure Password upon Factory Default/Hard Reset, commissioning mode.
- Implement Buffer Size and Timeout options in Serial-IP Mode.
- The Logout option has changed to Door Exit icon.
- The browser tab name has changed to reference rCell page name instead of default
  "MultiTech rCell" name.
- The Dashboard signal strength icon was removed and replaced with dBm value.
- The signal strength icon from WiFi page was removed and replaced with dBm value.
- Reboot/Flash Upgrade progress bar was replaced with a 9 rotating square pattern.
- Changed LogIn screen to sign-in.
- Page links have removed the .html extension.
- Update GUI to read Intelligent Cellular Router.

Bug Fixes since release 3.7.3:
- Add Statistics page for OpenVPN tunnel.
- Fixed inability to modify time when using Serial Modem or PPP-IP Passthrough
  modes.
- Fixed issue where populating GPS ID Prefixes prevented GPS location.
- Implement GRE Tunnel Checking Period (minutes) for DDNS updates.
- Populated leading 0's in SMS #cellular Command, Uptime now reads 00:00:00
  not 0:0:0.
- Fix "Invalid Date" issue when viewing Remote Management with Firefox 47.
- Updated Help Content.

Known Differences since 3.7.3:
- Flashing from 3.7.3 to 4.0.5 may not require a new Username/Password but a hard
  reset of 4.0.5 will require a new Username and secure Password, called
  commissioning mode.
- Security modifications may require "sudo" usage if using SSH.
- Security modifications require a "sudo su" to log into root and adding the
  following "--unix-socket /var/run/api/http.sock" to existing curl commands.
- Although not recommended, downgrading from 4.0.5 to a previous version will
  require a hard reset back to default settings. Very important to not
  downgrade when remote to the MTR or when using DeviceHQ (Remote Management)
  because access will be lost.

Known Issues in 4.0.5:
- User must be at version 3.4.5 (or later) before upgrading to 4.0.5. Any firmware
  previous to 3.4.5 (like 3.3.2/3.4.2) must be flashed to 3.4.5 first.
- On MTR-EV3, continuous ringing of Wake On Call prevents cellular wake up.
- In Serial Modem mode, using +FTP command for files greater than 2 MB, may
  experience data loss.
- In Serial Modem mode, DCD and DSR LED's may not function properly.
- On MTR-LVW2, certain newer Verizon SIM's do not support SMS.
- On MTR-LVW2, received SMS's greater than 140 characters may be limited to 140.
- With SMS Commands, the Whitelisted numbers may need to be updated to include
  a + or full phone number because of the carrier number layout.
- Using a Saved Network with GRE/IPSec Tunnels may be lost after a flash upgrade.
- AT+WS46 reverts to default after power cycle which may affect customer that sets
  to 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.
- Certain version 1 API (/api/v1/) calls do not work.
- Connecting OpenVPN Tunnels, user is unable to open WebGUI of remote MTR.
- On the WebGUI Dashboard, the Ethernet and WiFi MAC Addresses match. This is
  only in the UI, the actual hardware has the proper MAC Addresses.

****************************************************
*      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::