Howto:Firmware Upgrade V9 V10
Applies To
This information applies to:
- All PBX devices
- All DECT devices
- Linux Application Platform
Configuration Changes
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.
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
Reporting Replication
- 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!
Known Problems
myPBX
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.
Related Articles
- 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