Vocera Communications System Release Notes

Vocera Voice Server Version 5.10.2.76

Release Date: September 2024

Updated: September 12, 2024

  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.10.x platform has new features and enhancements.

This section summarizes prominent features and functionality for each release.

New and Enhanced Features in 5.10.2.76

This is a maintenance release that does not introduce any new features.

New and Enhanced Features in 5.10.2.66

This is a maintenance release that does not introduce any new features.

New and Enhanced Features in 5.10.2.63

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

The Vocera Voice Server can now be integrated with Vocera Edge to enable the following interoperability features:

  • User, Group, and Group membership is now synchronized between Voice Server and Edge.
  • Real-time presence information for badges and Edge clients is shared between systems.
  • Voice communication including calls, broadcasts, and emergency broadcasts can now involve both Badges and Edge clients.

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.58
Apache Tomcat 9.0.87
JRE (Zulu built on OpenJDK) 1.8.0_402 (Zulu 8.72.0.17)/17.0.8.1 (Zulu 17.44.53)
MySQL Server 8.0.36(VS)/5.7.42 (VRS)
ODBC Connector Not installed; used at install-time only
TLS 1.3 and 1.2
PJSIP 2.14

Vocera Firmware Versions

The following firmware versions are included in this release:

Vocera Device Firmware Build Number
B3000n 4.3.5.10
C1000 1.6.0.104
V5000 5.6.1.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:

  • Verify that you have one of the following Vocera products installed, if you are upgrading from an earlier version of Vocera:
    • Vocera Server Version 5.x (5.0.1 or later)
    • The GA release or any service pack of Vocera Server 4.3.0 or 4.4.0.
  • Ensure all B3000n badges are operating on firmware version 4.3.1.17 or later before upgrading. Otherwise, a signaling change may cause B3000n badges to continuously reboot. B3000n firmware 4.3.1.17 can be installed on Vocera Voice Server version since 4.3 SP4. B3000n firmware version 4.3.1.17 ships with Voice Server 5.3.0.415.
  • Starting with Vocera Voice Server 5.7.0, B2000 devices are no longer supported.
  • Verify that you have turned the Compatibility Mode off in the browser, if you are using any of the following consoles:
    • Administration Console
    • User Console
    • Staff Assignment Console
    • Report Server Console
  • Perform one of the following to get a telephony connection to Vocera Voice Server 5.x:
    • If you have an analog or digital PBX, connect to the Vocera SIP Telephony Gateway through a hardware gateway such as the Sangoma Media Gateway.
    • If you have a SIP PBX, connect to the Vocera SIP Telephony Gateway directly.

Installation

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

Installation prerequisites

  • If Vocera Secure Texting (VST) is installed in your environment, you must uninstall the Vocera Secure Texting Sync Connector before you upgrade to the latest version of Vocera Voice Server.

    Re-install the Vocera Secure Texting Sync Connector after you complete the Vocera Voice Server upgrade.

    See How to Uninstall the Vocera Secure Texting Sync Connector in the VST Vocera Administrator Guide.

  • Ensure that you download and install the latest version of the Vocera Secure Texting Sync Connector.
  • Ensure that you have installed an English-based language pack in Windows Operating System where you are installing Vocera Voice Server and any subsequent Vocera localization packs.

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.10.x platform.

Fixed Issues in Version 5.10.2.76

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

  • CRVC-27846 Voice Server no longer sends alert messages, voice email messages, and email messages to the Vocera devices when the mail server authentication is configured to use Microsoft Graph.

Fixed Issues in Version 5.10.2.66

This release has no fixed issues.

Fixed Issues in Version 5.10.2.63

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

  • VCXP-18613 When a user sends a text message to another user with the “Send a text message” command from a Smartbadge connected to VMP, the text message is not delivered.
  • VCXP-18448 When the French-Canadian localization pack is installed on the Voice Server, the server logs cannot be read by Vocera Analytics due to a log format error.
  • VCXP-18197 When the French-Canadian localization pack is installed on the Voice Server, the emergency broadcast location message is displayed in English instead of French.
  • VCXP-18170 Genie audio can unexpectedly use ports outside the documented port range of 7500-8220.
  • VCXP-18147 For customers with Enhanced Voice enabled, saying the command “Transfer to 1234” without specifying “extension” results in no response from the Genie.
  • VCXP-18144 For customers with enhanced voice enabled, the Genie does not provide the site name when disambiguating multiple users with the same name in both the current site and the global site.
  • VCXP-18129 For customers with enhanced voice enabled for guest access calls, the Genie does not search the configured shared sites.
  • VCXP-18110 For customers with enhanced voice enabled for yes/no interactions, the Badge button responses are not processed, requiring the user to verbally say "yes" or "no."
  • VCXP-18109 For customers with enhanced voice enabled, the “Add me to multiple groups” command does not correctly process confirmation responses when multiple groups are offered in the response.
  • CRVC-27152 In certain scenarios involving momentary network disruption, the signaling gateway service can stop listening for connections. This results in Smartbadges being in a "Searching for Server" state and requires a voice cluster failover to resolve.
  • CRVC-27146 A rare race condition involving a user receiving a conference call and a separate one-to-one call at approximately the same time can cause the Voice Server cluster to failover.
  • CRVC-27044 Modifying and saving a group with more than 1000 members can cause some group membership or permission information to be lost.
  • CRVC-27040 For customers with the VST connector configured, updates to call log information can make the VST connector to disconnect from the Voice Server requiring a manual refresh to resolve.
  • CRVC-27040 In certain rare cases, special characters such as emoji’s can end being stored on the Voice Server causing the backup file to be invalid.

Known Issues

A few issues are known to exist in the Vocera Voice Server 5.10.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.10.x platform.

  • CRVC-27900 Ringback tone observed on calls made to badges following the system upgrade from version 5.8 to 5.10.
  • 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.