.rst .pdf

On this page

Upgrade Guide with Delta Bundle

Note

• Your current release must be release 21.1 or newer prior to upgrading using the Delta Bundle.

• 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.

• Users on Azure who carry out this Delta bundle upgrade should first install the applicable patch for EKB-11598 below:

  Release 21.1: patch and the MOP are available here:

  • Server Name: https://voss.portalshape.com

  • Path: Downloads > VOSS-4-UC > 21.1 > Patches

  • Patch Directory: EKB-11598-21.1_patch

  • Patch File: EKB-11598-21.1_patch.script

  • MOP File: MOP-EKB-11598-21.1_patch.pdf

  Release 21.2: patch and the MOP are available here:

  • Server Name: https://voss.portalshape.com

  • Path: Downloads > VOSS Automate > 21.2 > Patches

  • Patch Directory: EKB-11598-21.2_patch

  • Patch File: EKB-11598-21.2_patch.script

  • MOP File: MOP-EKB-11598-21.2_patch.pdf

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.

• Using the screen command

Multinode Upgrade

• Unified Node Topology: Upgrade a Multinode Environment with the Delta Bundle
  • Download Files and Check
  • Adaptations Check
  • Schedules, Transactions and Version Check
  • Pre-Upgrade, Security and Health Steps
  • Upgrade
  • Post-Upgrade, Security and Health Steps
  • Post Template Upgrade Tasks
  • Restore Adaptations
  • Restore Schedules
  • Release Specific Updates
  • Log Files and Error Checks
• Modular Cluster Topology: Upgrade a Multinode Environment with the Delta Bundle
  • Determine the Primary database and application node in a Modular Cluster Topology
  • Download Files and Check
  • Adaptations Check
  • Schedules, Transactions and Version Check
  • Pre-Upgrade, Security and Health Steps
  • Upgrade
  • Post-Upgrade, Security and Health Steps
  • Post Template Upgrade Tasks
  • Restore Adaptations
  • Restore Schedules
  • Release Specific Updates
  • Log Files and Error Checks

Single Node Upgrade

• Upgrade a Single Node Cluster Environment with the Delta Bundle
  • Download Files and Check
  • Adaptations Check
  • Schedules, Transactions and Version Check
  • Pre-Upgrade, Security and Health Steps
  • Upgrade
  • Post-Upgrade, Security and Health Steps
  • Post Template Upgrade Tasks
  • Restore Adaptations
  • Restore Schedules
  • Release Specific Updates
  • Log Files and Error Checks

previous

Multinode Upgrade Sheet

next

Unified Node Topology: Upgrade a Multinode Environment with the Delta Bundle