Vocera Communications System Release Notes

Vocera Voice Server Version 5.4.0.166

Updated: March 1, 2023

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

This section summarizes prominent features and functionality for each release.

What's New in 5.4.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 from versions 4.3.x, 4.4.x, 5.0.1, 5.1.0, 5.2.0, 5.2.1, or 5.2.3.

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

What's Fixed in 5.4.0

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

  • VCXP-9473/CASE-1321: Server failed with null pointer exception when groups.csv file was validated.
  • VCXP-9407/CASE-1401: Server failed due to Nuance Vocalizer errors.
  • VCXP-7144: The Genie enunciated urgent messages and did not announce the time stamp when the Play old messages command was used.
  • CRVC-18391: The Apache Tomcat Vulnerability (Nessus Plugin ID 133845).
  • CRVC-18213/CASE-1554: The availability incorrectly showed off-campus for the user who was available on-campus and logged in to voice.
  • CRVC-18144/CASE-1572: The Apache Tomcat AJP File Inclusion vulnerability (CVE-2020-1938).
  • CRVC-17689: Only the default Port values were accepted for the selected Mail Server Type. The custom port values added to the Port field on the Email > Mail Server Settings tab in the Administration Console were not saved.
  • CRVC-17724/CASE-1366: Repeatedly joining a group broadcast call, putting it on hold, joining another group broadcast, then leaving and call a user in a group broadcast call induced server failure.
  • CRVC-17631/CASE-1415: Some V5000 device serial numbers were not consistent with MAC addresses and not accepted in the Devices page of the Administration Console.
  • CRVC-17612: The audio stopped streaming between smartbadge and badge users as the badge user merged the call on hold to establish a three-way conference with another badge user.
  • CRVC-17069/CASE-1261: Server failed after the broadcast events.
  • CRVC-16888/CASE-1508: The following EAP-TLS properties were exposed in the BPE UI natively V5.ClientKeyPassword, V5.EAPTLSUseExtCert, and V5.UserName.
  • CRVC-15269/CASE-968: Memory leak in RSIP caused disconnections.
  • CRVC-14924: When the Delete all Text Message command was used, the text messages were not deleted from the Smartbadge.
  • CRVC-14177: Install and Uninstall errors were not suppressed, users were repeatedly presented with pop-up messages to restart to apply changes.

Known Issues

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

  • CRVC-18406/CASE-1614: The server fails when the call from a V5000 user is waiting to get into a conversation between B3000n and V5000 users.
  • 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-18248/CASE-1586: When the Shared Telephony has the Calling Party Number field populated, an extra semi-colon is inserted into the URI of the SIP invite.
  • CRVC-18174: When the VS and VMP versions mismatch during an upgrade, B3000n device users may hear an error message even if the page is successfully sent to VMP for delivery.

    Workaround: Upgrade all the servers to the same software version.

  • CRVC-18152: The B3000n badges do not support non-ASCII characters. The badge asserts and restarts repeatedly when a text message is sent with a special character in the subject or body.
  • CRVC-17969/CASE-1538: Vocera Report Server⁠—When more than one department is listed, the name of the department is removed from the Recognition Results by Department report.
  • CRVC-17930/CASE-1518: When the hourly option is used in the Telephony Usage Trend Report, hours are not labeled in the chronological order.
  • CRVC-17871: Sending an urgent message to a V5000 (firmware version 5.0.2.163) user crashes the device.
  • CRVC-17645: The mismatch in MasterHash calculation values for the same firmware version triggers a background firmware update when you upgrade the Voice Server from version 5.2.3 (and older) to 5.3.0 (and later).
  • 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-17343: When the cross-site option Receive Offsite Calls is disabled, offsite calls are still allowed.
  • CRVC-17242: Stopping the Voice Server and then starting it make the VCS client appear offline to other VCS and Web Console clients impacting the user's availability for voice calling.

    Workaround: Restart VMP.

  • 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-12136: Urgent TextMessage through email is not being delivered with urgent priority to VCS.
  • CRVC-3274/DE7741: Multiple Choice Response (MCR) messages fail to be updated on the sender's side.
  • CRVC-3232/DE8965: Non-VMI messages are not correctly enunciated when setting the MsgEnunciateModeSmartphone setting in properties.txt to a value of 1 or 3.
  • CRVC-2889/DE12345: The Vocera User Console allows a user to set call forwarding to another user when the permission is not available.
  • CRVC-2838/DE12547: When placing a call to a group with a normal or high alert status, the user is unable to call the sender back and results with the prompt "I'm sorry, no one answered".

    Workaround: Only alerts with urgent priority allow return calls.

  • CRVC-2795/DE12922: Text-to-speech playback is incorrect for groups written in all capital letters.

    Workaround: Spell group names using lowercase letters.

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

  • CRVC-2584/DE14965 (VRS only): Tomcat timeouts when running a data load if the email configuration is incorrect.

    Workaround: Correct the email configuration or disable the data load notification email.

  • CRVC-2583/DE14971: A rare condition causes a Vocera Staff Assignment bed per unit data to be lost resulting in errors in the Staff Assignment Console.
  • CRVC-2552/DE15222 (Staff Assignment only): The Ctrl+U keyboard short cut is no longer supported, you cannot use it to assign staff members to a bed.

    Workaround: Use the Staff Assignment User Console User Interface to navigate.

  • CRVC-2482/DE15551: When the server is in IPv6 address mode, the Broadcast Test tone does not work.
  • CRVC-2410/DE16138 (Vocera Report Server Only): Empty characters found in reports that are exported to a spreadsheet, specifically to a comma-separated values (CS) file.

    Workaround: Export to a Microsoft Excel format instead of CSV.

  • VCXP-10490: Disabling direct call feature for a user requires the direct call recipient field to be cleared.

    Workaround: To disable the direct call feature, clear the Enable Direct Call checkbox and remove the direct call recipient from the Direct Call to Another Badge, Group, or Address Book Entry field before saving the changes made to the user profile.

  • VCXP-10269: After putting an active call on hold, the Smartbadge user can use the Genie and not the microphone to initiate STT sessions.
  • VCXP-10259: The VRS Command Usage report displays two command entries (transcription and SendTextMessage) for a STT session.
  • VCXP-10008: On tapping the Touch to Edit option on the screen, the Smartbadge user hears a tone. The user is not silently taken to the edit conversation screen.
  • 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.