Howto:Firmware Upgrade V10 V11r1

From innovaphone-wiki

Jump to: navigation, search

Contents

Applies To

This information applies to:

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

Migration Policy

As it may not be possible to update a complete installation in one step, we recommend to first update the endpoints (i.e. phones) to V11. Although our standard support policy requires you to run the entire installation based on the same firmware build, we support running V11 phones with the-current (that is, newest) V10 PBXs for migration purposes.

Configuration Changes

SRTP default now

In V11, SRTP is turned on by default. You only need to change the configuration if you do not want SRTP to be used. You can disable SRTP via the DHCP Server. See Reference11r1:IP4/ETH/DHCP-Server or if you use another DHCP Server Reference11r1:DHCP_client .

Default Registration Name changed

In v11, the default name used for an endpoint registration changed from something like IP222-01-02-03 to 009033010203. However, the v11 PBX is able to convert the two forms, so no configuration change should be required. Also, the latest pre-v11 v10 firmware will be able to do so, so phones should be still able to register with the v10 PBX when they are updated to v11 during migration.

Access settings (visibility) slightly changed

Evaluation of access rights has changed slightly. This only affects configurations where conflicting settings exist at template and user level.

Following the new evaluation rules:

  • Settings at the user directly or subsequent templates do have higher priority as general definitions.
  • Only similar settings will be overwritten. Example: Existing visibility setting in template for '@innovaphone.com' can only be overwritten at user level for the same named visibility '@innovaphone.com'
  • Type of visibility settings are prioritzed in following order
    • High: User
    • Medium: Groups
    • Low: Domains
  • Once a user is member of several groups, the visibility settings defined for these groups are merged (as long as there is not user defined setting)
  • Definition of group visibility just overwrites the group settings within a previously defined template.


FXS Gateways change initial port gain calibration

In V11, the FXS gateways ip22, ip24 and ip28 change their initial gain level calibration. The calibration changes vary from the gateway type as follows :

ip22, ip24

  • Receive direction changes by -1.5dB in comparison to V10 and earlier.
  • Transmit direction changes by +4.0dB in comparison to V10 and earlier.

ip28

  • Receive direction changes by -4.5dB in comparison to V10 and earlier.
  • Transmit direction changes by +6.0dB in comparison to V10 and earlier.

Hint : See Reference11:Interfaces/FXS/Physical if you are unsure which direction is supposed to be receive or transmit.

Linux Application Platform and its applications

V11 will be compatible with Linux Application Platform V10. There will be no separate V11 release for the Linux Application Platform!

Known Problems

H.323 Signalling Ports changed

In v11r1 final, H.323 uses different H.225 signalling ports (>60000). If you run a firewall with port filters you may need to allow this new range too (in previous versions, port ranges >2048 were used). This has been fixed in v11r1 sr1 (port usage is now similar to v10 again).

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 v11r1 release will consume 1MB RAM and 0.5MB flash more compared to a v10 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.

Registration of Objects by Number in Multi-Node Scenarios

V10 (and possibly even older firmware versions) did allow registration of objects by specifying the node-local number (that is, the sheer value of the Number attribute) instead of the full number including all node prefixes from the root. This has been fixed in v11r1. As a result, some configurations which used to work before will stop working. To fix this, change the number for the registration from the root-local number to the full number with all prefixes (e.g. if the object you register with lives in a node with number 9 and has the node-local number 16, then use 916 instead of 16 for the registration).

ICE

From V11r1 up, both H.323 and SIP will use ICE for media negotiation. Although ICE should be downward compatible with non-ICE-capable peers it turns out that this is sometimes not the case. In other words, some H.323 or SIP peers may show interop issues when ICE is used.

In particular, we have seen this behaviour with SIP provider connections. If you upgrade an installation with SIP trunks, you may want to test media negotiation towards the SIP trunk extensively. If you experience "no media" situations, you can try to fix them by setting the No ICE check mark in Gateway/Interfaces/SIP for the respective SIP trunk.

Addressing of Configuration File Sub-Modules for "mod cmd" changed

When you use direct "mod cmd" commands (e.g. in update scripts), you may need to change the syntax slightly. For example, instead of

mod cmd PHONE DIR local-dir add-imported "xxxxxxxxxxxx",,,"yyy"

you need to code

mod cmd PHONE/DIR local-dir add-imported "xxxxxxxxxxxx",,,"yyy"

now.

RFC-5806 deprecated

RFC-5806 was an early RFC for providing redirection information in SIP messages using a Diversion: header, which is deprecated now. Instead, redirection information is provided using the History-Info: header now.

While this should not create any interop issues, it may do so if the remote SIP peer still insists on the deprecated RFC.

A rather non-obvious situation where redirection information is used is with active recording as described in Reference11r1:Phone/User/Recording#Call_Data.

Related Articles

Personal tools