Guide to upgrading from pascom 17 or older to pascom 18 or newer.
Before you can upgrade, please contact our sales team in order to update your licence to pascom 18 or newer. This process is of course free of charge.
For the migration, you will also require access to my.pascom.net. Should you not yet have access to my.pascom.net, our team will of course be happy to help.
Please take the time to review the following checklist before you begin the upgrade process
Further details regarding the changes can be found in the release notes.
From pascom phone system version 18, pascom systems are based on a completely new underlying technological framework. Therefore, the upgrade cannot be performed as usual i.e. “inplace” and directly on the running server, but rather requires the following steps:
As a migration base, you will require a minimum of mobydick 7.11 (LTS). Should you have an even older system, please update to a minimum of version 7.11 (LTS).
On your existing system, now create a database backup. Login into you your pascom / mobydick server and navigate to: >> auf .
Enter an name and include any recordings, faxes and voicemails in your back up.
Click and be sure to download the generated backup to your computer.
This backup is required as a disaster recovery to restore the original solution should the upgrade not function correctly. Be sure not to skip this step!
Click >> and finally .
Click and make sure you download the newly generated backup to your computer.
As you have most likely configured the new pascom server with the same IP address you previously used, it is likely that when surfing to the IP address your are redirected to /mobydickcmd/ as this is saved within your Browser’s Cache. In this case, simply use “HTTPS” (e.g.: https://192.168.0.1) in order to access the system.
Now install the pascom phone system server version 18 or newer.
Should you by deploying a virtual phone system, to start with it is advisable to setup a new virtual machine and only shutdown the old system.
Should you use an on-premise pascom PBX, i.e. the pascom Appliance, SOHO or SMB server, please perform a new installation of the system.
To do so, please follow the instructions according to your solution as described in our Server Installation Guide.
During the installation process, the pascom setup wizard provides you with the option to register the installation via my.pascom.net and to use your newly created backup as he basis for the new installation.
The DHCP server has been moved from the pascom phone system web UI to the pascom Management UI. As such, the configuration of the DHCP server is not a component of previously imported backup.
Should you have used the pascom DHCP server in the past, you will need to activate and configure the DHCP server via the pascom Management UI. Details on how to do this can be found in the HowTo Telephone Provisioning via DHCP.
Should you use your own DHCP Server for provisioning, you will need to update the DHCP option 66 as this has changed slighty in terms of provisioning. Details on how to do this can be found in the HowTo Telephone Provisioning via DHCP.
Should you power all your hardware telephones centrally using PoE, then simply disconnecting and reconnecting your PoE switch from the network is sufficient to restart all the phones.
All hardware phones must switched from SIP-UDP and RTP to SIP-TLS and SRTP (encryption). Once you have prepared the DHCP server, you will only need to restart all the telephones. This process must be done manually as rebooting via the pascom Server without previously having performed this Provisioning switch is not possible.
Internal beroNet PCI cards can still be automatically provisioned. There is no need to copy the provisioning URL. Simply proceed as follows:
Log into the beroNet card web UI and und Management > Info that you use appfs 16 or newer. If not, update the box now:
Log into the phone system web UI. Under Gateways > Gateway list, select your beroNet Gateway and click Actions > Provisioning. The PCI cards will automatically restart and takes over the configuration of the pascom server.
As beroNet boxes can now also be used with pascom.cloud solutions, pairing using the provisioning URL is required. Simply proceed as follows:
Log into the beroNet card web UI and under Management > Info that you use appfs 16 or newer. If not, update the box now:
Log into the phone system web UI. Under Gateways > Gateway list, select your beroNet Gateway and click Actions > Provisioning URL, which you must now copy to your clipboard.
Log into thhe web UI of the beroNet box and under GUI Mode, ensure that you have selected Advanced.
Under Preferences > Provisioning, enter the following values:
|Provisioning on Boot:||always|
|Provisioning-URL||Paste the previously copied Provisioning URL|
|Polling Interval (min.)||Leave empty|
Save your changes and the beroNet box will now restart.
Should you use a pascom desktop client version older than 17.10 then you will need to manually reinstall all the desktop clients.
To do this please follow the pascom Dekstop Client Installation guide.
Why: pascom desktop client versions older than 17.10 update themselves via the pascom Server. From pascom 18 onwards, the server will no longer be responsible for client updates as this role will be performed by a specifically established, centralised pascom update service.
The pascom Server no longer supports Print-to-Fax.
In addition, using Fax-to-Mail has also changed. The pascom server now retrieves the faxes from a POP/IMAP inbox instead of receiving the E-mail directly via SMTP.
Please update your configuration accordingly.
The QueueMetrics Interface now transfers data between the pascom Server and QueueMetrics via Uniloader. Uniloader replaces the previous Qloader. The Uniloader is also able to receive commands from QueueMetrics via HTTPS and pass these commands on to the Asterisk AMI.
Further Information can be found in the Uniloader Documentation