Vocera Communications System Release Notes

Vocera Voice Server Version 5.9.0.123

Release Date: April 2023

Updated: May 2, 2023

  1. New and Enhanced Features
  2. Prerequisites and Reminders
  3. Installation
  4. Fixed Issues
  5. Known Issues

New and Enhanced Features

The Vocera Voice Server 5.9.x platform has new features and enhancements.

This section summarizes prominent features and functionality for each release.

New and Enhanced Features in 5.9.0.123

The following list displays new features in this version of the Vocera Voice Server.

Vocera Voice User Interface

Vocera Voice Server

Third-party Software Versions

The following third-party software versions are included in this release and provide 64-bit compatibility or security enhancements:

3rd-party Software Version
Apache HTTP Server 2.4.54
Apache Tomcat 9.0.70
JRE (Zulu built on OpenJDK) 1.8.0_352-b08 (Zulu 8.66.0.15)
MySQL Server 8.0.31(VS)/5.7.39 (VRS)
ODBC Connector Not installed; used at install-time only
TLS 1.3 and 1.2
PJSIP 2.9

Vocera Firmware Versions

The following firmware versions are included in this release:

Vocera Device Firmware Build Number
B3000 3.1.3.13
B3000n 4.3.4.12
C1000 1.5.0.115
V5000 5.0.8.12

Prerequisites and Reminders

Before you install Vocera Voice Server along with its components and consoles, ensure that the following prerequisites are met.

Prerequisites for Vocera Voice Server and server components:

Installation

Follow these instructions to install Vocera Voice Server or upgrade it to the latest version. .

Installation prerequisites

To install or upgrade:

Note: While installing or uninstalling, you can be repeatedly presented with pop-up messages instructing you to reboot for changes to be applied. Do not reboot when prompted. Wait until the installation is complete to reboot.
  1. To perform a new installation, follow the steps described in the Running theVocera Voice Server Installation Program section of the Vocera Voice Server Installation Guide.
  2. To upgrade from previous Vocera versions, follow the steps described in Upgrading Vocera Voice Server to Version 5.6.0 section of the Vocera Voice Server Installation Guide.
    Note: Your previous system configuration remains in the database that is restored at the end of the upgrade. Because some 4.x features have been deprecated.
    • Update the values in your database as follows:
      1. Open the Vocera Voice Server Administration Console and navigate to the System > Preferences page.
      2. Choose Save Changes.

        The server updates your database and removes any settings for deprecated features.

    • Convert custom names directory:
      • If you are upgrading from a version 4.x deployment and have a custom names dictionary, convert the custom names directory to the version 5.x format manually.
      • If you are upgrading from version 5.x and have a custom names dictionary, no conversion is required.

Fixed Issues

The following list contains fixes and improvements made to the Vocera Voice Server 5.9.x platform.

Fixed Issues in Version 5.9.0.123

