Upgrade Guide with Delta Bundle
################################

.. toctree::
   :maxdepth: 1

   /src/user/src-user-install-index-upgrade-Delta-whatsnew




.. _20.1.1|EKB-3853:
.. _21.4-PB2|EKB-15903:



****************
Introduction
****************


.. toctree::
   :maxdepth: 1


Before starting with this upgrade, please read the following notes related to upgrades from 
earlier versions of the software. 

Normal operations will be interrupted during an upgrade. Perform the upgrade in a maintenance 
window. Refer to the type of upgrade for details on the upgrade duration.





.. rubric:: Upgrades to v21.4-PB1 and v21.4-PB2 - Web Portal Default Settings 

VOSS Automate offers two graphical interfaces, or web portals - ``admin`` and ``classic``. 

Your system administrator defines, via the following command, the web portal that will be the default 
for your system: ``web portal default set <admin|classic>``

Typically, the ``admin`` web portal is set as default, and the ``classic`` web portal is disabled (only ``classic`` 
can be disabled). 

These settings should be preserved post-upgrade. 

However, an issue was reported for upgrades from v21.4 to v21.4-PB1, where the web portal settings were not 
preserved post-upgrade. In this case, you would need to re-run the following commands to set 
``admin`` as default, and to disable ``classic``: 

* ``web portal default set admin``
* ``web portal disable classic`` 

This issue was fixed for upgrades to v21.4-PB2, which means that the web portal settings you have in 
earlier versions are preserved when upgrading to 21.4-PB2. 

For more information around these settings, see:  

* 

  .. raw:: html

     <a href="../platform/reference-web-portal-commands.html">Web Portal Configuration</a>.

  .. raw:: latex

     *Web Portal Configuration* in the Platform Guide



.. rubric:: Release 21.4 onwards - Product License Changes 

From release 21.4 onwards, VOSS Automate allows for the registration and update of product licenses 
within the application. A licensing service is installed during installation or upgrade and 
a license token is associated with the platform on which it is installed.



.. rubric:: Upgrades to a v2x.x Release from a v18.x or v19.x release - Impact of new *Usage* field added to Directory Numbers 

From release 21.1 onwards, a new field called **Usage** has been added to Directory Numbers (DN).

This field tracks the type of device that the DN has been assigned to. For example, for Phones, 
Device Profiles, and Remote Destination Profiles, the usage is "Device". For Hunt Groups, the usage 
is "Hunt_Pilot", and so on.

The **Usage** field is automatically populated when the DNs are assigned to and removed from 
various devices from 21.1 onwards.

In order to populate the **Usage** field once-off for all existing Directory Number inventory 
instances, the Audit Number Inventory tool (``view/NumberInventoryAudit``) should be run once 
post-upgrade for each customer.

The tool only needs to be run once when initially upgrading to a 2x.x release from a 18.x or 19.x release.

If you ran the tool already when upgrading to 21.1 for example, then it does not need to be run 
again when upgrading to later versions, for example 21.2, 21.3, 22.1, and so on.

Before running the tool:
   
* Careful consideration must taken when selecting where the Number Inventory is deployed: 
  Customer or Site - this is usually Dial Plan dependent. 
* Review the Audit Number Inventory topic in the Core Feature Guide.
   




****************
Upgrade Planning
****************


.. toctree::
   :maxdepth: 2


   /src/user/platform/reference-screen-command



*****************
Multinode Upgrade
*****************

.. toctree::
   :maxdepth: 2

   /src/user/install/multinode-upgrade-Delta
   /src/user/install/multinode-upgrade-Delta-modular

   
*******************
Single Node Upgrade
*******************

.. toctree::
   :maxdepth: 2

   /src/user/install/upgrade-standalone-Delta