Commit 7876e548 authored by Etienne Allovon's avatar Etienne Allovon

Add upgrade proc from LTS to LTS

parent 201ce5af
Upgrade Five to Polaris
In this section is listed the manual steps to do when migrating from Five to Polaris.
Before Upgrade
Follow the :ref:`upgrade` page.
The *xivo-solutions-VERSION* no longer exists. The ``xivocc-installer`` package is now located in *xivo-VERSION* distribution.
You have to update your source list accordingly.
#. Remove apt source list file::
rm /etc/apt/sources.list.d/xivo-solutions.list
#. Add new source list file::
echo "deb xivo-polaris main" > /etc/apt/sources.list.d/xivo-dist.list
After Upgrade
* Accept new cel.conf: if you are asked by ``xivo-upgrade`` installer, you must choose to replace the ``cel.conf`` file or ensure
that its content correspond to these :ref:`defaults <cel>`.
* Finish to remove xivo-ctid-ng and xivo-websocketd::
apt-get purge xivo-websocketd xivo-ctid-ng
* Add `writetimeout` parameter to the the :file:`/etc/asterisk/manager.d/02-xivocc.conf` file:
.. code-block:: bash
:emphasize-lines: 7
secret = ...
deny = ...
permit = ...
read = ...
write = ...
writetimeout = 10000
* You **MUST** update:
* *Snom* phones to use plugin version **>=2.2** to be able to use CTI Transfer (UC Assistant or CCAgent),
* *Yealink* phones to use plugin with **v81** firmware to be able to use CTI Transfer (UC Assistant or CCAgent).
* The WebRTC call limit was raised to 2 (to enable transfers). The simultcalls parameter of a WebRTC user should be set to 2 also.
* Update new fingerboard::
xivocc-dcomp stop fingerboard
docker rm xivocc_fingerboard_1
xivocc-dcomp up -d
* SpagoBI:
* **Import new reports** as described in :ref:`spagobi` post install step
* Then, you should also remove old sample reports:
* Go to `Reports` menu and delete all reports which are located under **Racine -> Sample**
* Once all reports are deleted inside these folder you can go to `Functionalities Management` menu as shown in following
.. figure:: reportsdelete1.png
:scale: 100%
* From here, you can delete empty folders by clicking on it
.. figure:: reportsdelete2.png
:scale: 100%
* At the end you should have a report folder list, that contains only `Rapports` and `Accueil` folder as seen here (unless
you have some specific customer report):
.. figure:: reportslist.png
:scale: 100%
Upgrade Polaris to Aldebaran
In this section is listed the manual steps to do when migrating from Polaris to Aldebaran.
Before Upgrade
* If docker is installed (on XiVO PBX or XiVO CC), its custom start options may cause the upgrade to fail. Please check that ``/etc/systemd/system/docker.service.d``
directory does not exist or it is empty. Otherwise see documentation on `docker web <>`_.
* XiVO Aldebaran is only available in **64-bit** versions. To migrate XiVO from ``i386`` to ``amd64``, you must follow :ref:`migrate_i386_to_amd64`.
* Configuration files and dialplan subroutine for ACD outgoing calls for call blending
(See `Polaris documentation <>`_)
was integrated to XiVO.
The configuration **must** be manually removed if it exists::
sed -i '/' /etc/asterisk/queueskills.conf
rm /usr/local/sbin/
rm /etc/asterisk/extensions_extra.d/xuc_outcall_acd.conf
* If the XiVO was added to XiVO Centralized User Management, the file ``routage.conf`` **must** be updated.
* Download the new `routage.conf <>`_ file
* Replace the old file ``/etc/asterisk/extensions_extra.d/routage.conf`` by the new one
* Follow the :ref:`upgrade` page.
* Update distribution to xivo-aldebaran in source list::
echo "deb xivo-aldebaran main" > /etc/apt/sources.list.d/xivo-dist.list
After Upgrade
* Outgoing call was removed from redirections.
You MUST check the xivo-upgrade log with the following command::
zgrep MIGRATE_OUTCALL_FWD /var/log/xivo-upgrade.log*
Then you MUST edit each object to reconfigure the changed destination.
All Outgoing call redirections can be replaced by an Extension redirection with the appropriate context.
For example an outgoing redirection towards "my_outcall (@to-extern)" to number "0123456789"
can be replaced by an extension redirection to "0123456789" with context "to-extern"
* ConfigMgt service was moved to XiVO PBX. Here's how to migrate the ConfigMgt database:
* On your **XiVO CC** (where the service pgxivocc is run) authorize user root to login with password via ssh,
* Then on your **XiVO CC**, stop the services with ``xivocc-dcomp stop``
* Then, on your **XiVO PBX**, run the migration script and follow the instruction::
* Finally, when migration is complete, relaunch the services on **XiVO CC**::
xivocc-dcomp up -d --remove-orphans
* Update new kibana default panels::
xivocc-dcomp stop kibana_volumes
docker rm -v xivocc_kibana_volumes_1
xivocc-dcomp up -d
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment