Upgrade Guide with ISO and Template#
Introduction#
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.
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.
Upgrades from 19.X or earlier - Model and Workflow Changes
When upgrading from 19.X or earlier, 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.
Release 19.2.1 onwards - Minimum Hardware Requirements
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.
Patches Required for Upgrades from v19.1.2, v19.2.1, v19.3.1, v19.3.2
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
From Downloads > VOSS-4-UC on voss.portalshape.com:
19.3.1 > Patches > EKB-3853-19.3.1_patch
19.3.2 > Patches > EKB-3853-19.3.2_patch
Microsoft/Cisco Hybrid Adaptation not Supported for Upgrades to v21.2
Customers using the Microsoft/Cisco Hybrid (Direct Routing) adaptation will not be able to upgrade to the 21.2 release. This adaptation is only supported on release 19.3.4 and has not been made compatible with some of the core functionality in release 21.2.
Customers using this adaptation and wish to upgrade to release 21.3 should first contact VOSS Global Services.
Upgrading From v19.3.x with FIPS Enabled
If you have FIPS enabled on your system, then before continuing with the upgrade, see:
Upgrading from Release 19.3.x with FIPS enabled.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#
Multinode Upgrade#
- Unified Node Topology: 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)
- Licensing (outside, after Maintenance Window)
- Upgrading from 18.1.3 to Current Release - Summary
- Modular Cluster Topology: 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 and Health Steps (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)
- Licensing (outside, after Maintenance Window)
Single Node 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)
- Licensing (outside, after Maintenance Window)