Howto:Firmware Upgrade V9 V10
This information applies to:
- All PBX devices
- All DECT devices
- Linux Application Platform
Registrations with H.323 and there is no matching Device
According to Reference9:PBX/Objects, registrations must not be possible if there is no matching device entry in the object. However, up to V9 it was possible to register if the H.323 id matched with the user entry. Such registrations will not be possible with V10 any more.
LLDP is enabled by default
From version 10, LLDP is implemented and enabled by default for all the Ethernet interfaces and can be disabled. If a V9 device is connected to a switch that offers VLAN settings via LLDP, then this was ignored in V9 and will be honoured after an upgrade to V10. Unfortunately, this will change the VLAN the device uses and thus may inhibit IP access to the device after the upgrade.
You should disable LLDP before the upgrade thus. If this is not possible, you may connect to the device using the other ETH interface to disable LLDP. If this is not possible either, you need to connect the device to another switch w/o LLDP prior to the upgrade, disable LLDP after the upgrade and then put back the device to the original switch.
For some time now we do recommend to use SIP to register an XCapi client with the PBX. For more details, see Howto:XCAPI. XCapi installations which used to work with pre-V9 PBXs using H.323 may stop working with V10. Changing the registration to SIP however may fail, if the XCapi used is old. You may need to upgrade to a recent XCapi version (pls. refer to XCapi support for details, we have seen version 3.4 work fine).
Upgrading Linux Application Platform
There is no upgrade hotfix/package available, as we have upgraded to the latest Debian distribution and changed other things, which prevent an easy upgrade. So you have to set up a new Linux Application Platform V10 with Reporting V10.
To keep your configuration and data, perform the following steps:
- Save your Application Platform configuration files (see Concept Linux Application Platform)
- Save your Reporting configuration and data (see Concept Reporting)
- Save your files from your Linux Application Platform webdav folder
- Install the current Linux Application Platform V10
- Install V10 Reporting and further applications, if needed
- Restore the saved configurations and data (see Concept Linux Application Platform)
- Copy your webdav files to the new webdav folder
- Reconfigure relay hosts under Administration->Relay Hosts (formerly known as SMTP Relay)
- Perform the above steps for the standby server too
- disable replication on master and standby afterwards!
- reconfigure replication on master and standby
Upgrading from beta/rc?
Sorry, you have to perform the steps from above too! And you can't restore faxserver/exchange configuration/data files. You'll have to configure the servers again!
Mixed V9 V10 myPBX chat conversations (as may occur when a large multi-slave site is upgraded step by step) are not supported.
myPBX needs a license in v10.
Presence state "Meeting" did not work anymore when upgrading from V9 to V10.
With Version 10, we removed "Meeting" from the default set of presence activities to match myPBX.
Set of presence activities can be adjusted with
/presence-mask (see Presence Mask).
Versions / hotfixes
We strongly recommend not to omit a version during a upgrade
I.e. Don't upgrade from v7 directly to V9 or V10
Upgrade only step by step to the next versions highest hotfix.
v7 (latest hotfix) -> v8 (latest hotfix),
v8 (latest hotfix) -> v9 (latest hotfix),
v9 (latest hotfix) -> v10 (latest hotfix)
Old Phone Models
Some of the older phone models (namely IP110, IP150, IP200A, IP230 and IP240) are not capable of running the complete V10 firmware due to memory restrictions.
For above mentioned phone models, 802.1X was dropped completely in V10 (and higher).
H.323 / SIP / PPP / Video
Following features/protocols have been splitted into different named firmware versions with limited feature set to ensure further operation:
xxx stands for the phone model (110, 150, 200A, 230, 240).
* Abbreviation displayed in the General/Info screen next to the version-number
So if you do not need SIP on the phones, you can still use the normal firmware file (e.g. ip110.bin). However, if you need SIP, you need to decide on which feature to drop and use the respective firmware file variation. This may have some effect on your update scripts.
IP110, IP200A, IP230 and IP240 do not support midi-ring tones any more. RTTTL still works.
- Howto:Guideline V5 to V6 upgrade
- Howto:Upgrade Issues V5 to V6
- Howto:Firmware Upgrade V6 V7
- Howto:Firmware Upgrade V7 V8
- Howto:Firmware Upgrade V8 V9