Howto13r2:Firmware Upgrade V13r1 V13r2
This information applies to:
- All V13r1 capable innovaphone devices
12r2 to 13r1
13r1 to 13r2
Single AP/Single PBX
- Use update service in devices and select 13r2 as major version
Common AP/Several PBX'es
In case updating all systems at once is not desired, update jobs are splitted in the preferred order described below:
- Update the PBX'es first. Ensure the PBX'es are separated in different categories. Create dedicated update jobs for the PBX'es in those categories. Execute/Schedule PBX update jobs separated in time according to your update plan with endcustomer. After successful update of all PBX'es proceed with step 2.
- Create & execute a dedicated update job for the common AP.
- Finally update the common AP's version under AP Manager/Update (not mandatory)
Note: If Recordings is used on the common AP, update jobs can't be split over a long time. Postpone the update until further notice, see also section Recordings App or choose to update all systems at once!
When you try to upgrade from 13r1 to 13r2, you get a notification about a DNS problem. This is not a DNS problem, it's a Problem with the json update files (firmware.json, apps.json) of the store because they are too large for the 13r1 Devices App. We used the beta store to provide a minimized version of the json files that is still compatible with the 13r1 Devices App. Therefore, you need to change the URLs in the Update section of the Devices App to https://store.innovaphone.com/beta/download/firmware.json and https://store.innovaphone.com/beta/download/apps.json
In 13r2 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r2 from scratch. If you upgrade an existing installation you have to setup the configuration manual.
A Tutorial App to provide additional help to the end user. The configuration must be done according to the myApps concept article.
Via PBX Manager, AP Plugin, delete the old Push Service to services.innovaphone.com.
To use the new Push Concept, simply use the new (Black/Wite) Push PBX-Manager-Plugin and edit the existing Push-Object (set URL to
https://push.innovaphone.com/push/ws) and confirm the settings. If your PBX runs on a IPVA that has no innovaphone device certificate, you need to install an innovaphone signed device certificate.
To use the new Switchboard App see Reference13r2:Concept_App_Service_Queues and add the Queues App accordingly.
For exchanging the Operator Application to the Switchboard App, also check Reference13r2:Concept_App_Service_Queues#Additional_information regarding the licenses.
In the Configuration panel of Events App (Burger Menu top right corner) a new option "Save logs on database" is available. This is by default in v13r2 not activated, logs are only displayed in the Logging App as LiveView.
You will need to activate the option after the update, if you want to have the logs saved in the DB.
With the v13r1 logs were always by default stored in the Event App service DB, start from the v13r2 logs are by default available as LiveView mode via the Logging App. Its storage need to be activated by the administrator in the Event App settings.
To use the new e-mail notification feature, you must configure your SMTP server in the Fax PBX Manager plugin. Neither the SMTP data configured in the App manager nor in the PBX/Config/Authentication tab of the advanced UI are used for this.
Favorite Users on Home Screen
Favorite users added to the Home screen in V13r2 will update their display Name automatically. In V13r1 this was not the case as the display name was only stored when added. As a result of this, pre-V13r2 added favorite users cannot be removed from the homescreen by unticking the Home-icon in the Users-App, but must be deleted via a longpress on the favorite in the Home screen.
SNPMv1 is disabled in 13r2 per default. If you use SNMPv1, you have to explicitly enable it, after the firmware upgrade.
Application Platform and its applications
App Platform image
It is not mandatory but recommended to update the App Platform image to the latest version to receive a newer kernel and updated linux packages.
A new used disk space threshold and an email address of the responsible person that shold be notified can be configured in the Alarms and events section of the AP manager. The Email notification is sent by the AP Manager, therefore the SMTP section of the AP manager should be configured.
The Recordings App is not yet included in the 13r2 release. If a 13r1 installation using the Recordings App must be upgraded to 13r2, please follow the upgrade procedure described in the 13r2 Recordings App concept article.
Changes visible to end customers
Here are listed changes that should be communicated by resellers to the users before a 13r2 upgrade, since the change in the behavior of the application/device will be visible/hearable.
App Sharing via Video
To significantly improve the quality of Application Sharing in myApps, we are now using a high-performance video codec to transmit shared content. This will provide the user with a smooth experience in excellent quality, even for scrolling movements and animations.
The Application Sharing protocol in 13r2 uses the VP8 video codec for encoding the shared application and the RTP protocol for transmitting the encoded data.
This new implementation has still some limitations, which will be addressed in future releases:
- If application sharing is activated, it replaces the normal video stream. The speaker recognition is deactivated to keep the shared content visible. This means that during Application Sharing, no webcam video image is transmitted (neither of the speaker nor of any other participant) since both streams use the same RTP connection. If application sharing is stopped, webcam video is transmitted again.
- No possibility to provide mouse or keyboard control to remote peer.
Improved echo cancellation for telephones IP111, IP112, IP101, IP102 and myApps for Windows
Echo cancellation technique has been improved for the speakerphone mode of the VoIP telephones IP111, IP112, IP101 IP102 and for the myApps for Windows native client.
For a list of devices with no/restricted support in 13r2, see the Firmware Upgrade article.
Configuration changes after the Upgrade
After you have successfully upgraded, change the URLs back (from step Preparation) to https://store.innovaphone.com/release/download/firmware.json and https://store.innovaphone.com/release/download/apps.json.
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.
As a rough rule of thumb, a v13r2 release will consume ~ 1 MB RAM more compared to a v13r1 firmware.
As a rough rule of thumb, a v13r2 release will consume ~ 0.4 MB flash more compared to a v13r1 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 v13r2. 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 end 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.
In 13r1 and previous firmware, PBX users having a mobility device configured could fork calls (and use Mobility features) without a mobility license. This bug has been corrected in 13r2.
- Howto:Firmware Upgrade V11r2 V12r1
- Howto:Firmware Upgrade V12r1 V12r2
- Howto:Firmware Upgrade V12r2 V13r1
- Howto:V13 Firmware Upgrade V13r2 V13r3