Howto14r2:Firmware Upgrade V14r1 V14r2

FIXME: This article is still in progress and not finished not yet finished!

Applies To

This information applies to:

• All 14r2 capable innovaphone devices

For a general overview of the upgrade process and a list of supported devices with 14r2, see Howto:Firmware Upgrade

Licenses

In case of cloud or rental model, don't worry about licenses.

If the system is licensed on premise, and you already have V14 licenses, there is nothing to do. Otherwise, you'll need to regenerate the license file for V14 in https://portal.innovaphone.com/ and load into the system before upgrade.

Migration Policy

Here is how you upgrade a system to 14r1 from 14r2.

App Platform and Apps

14r2 Apps are no longer compatible with App Platform Images version 11xxxx or below due to a major update of the used OpenSSL library, as the old 1.1 version is deprecated.

• first update your Apps to the latest 14r1 version (this is important, don't skip this step!)
• upgrade your App Platform to version 12xxxx in the settings of your App Platform Manager
• upgrade your Apps to version 14r2 now

Note that all previous versions of Apps will still run on App Platform version 12xxxx, just 14r2 Apps require this new image version.

App Platform replication

Sadly it's not possible to upgrade the App Platform on App Platform Standbys directly due to a major version change of the PostgreSQL database. So follow these steps:

• follow the steps above to upgrade your primary server
• update the App Platform Manager and Webserver to the latest 14r1 version on each standby (this is important, don't skip this step!)
• disable replication on each standby completely
• upgrade your App Platform to version 12xxxx in the settings of your App Platform Manager on each standby
• upgrade your Apps to version 14r2 now on each standby
• activate standby replication on the standbys again now -> this will do a full replication again which might take some time

Alternativly you can install the standbys from scratch.

Changes visible to the end customers

Listed here are changes that should be communicated by resellers to end users prior to a 14r2 upgrade, as the change will be visible/audible in the behaviour of the application/device.

• myApps accessibility: Several improvements in myApps accessibility like screen reader support and keyboard control Reference14r2:Concept_myApps#Accessibility
• Connect UI: Changes and improvements in the UI of the Connect app
• Fax Cover Page: For outgoing FAX documents, a cover page with user content can be prepend

Changed Apps

If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

• Calendar App - Microsoft Office 365 Exchange. Microsoft Retirement of RBAC Application Impersonation in Exchange Online . You have to change some configurations in the PBX Manager Plugin for the Calendar App. See Howto13r2:Setting up Calendar with OAuth2
• Mail2Fax - You can now enter mail server settings in the PBX Manager plugin for the fax app, to use the Mail2Fax feature. See Reference14r2:Concept_App_Service_Fax

New Apps

New Apps will not be installed automatically by the 14r1 to 14r2 upgrade. The installation description of new 14r2 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

• Reference14r2:Concept_App_Remote_Control
• Reference14r2:Concept_App_Service_Translations

Removed in 14r2

The following software is no longer included in 14r2.

Deprecated in 14r2

The following software is based on legacy technology with no further development and limited maintenance and support. We strongly recommend migrating to our successor products that are fully compatible with 14r2 and myApps technology.

• running an AP on the CF card of an IPxx10 gateway is no longer supported, use a gateway with an SSD or a VirtualMachine to run the AP instead. The Linux/AP functionality is not yet removed from the firmware, so when migrating to 14r2, existing installations will continue to work (even if unsupported).

Known Problems

Long Update-duration

When you update, it can be up to 10 minutes before you have access to your app platform again.

Resources Considerations

New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.

Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.

RAM

As a rough rule of thumb, a 14r2 release will consume the same amount of RAM compared to a v14r1 firmware.

Flash Memory

As a rough rule of thumb, a v14r2 release will consume ~ 64KB more flash memory compared to a v14r1 firmware. New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r2. Here is the recommended procedure for upgrade on such devices:

• save entire configuration
• reset to factory defaults
• load saved configuration (this will reorganize the flash memory usage)
• upgrade to new firmware

When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a Firmwareupdate failed:no space / Update client end in a Error 0x00130001 Major FLASHMAN0 no space event) please open a support case with your current configuration file.