Upgrade Guide with ISO and Template¶
Important
For VOSS-4-UC release 21.1, refer to the VOSS-4-UC 21.1 Release Changes and Impact document for details on model and workflow changes. Customizations related to these changes may be affected.
From Release 19.2.1 onwards, the minimum RAM hardware requirements for all unified nodes is 16GB.
Refer to the topic on Memory (RAM) Increase for Large End User Capacity in the Platform Guide for steps to upgrade your virtual machine.
When upgrading from any of the following versions, first obtain and apply the patch corresponding to your version from the VOSS secure FTP site:
19.1.2 -
/software/patches/19.1.2/Recommended_Patches/EKB-3853-19.1.2_patch
19.2.1 -
/software/patches/19.2.1/Recommended_Patches/EKB-3853-19.2.1_patch
19.3.1 -
/software/patches/19.3.1/Recommended_Patches/EKB-3853-19.3.1_patch
19.3.2 -
/software/patches/19.3.1/Recommended_Patches/EKB-3853-19.3.2_patch
Any customer using the Microsoft / Cisco Hybrid (Direct Routing) adaptation will not be able to upgrade to the 21.1 release. This adaptation is only supported on release 19.3.4 and has not been made compatible with some of the core functionality in the new release.
Note
Normal operations will be interrupted during an upgrade. Carry out the upgrade in a maintenance window. Refer to the type of upgrade for details on the upgrade duration.
Note
From release 21.1 onwards, a new field called Usage has been added to Directory Numbers (DN). This field tracks the type of device which 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 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 it was already run when upgrading to 21.1 for example, then it does not need to be run again when upgrading 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.
Please review the Audit Number Inventory topic in the Core Feature Guide.
Upgrade Planning¶
Multinode Upgrade¶
- Upgrade a Multinode Environment with the ISO and Template
- Download Files and Check (Prior to Maintenance Window)
- Security and Health Check Steps (Prior to Maintenance Window)
- Schedules, Transactions and Version Check (Maintenance Window)
- Pre-Upgrade Steps (Maintenance Window)
- Upgrade (Maintenance Window)
- Post-Upgrade, Security and Health Steps (Maintenance Window)
- Database Filesystem Conversion (if required, Maintenance Window)
- Database Schema Upgrade (Maintenance Window)
- Template Upgrade (Maintenance Window)
- Post Template Upgrade Tasks (Maintenance Window)
- Restore Schedules (Maintenance Window)
- Release Specific Updates (Maintenance Window)
- Log Files and Error Checks (Maintenance Window)
- Upgrading from 18.1.3 to 21.1 - summary
Standalone Upgrade¶
- Upgrade a Single Node Cluster Environment with the ISO and Template
- Download Files and Check (Prior to Maintenance Window)
- Security and Health Steps single node cluster (Prior to Maintenance Window)
- Schedules, Transactions and Version Check (Maintenance Window)
- Pre-Upgrade Steps single node cluster (Maintenance Window)
- Upgrade single node cluster (Maintenance Window)
- Post-Upgrade, Security and Health Steps single node cluster (Maintenance Window)
- Database Filesystem Conversion single node cluster (Maintenance Window, if required)
- Database Schema Upgrade single node cluster (Maintenance Window)
- Template Upgrade single node cluster (Maintenance Window)
- Post Template Upgrade Tasks single node cluster (Maintenance Window)
- Restore Schedules single node cluster (Maintenance Window)
- Release Specific Updates single node cluster (Maintenance Window)
- Log Files and Error Checks single node cluster (Maintenance Window)