Howto:Firmware Upgrade V11r2 V12r1

From innovaphone wiki
Jump to navigation Jump to search

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

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 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.

Flash Memory Considerations

New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, the IP800/IP22/IP24/IP38/IP302/IP305 as well as the older IP110, IP200, IP230 and IP240 phones may run out of flash memory during upgrade to v12r1. 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, local phone book and call lists) is less than before to accommodate for the larger requirements. It is reduced from 3200kB to 2816kB on the IP800, from 3200kB to 2560kB on the IP22/IP24/IP38/IP302/IP305 and from 768kB to 496kB on the phones.

No /DRIVE/CX0 any more

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

SIP digest authentication

We have implemented the security feature SIP digest authentication . If the client did not support this feature the PBX will reject the registration. There is a config option to avoid this. But it is not recommended to disable this feature. It's a security feature.

http://ip-of-pbx/!config change SIP /disable-digest-replay-check 
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate

You get a hint with the SIP/2.0 401 Unauthorized message (wireshark pcap)

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.88.142:5060;branch=z9hG4bK5d7b5284edaa9bed3e3a323dc78f4022;rport=5060;received=192.168.88.142
From: <sip:111@192.168.88.134>;tag=2469966351
To: <sip:111@192.168.88.134>;tag=1151509663
Call-ID: 3129114392@192_168_88_142
CSeq: 1903 REGISTER
Content-Length: 0
Date: Fri, 06 May 2016 13:54:31 GMT
Warning: Digest replay attack detected
WWW-Authenticate: Digest realm="192.168.88.134",nonce="859b13f3852c5701116600903340032b",qop="auth",algorithm=MD5

Related Articles