Howto:Firmware Upgrade V12r1 V12r2

From innovaphone-wiki

Jump to: navigation, search

Contents

Applies To

This information applies to:

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

Configuration Changes

Changed Semantics of conditional Call Forward

From the beginning, phone numbers used as a condition in an E.164 setup needed to be configured as full numbers starting from the root node. This is obviously wrong so that it has been fixed for v12r2 (see fix 13402 - PBX use adjusted number for checking numbers on call forward).

Apply updated SIP Provider Profiles

SIP provider profiles create a particular configuration once you save the it from the profile's configuration dialogue. They do not change "under the hood", even if you install a new firmware that may include updated settings. To apply such updated settings, you need to open the provider's configuration dialogue and apply it using the OK button.

The SIP profile creates also automatically routing-table entries from and to the respective SIP-interface. An update of the SIP-profile by the OK button, will therefore also recreate these routing entries. As a result, modifications (e.g. CDPN-maps) of the profile-created-routes must be redone after updating the profile. To circumvent this problem, it is recommended to not modify the routes created by the profile but create additional routes for the own modifications.

Hardware Restrictions

Following hardware is no more supported by V12r2 due to performance issues:

  • IP72
  • IP110
  • IP200A
  • IP230
  • IP240, IP240-1000M

The modernized phone models IP110A and IP240A of the above mentioned models IP110 and IP240 will support V12r2.

The following phone models will work with V12r2 but with slightly less flash memory for phone books and some less important (such as e.g. IPv6, PPP) features removed:

  • IP150

For the following hardware the PBX functionality is no more supported by V12r2 due to performance issues:

  • IP38
  • IP302
  • IP305
  • IP800
  • IP2000
  • IP6000

Software Requirements

myPBX now requires .NET 4.5.2 (v12r1 only required .NET 4).

Known Problems

Main Memory (RAM) 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 v12r2 release will consume ~ 1 MB RAM and 0.4 MB flash more compared to a v12r1 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.

Flash Memory Considerations

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 v12r2. Here is the recommended procedure for upgrade on such devices:

  • save entire configuration
  • reset to factory defaults
  • load saved configuration (this will reorganize flash memory usage)
  • upgrade to new firmware

When there is still not enough flash memory available to store the new firmware, the web GUI will issue a Firmwareupdate failed:no space during firmware upload. If the firmware upload is done using the update client, a Error 0x00130001 Major FLASHMAN0 no space event will occur.

With the new firmware, the amount of flash memory allocatable for the LDAP directory (that is, PBX config and call lists) is less than before to accommodate for the larger requirements. See http://x.x.x.x/!mod%20cmd%20FLASHMAN0%20info%20state for details (after upgrade).

Related Articles

Personal tools