Howto14r2:Firmware Upgrade V14r1 V14r2

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 from 14r1 to 14r2.

Before you begin, be sure that your whole installation is running the latest 14r1 service release. If you are still running 13r3 or earlier, be sure to update to 14r1 latest service release before.

IPVA - Flash preparations

Due to an internal change in the flash segment allocation in the IPVA environment, you may have to prepare your system for the upgrade.
Please execute the command !mod cmd FLASHMAN0 info on all your IPVAs before the update. You must check whether all flash segments are allocated in your current installation.

In this example, you can see that 228 segments are used by the LDAP (marked in green), and a total of 228 segments are available (marked in yellow). If the difference between these two numbers is less than 10, you must perform the following steps before the upgrade:

Download the configuration (NOT "with standard password") from the IPVA
Upload the configuration to the IPVA
Reboot the IPVA

segments=249, segment-size=0x10000 (64k)
LDAP - used 47k avail 43k owned 14592k (segments 228) maximum 14592k (segments 228, configured 228)
VARS - used 51k avail 8k owned 1280k (segments 20) maximum 1280k (segments 20, configured 20)

After execute the above command again, you will see the following. The segments used by the LDAP (marked in green) changed.

segments=249, segment-size=0x10000 (64k)
LDAP - used 47k avail 61k owned 128k (segments 2) maximum 14592k (segments 228, configured 228)
VARS - used 24k avail 21k owned 1280k (segments 20) maximum 1280k (segments 20, configured 20)

If the difference between these two numbers is now greater than 10, you can go ahead with your upgrade. Otherwise, please open a support case.

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.

upgrade your App Platform to version 12xxxx in the settings of your App Platform Manager via the Update option (open the AP Manager, Burger menu, Settings, update -> update to 12xxxx) and then carry out the restart offered in the update procedure
verify that the App Platform is rebooted by checking the version using the "burger menu / Settings / Update" in the 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:

disable replication on each standby App Platform
shutdown each standby App Platform
proceed with the regular update on your infrastructure for all other devices
verify proper function of your system
startup each standby App Platform
follow the above steps to upgrade each standby App Platform
activate standby replication on the standbys App Platforms again now (this will do a full replication again which might take some time)

Alternatively 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

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.

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

Connect App / Search App

In order for the Search App to find Connect posts, you need to make sure to change the following things:

PBX Manager plugin "AP messages" - "Api" - Make sure to enable "Config User" for the Messages API Object. (Not Administrators or Moderators)
For the "Connect" PBX-Object
- In the "App"-Tab enable "PbxApi" (additionally to "Websocket" and "PbxSignal")
- In the "Apps"-Tab enable "messages-api"

Contacts App

You have to enable the checkmark "Websocket" in the App Object. Otherwise you will not have new "Add Contacts" functions inside the PhoneApps

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

WorkingManager

You need to add the string "hr" to the "Modes" field in the WorkingManager app object to create a special app that can be assigned to a user that grants all rights. Otherwise, users to whom the WorkingManager is assigned will only have the assigned group permissions. See https://wiki.innovaphone.com/index.php?title=Reference14r2:Concept_App_Service_Working#innovaphone-working-admin

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.

Removed

The following software is no longer included in 14r2.

Nothing

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 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 Virtual Machine 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).
iQM (innovaphone Queue Monitor) is deprecated, and we recommend migrating to the Queueboard App.

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: Howto14r1:Firmware_Upgrade_V13r3_V14r1#Deprecated_in_14r1
We strongly recommend migrating to our successor products.

Linux Application Platform (v10)

Please migrate to the innovaphone App Platform.

innovaphone Faxserver (v10)

Please migrate to the Fax App.

innovaphone Reporting (v10)

Please migrate to the Reports App.

innovaphone Exchange (v10)

Please migrate to the Calendar App.

Operator (v9)

Please migrate to the Switchboard App.

innovaphone Voice Recording 2014

Please migrate to the Recordings App.

PBX Object External UC

Existing configurations still work. But new configurations can't be done using the advanced UI anymore.

Please use the integrated UC and federation features of the innovaphone PBX.

For presence synchronization with other systems we recommend using

innovaphone myApps Connector for Microsoft 365
Connector for kuando®
Calendar App

Known Problems

Long Update-duration

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

Downgrade on IPVA with large configuration

The number of 64kB memory segments that an IPVA uses internally to store "VARS" has been increased from 10 to 20. This is only an internal adjustment and does not require any adjustment to the virtual machine.

After an upgrade to v14r2 a downgrade is possible as long as the total space used by VARS is less than 540 kB, i.e. mod cmd FLASHMAN0 info -> VARS - used=nk (n <= 540)

Because VARS data may be scattered over all assigned segments, the downgrade procedure must be:

"config download" to gather the potentially scattered VARS
downgrade
"config upload" to restore the VARS as densely packed

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.