The following list includes items fixed or improved in this version of the Vocera Voice Server.

  • VCXP-16615 An issue causing the delayed removal of obsolete dynamic grammar files can cause a performance issue when a large number of old grammar files are removed at the same time. This logic is now optimized to remove old files more regularly.
  • CRVC-22909 The Voice Server can crash if a VCS client changes IP addresses in the middle of a call. This condition is now properly handled.
  • CRVC-23160 If the active cluster node fails during a remote restore, the remaining server can under certain conditions become active with an empty database.
  • CRVC-23484 Multiple parties transferring the same conference call on VCS clients can result in a server crash.
  • CRVC-23491 A device going off network during certain call transitions can result in a crash.
  • CRVC-23575 A system crash can result from a user’s device going off-network while that user’s call is being transferred. The call is now properly ended.
  • CRVC-23742 After recovery of a temporary cluster split-brain condition, users who have logged in to a new device may cause a crash when the system doesn’t properly track the active device.
  • CRVC-23836 After upgrading from VS 5.4 to VS 5.8, login attempt with incorrect password causes the Voice Server to failover.
  • CRVC-23906 In certain rare cases, configuration changes such as deleting a site can conflict with ongoing badge activity resulting in a server crash. This situation is now properly handled.
  • CRVC-23923 In certain cases involving dual mode with VCS and Smartbadge the Smartbadge login can fail and leave the system in a state where alerts are not being delivered properly to VCS. This situation is now properly handled.
  • CRVC-24105 System performance can be degraded resulting in the Voice Server timing out and shutting down in cases where groups are configured with a very large number of nested sub-groups. This behavior is now optimized to avoid the extreme performance impact.
  • CRVC-24152 The Everyone group can be accidentally deleted from the Admin console resulting in the Voice Server shutting down. Deletion of the Everyone group is now prevented.
  • CRVC-24302 A memory leak in the RSIP server can result in degraded performance requiring a restart of the services to recover.
  • CRVC-24379 In some situations, the B3000n badge does not display the sender information when a message is initiated from VMP.
  • CRVC-24461 An error processing invalid call data can result in a VCG crash. The invalid data is now properly handled.
  • CRVC-24576 After upgrading to VRS 5.8 HF2, the scheduled dataload task may sporadically fail.

Known Issues

A few issues are known to exist in the Vocera Voice Server 5.9.x platform and this section summarizes all the known issues in the release.

Known Issues in the Vocera Voice Server

This section summarizes known product defects and limitations, including any workarounds we may have, for the Vocera Voice Server 5.9.x platform.

  • VCXP-16822 When Locale packs are applied to the Voice Server, if the user issues the command, "Play Voice Message" or "Play Text Message," the Genie asks if they want to hear both voice and text messages (if both are present).
  • CRVC-21935 Certain situations such as corrupted data file can cause the staff assignment data file to be incorrectly written. This can lead to a staff assignment outage if the server is restarted or the cluster is failed over. Staff Assignment console displays some or none of the expected sites, units, staff, or assignments, and it displays the following error message:

    "Vocera Staff Assignment Error: Unexpected exception. You may need to refresh or log back in to Vocera Staff Assignment. Please note the error and contact your Administrator."

    Workaround: Contact Vocera Support to recover or restore data.

  • CRVC-22026 Character limit in the Call Signaling Address field doesn't allow VSTG to start. After upgrading to VS 5.7.0 or higher version, VSTG doesn't connect to the Voice Server when the Call Signaling Address field value exceeds 60 characters. The Vocera Control Panel status remains to display the following message:

    “Connecting to Vocera Server..”

    Workaround: Reduce the number of IPs in the Call Signaling Addresses list (60 or less characters) and restart VSTG (stop/start) through the Run menu on the Control Panel.

  • CRVC-22921 During timezone or daylight savings time changes, the V5000 device screen and Voice server logs show a one hour time difference.
  • CRVC-23790 Passwords longer than 15 characters are not supported for mail configuration on the VRS while the VS supports passwords up to 64 characters.
  • CRVC-24121 A call placed to a badge from a VCS client while the smartphone is changing to a new wireless network can cause the badge to restart.

    Workaround: Try the call again once the wireless network change has completed.

  • CRVC-24212 Entering an invalid IP address in the “Report Server IP Address” field in the VS Admin Console can cause the Voice Server to crash.

    Workaround: Fix the invalid IP address in the “Report Server IP Address” field.

  • CRVC-24542 When running the “Badge Last Used” report from a scheduled reporting package, data can be missing from the “Days Last Used” column.

    Workaround: Manually run the report to see all data.

  • CRVC-24544 Certain situations such as forced failover due to maintenance upgrade can cause the staff assignment data file to be incorrectly written. Staff Assignment console displays some or none of the expected sites, units, staff, or assignments, and it displays the following error message:

    "Vocera Staff Assignment Error: Unexpected exception. You may need to refresh or log back in to Vocera Staff Assignment. Please note the error and contact your Administrator."

    Workaround: Contact Vocera Support to recover or restore data.