Howto:Firmware Upgrade V11r2 V12r1: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
Line 27: Line 27:
==Known Problems==
==Known Problems==
=== Memory Considerations ===
=== Memory 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.  As a rough rule of thumb, a v11r2 release will consume 1.2MB RAM and 0.6MB flash more compared to a v10 firmware.
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.  As a rough rule of thumb, a v12r1 release will consume 1.5MB RAM and 0.8MB flash more compared to a v11r2 firmware.


Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Recommended__number_of_users_supported | to spec ]] 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]].
Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Recommended__number_of_users_supported | to spec ]] 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]].

Revision as of 19:11, 9 March 2016

Applies To

This information applies to:

  • All PBX devices
  • All DECT devices
  • Linux Application Platform

Migration Policy

Configuration Changes

Automatic Media Relay

<internal>http://inno-social.innovaphone.com/microblog/global/portal/topics/12r1/notes/45172</internal>


Linux Application Platform and its applications

xx11/11xx gateways can host a LinuxPlatform as well. First LinuxImage which as well fits for the new hardware types is V10sr32 (Build 100210). This build contains TWO linux images labeled

  • Image-6010-3.4.10 - for old hardware types
  • Image-IPx11-4.4.0 - for new hardware types (xx11/11xx)

Pay attention to the definition of used "Linux Kernel file" at Linux/General - especially when moving configuration files from "old" to "new" hardware types.

Please note that there is no v12 version of the linux application platform, so you still will be using Linux Application Platform V10.00!

Known Problems

Memory 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. As a rough rule of thumb, a v12r1 release will consume 1.5MB RAM and 0.8MB flash more compared to a v11r2 firmware.

Standard configurations which are according to spec 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.

Special care has to be taken for old devices with less memory than suggested by current specs. Most notably, these are the older IP30x models (hardware build 306 or less, which had 16MB RAM as opposed to 32MB in the current models). We do not recommend to upgrade such old hardware to a current firmware version unless it has been determined that the configuration in question will work.

No /DRIVE/CX0 any more

The /DRIVE/CX0 announcement file encoder has been removed. Use the web based converter instead.

Related Articles