Howto13r2:Firmware Upgrade V13r1 V13r2: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
Line 21: Line 21:
The Email notification is sent by the AP Manager, therefore the [[Reference13r2:Concept_App_Platform#SMTP | SMTP section of the AP manager]] should be configured.
The Email notification is sent by the AP Manager, therefore the [[Reference13r2:Concept_App_Platform#SMTP | SMTP section of the AP manager]] should be configured.


===Recording App===
===Recordings App===
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 [[Reference13r2:Concept App Recordings#Upgrade_from_V13r1_to_V13r2_Recordings_App | 13r2 Recordings App concept article]].
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 [[Reference13r2:Concept App Recordings#Upgrade_from_V13r1_to_V13r2_Recordings_App | 13r2 Recordings App concept article]].



Revision as of 17:42, 30 June 2021

Applies To

This information applies to:

  • All V13r1 capable innovaphone devices

Migration Policy

Configuration Changes

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.

Tutorials App

A Tutorial App to provide additional help to the end user. The configuration must be done according to the myApps concept article.

Push

To use the new Push Concept, simply open your Push PBX object and replace the URL with this URL: https://push.innovaphone.com/push/ws

Application Platform and its applications

AP Manager

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.

Recordings App

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.

Hardware Restrictions

For a list of devices with no/restricted support in 13r2, see the Firmware Upgrade article.

Known Problems

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 v13r2 release will consume ~ 1 MB RAM more compared to a v13r1 firmware.

Flash Memory

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 presales case with your current configuration file.

Mobility Licenses

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.

Related Articles