Howto15r1:Firmware Upgrade V14r2 V15r1

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

Applies To

This information applies to:

• All 15r1 capable innovaphone devices

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

Licenses

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

If the system is licensed on premise, you'll need to regenerate the license file for V15 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

Migration Policy

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

Before you begin, be sure that your whole installation is running the latest 14r2 service release.

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.

• tbd

Manual steps needed after upgrade

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.

Techassist App

You have to enable the API "PbxSignal" in the APP Objects "App" Tab

New Apps

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

• tbd

Removed

The following software is no longer included in 15r1.

• tbd

Deprecated

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 15r1 and myApps technology.

• tbd

Previously deprecated and now no longer supported

The following software is based on legacy technology, with no further development and no more maintenance and support.
See: Howto14r2:Firmware_Upgrade_V14r1_V14r2#Deprecated_in_14r2
We strongly recommend migrating to our successor products.

• tbd

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 (tbd)

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 (tbd)

As a rough rule of thumb, a 15r1 release will consume the "tbd" amount of RAM compared to a v14r2 firmware.

Flash Memory

As a rough rule of thumb, a v15r1 release will consume ~ "tbd" flash memory compared to a v14r2 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 v15r1. 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.