Vocera Communications System Release Notes

Vocera Voice Server Version 5.5.1.3 (HF1)

Updated: March 1, 2023

  1. Vocera Messaging Platform Compatibility
  2. What's New
  3. Prerequisites and Reminders
  4. Installation
  5. Fixed Issues
  6. Known Issues

Vocera Messaging Platform Compatibility

Warning: If you are running a version of Vocera Messaging Platform (VMP) older than 5.4, the connection between the Voice and VMP servers will be temporarily disconnected when a user deletes messages using a voice command on a badge. If this happens repeatedly, end users may experience delays in updates passed between the servers.

Workaround: Update VMP to 5.4 or later. Vocera strongly recommends using the same version on both Voice and VMP.

What's New

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

This section summarizes prominent features and functionality for each release.

What's New in 5.5.1.3 (HF1)

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

What's New in 5.5.1.2

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

Vocera Voice Server

What's New in 5.5.0

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

Vocera Voice User Interface

Vocera Voice Server

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.3.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.5.x platform.

What's Fixed in 5.5.1.3 (HF1)

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

  • CRVC-19903: On a new install (not an upgrade), the vsa_data2.txt file is missing; accessing the Staff Page feature of Staff Assignment results in a VAIException.

    The vsa_data2.txt file is now correctly delivered with the software.

What's Fixed in 5.5.1.2

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

This release has no fixed issues.

What's Fixed in 5.5.0

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

  • CRVC-17242: Stopping the Vocera Voice Server and then starting it made the VCS client appear offline to other VCS and Web Console clients impacting the user's availability for voice calling.
  • VCXP-10724: (Staff assignment) Server failed while writing or reading VSA data file.
  • CRVC-18634/CASE-1652: The DNS Client Windows service was disabled during VSTG and VCG (5.3.3) installation.
  • CRVC-18406/CASE-1614: The server failed when the call from a V5000 user was waiting to get into a conversation between B3000n and V5000 users.
  • CRVC-18248/CASE-1586: When the Shared Telephony had the Calling Party Number field populated, an extra semi-colon was inserted into the URI of the SIP invite.
  • CRVC-18152: The B3000n badges did not support non-ASCII characters. The badge asserted and restarted repeatedly when a text message was sent with a special character in the subject or body.
  • CRVC-17343: When the cross-site option Receive Offsite Calls was disabled, offsite calls were still allowed.
  • CRVC-17305/CASE-1300: After bulk import, the local site set for the user did not match with the site value available in the CSV file.
  • VCXP-10490: Disabling direct call feature for a user required the direct call recipient field to be cleared.
  • CRVC-18343/CASE-1665: On-campus VCS users are now no longer shown as off campus on VMP Web Console after restarting the Vocera Voice Server.
  • CRVC-19226/CASE-1766: VCS user calling to a group now times out after the default 50 seconds instead of 30 seconds.

Known Issues

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

  • CRVC-18405: The VCG restarts rarely when it is sending a signal to the client and the client connection is closed due to change in client IP.
  • CRVC-18334: Running the cert.bat batch file does not create the new self-signed certificate server.crt in the \apache\apache2\conf\ssl folder.

    Workaround: Before creating a new SSL certificate, delete all the files available at \vocera\apache\apache2\conf\SSL.

  • CRVC-17581: After upgrading VRS, the docs folder is not removed and help links are not accessible.

    Workaround: Install the doc pack after upgrading if you are using local documentation.

  • CRVC-17560: In a broadcast call, the initiator's smartbadge displays the name of the initiator on the screen instead of the group name.
  • CRVC-17551: After configuring the authentication type as EAP-TLS with custom certificates, the Client Key Password and Username fields become mandatory for Non-EAP-TLS with custom certificates type of authentication.

    Workaround: Select BPE > Security Settings > Authentication Type > EAPTLS, uncheck Use Custom EAP-TLS Certificates, configure all the required fields, and click Submit.

  • CRVC-17344: When RejectMessageOnUrgentPlayback is set to true in the properties.txt file, the urgent email message is not enunciated on the VCS device.
  • CRVC-17162/CASE-1297: Observed the same behavior for all text and all VMI message enunciation modes.
  • CRVC-17121: When RejectMessageOnUrgentPlayback is set to true, the urgent email messages interrupt the playback of another urgent message.
  • CRVC-2889/DE12345: The Vocera User Console allows a user to set call forwarding to another user when the permission is not available.
  • CRVC-2646/DE14443: Some learned names and commands are not available after an upgrade from Vocera Voice Server, version 4x to 5x.

    Workaround: If you encounter this issue, use the Learn a Name command as usual to ensure speech recognition performance.

  • VCXP-5998: Voice reminder commands are not available to users accessing Genie over VAA Direct Access.
  • VCXP-813/DE15526: Voice reminders are not played when "Announce Caller Name" is disabled.

    Workaround: Enable the Announce Caller's Name setting.

  • CRVC-19985: In deployments where the Vocera Server and VMP Server installations have mismatched versions, VCS and Smartbadge clients do not show new call log records. Once the servers are on the same version, the problem will be resolved.