Vocera Communications System Release Notes

Vocera Voice Server Version 5.3.4.12

Updated: July 6, 2020

What's New

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

This section summarizes prominent features and functionality for each release.

What's New in 5.3.4

Here is the summary of a few release-defining new features in the 5.3.4 version of the Vocera Voice Server.

Vocera Voice User Interface

This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.

Vocera care team connect

The new direct call feature as part of the Vocera care team connect solution enables patients and their care team to communicate with each other in bed locations lacking nurse call. Use of this feature can reduce the need to don and doff Personal Protective Equipment (PPE) and improve the patient experience.

When the direct call feature is enabled for a Vocera Smartbadge or B3000n device users, a patient can press the Call button to immediately place a call to a predefined care team recipient without having to interact with the Genie.

The Direct Call feature is disabled by default. Using the Administration Console, Administrators can enable it from the new Direct Call section in the User > Add/Edit User > Phone tab and add a direct call recipient (User, Group, or Address Book Entry) to the user profile. To create user profiles in bulk with care team connect features, Administrators can update Direct Call and Direct Call Target columns in the user-template.csv file and import it.

For information on Vocera device usage guidelines for the care team connect feature, refer to the Vocera V-Series Smartbadge User Guide and Vocera B-Series Badge User Guide available on Vocera Documentation Portal.

Vocera Voice Server

This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.

What's New in 5.3.3

Here is the summary of a few release-defining new features in the 5.3.3 version of the Vocera Voice Server.

Vocera Voice User Interface

This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.

Vocera Voice Server

This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.

What's New in 5.3.2

Here is the summary of a few release-defining new features in the 5.3.2 version of the Vocera Voice Server.

Vocera Voice User Interface

This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.

Vocera Voice Server

This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.

What's New in 5.3.1.102

This is a maintenance release only.

There are no new features for this release.

What's New in 5.3.1.100

This is a maintenance release only.

There are no new features for this release.

What's New in 5.3.1.99

This is a maintenance release only.

There are no new features for this release.

What's New in 5.3.1.97

Here is the summary of a few release-defining new features in the 5.3.1 version of the Vocera Voice Server.

Vocera Voice User Interface

This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.

Vocera Voice Server

This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.

International Locale Support

What's New in 5.3.0

Here is the summary of a few release-defining new features in the 5.3.3 version of the Vocera Voice Server.

Vocera Voice User Interface

This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.

Vocera Voice Server

This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.

Documentation Updates

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 version 4.3.x or later.

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

What's Fixed in 5.3.4

This release has no fixed issues.

What's Fixed in 5.3.3

The following list includes nothworthy issues fixed in this release.

  • CRVC-17739/CASE-1296: The Vocera Report Server was unable to load data from the Vocera server automatically when automatic dataload was enabled and scheduled.
  • CRVC-17160/CASE-1286: When VMP was disabled and the MsgEnunciateMode was set to 0, recipients heard Message from email after the alert tone.
  • CRVC-17112/CASE-1293: Urgent message prompts were enunciated on the badge and Smartbadge when the sender information was missing, the text message alert priority was high, and EnunciateMode was set to 6.
  • CRVC-16887/CASE-1231: The BCU_Certs.bat file searched for the incorrect certificate subject, subject=CN= in the PEM file while configuring multiple badges.
  • CRVC-16868/CASE-1225: When the SSID name included the special character, #, all the text after # got removed while upgrading the badge through BCU.
  • CRVC-16775/CASE-1272: When a Call or DND button was pressed to respond to an urgent VMI message, Genie responded with, Message play cancelled.
  • CRVC-16602/CASE-1146: TCP Read Error was observed in the response to the trunk status request, OPTIONS SIP.
  • CRVC-16526/CASE-1144: Tiered Administrator Web Console view showed groups that were renamed, out of alphabetical sequence.
  • CRVC-16525: The device type, V5000 was missing from the options listed for entering default report parameters to add or edit a report package.
  • CRVC-16199: The audio stopped streaming between the Smartbadge and Badge as the Badge user placed the call on hold and then rejoined while the Smartbadge screen was showing Call Waiting from another Badge user.
  • CRVC-15754: The VCS screen continued to display Call on hold when the DND/Hold button was pressed to rejoin the call that was placed on hold.
  • CRVC-15597: The wireless credentials were not encrypted in profiles.txt.
  • CRVC-15299/CASE-947: When the call failed to disconnect, the Call Status column in VS Status Monitor did not show inactive status for the badge user who initiated the call.
  • VCXP-9126/CASE-1277: The active server failed during grammar write.
  • VCXP-9101/CASE-1265: After completing the remote restore operation, the standby server failed with a duplicate SpellCallRecordInfo entry.
  • VCXP-7737: By default, the Favor Frequently Called option was disabled for users and departments.
  • VCXP-6953: Observed delay in delivering weekly voice reminders.
  • VCXP-6802: Genie was enunciating help when the user recorded a name using voice commands after logging in.
  • CMSG-10761: When the client sent an empty signal to Vocera Client Gateway server, the signal was not processed properly and the call dropped.

What's Fixed in 5.3.2

The following list includes nothworthy issues fixed in this release.

  • CRVC-16236: The Vocera Voice Command Poster link in the Documentation page of Admin Web console was not found.
  • CRVC-15859: Vocera Server failed after the upgrade from 4.x to 5.2.3 during login due to apostrophe in site name.
  • CRVC-15842: The conversion from vsa_data.txt to vsa_data2.txt failed during upgrade of Staff Assignment.
  • CRVC-15485: Smartbadge did not respond when the call button was pressed to login and threw exception when touch device signal was received.
  • CRVC-15318: An incorrect internal group name was generated when the user added a group name that began with the word, everyone and it resulted in server failure.
  • CRVC-15306/CASE-1091: Upgrading VRS from 5.2.3 to 5.3.1.92 with SSL-enabled required port information in the URL to access Web Console.
  • CRVC-15283: Users with last names starting with A to C were missing from the Vocera Server Administration Web Console.
  • CRVC-15100/CASE-887: VMP received Operation Failed as the response from the Voice Server while processing voice logout request.
  • CRVC-14629: Staff Assignment Web Console page failed to load after upgrading from Vocera Voice Server 5.2.2.199 or older versions.
  • VCXP-8081: Observed gender switching when the VMI message was played back.
  • VCXP-7976: The Vocera Server failed when offering to learn a name. The Offer to Learn a Name command was being issued before the system was prompting for the action.
  • VCXP-7770: Deleting members of sub-department groups caused Vocera Voice Server to fail.
  • VCXP-7613: Spelled names in memory reduced time connecting calls.
  • VCXP-7471: Calls failed to connect when the group name had an apostrophe surrounded by spaces.

What's Fixed in 5.3.1.102

The following list includes nothworthy issues fixed in this release.

  • CRVC-13893: Vocera Voice Server failed when a user initiated a broadcast and then ended it while another user in the broadcast was initiating a call.

What's Fixed in 5.3.1.100

The following list includes nothworthy issues fixed in this release.

  • CRVC-15859: Vocera Server failed after the upgrade from 4.x to 5.2.3 during login due to apostrophe in the site name.
  • CRVC-15842: Conversion from vsa_data.txt to vsa_data2.txt failed during the upgrade.
  • VCXP-7613: Keeping spell recognition in database memory reduced Vocera Voice Server response time by not having to query the database for each request.
  • VCXP-7471: Dead air was seen when the group name had an apostrophe surrounded by spaces.

What's Fixed in 5.3.1.99

The following list includes nothworthy issues fixed in this release.

  • CRVC-15556: Vocera Server with standard license failed when a badge connects to server.

What's Fixed in 5.3.1.97

The following list includes nothworthy issues fixed in this release.

  • VCXP-5561: Text reminders missed, when the user was offline, were displayed as text messages on the badge when the user logs back in.
  • CMSG-9208: VCG occasionally failed when VCG for VCS client connection management was enabled in VMP.

What's Fixed in 5.3.0

The following list includes nothworthy issues fixed in this release.

  • CRVC-14021: Vocera Server failover due to server.SpeechPortServiceClientContext$PostRunnableEvent.
  • CRVC-13845: After failover, AutoLogout check happened with a timeout value of 10 min rather than the configured value.

    In a rare case, a customer experienced a failover and network event that kept a number of badges from communicating with the server. AutoLogout was done with a time value of 10 min rather than the configured value of 120 min. Resulting in 3500 users being logged out.

  • CRVC-13762: VS Install Guide gave incorrect instructions for updating a license.

    Instructions for Vocera license upgrades have been updated to cover all upgrade scenarios for cluster and stand-alone environments, and include the new Refresh option when adding users or telephone lines.

  • CRVC-13191: In some situations, Apache services were not installed as part of the VS 5.2.3 installation.
  • CRVC-13065: Vocera Server Version 5.2.3 installer failed with GetPhysicallyInstalledSystemMemory failed with unknown error code 0.
  • CRVC-12595: Vocera Server was not appending call back option to VMI messages sent to multiple recipients.

    Messages sent to multiple recipients were interpreted as a broadcast and the callback option was not appended to the enunciation. The call back option was added to the badge menu prompt for the message, but the user must scroll through the message to select the Call option.

    The Callback option must be checked and the phone number provided.

  • CRVC-12415: After upgrading to version 5.2.2, hangup macro did not send DTMF.
  • CRVC-12137: Site name containing an apostrophe caused a failover when a member of the Site was called.
  • CRVC-12001/DE15929: (VCS users only) The Who Called command failed to list callers that attempt to reach a user when the user was not in DND mode.
  • CRVC-9172: Configurable VMI Reconnect Email Notifications: Every VMI reconnect event triggered an email notification. The reconnect email notifications were sent once every 10 minutes. If this interval needs to be adjusted, contact Vocera Support.
  • CRVC-3158: HandleUnexpected in state server - AsktoMerge/Unhold crash.

    A rare race condition can occur when a user tries to conference two parties while one of the users has put the caller on hold and is rejoining the call during the conference operation. This situation is now properly handled.

  • CRVC-2889: User can set forwarding target without permissions.

    The Vocera User Console allows a user to set call forwarding to another user even when the permission has not been granted. Forwarding options have been added to allow Vocera Administrators to define forwarding permissions for individual users and groups.

  • CRVC-2887/DE12350: In Administration Console under Defaults > Genie Settings, the speaker icons widget failed to play the genie voice sample as expected.
  • CRVC-2448: VMI dll-Message method did not accept complete group name.
  • VCXP-5852: Groups with "T" in the name were pronounced as "tons" rather than the desired "tee". VMI messages with the same text were pronounced correctly.
  • VCXP-5493: Making Everyone group a subdepartment led to failover.
  • VCXP-809: Handle no speech when user was leaving a voice message. If a user was slow to start speaking in a voice mail message, a timer ended the message after one minute.
  • VCXP-784: Server failed when an email integration message was sent with malformed characters.

Known Issues

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

  • CRVC-17689: Only the default Port values are 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 are not saved.
  • 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).

    Workaround: None.

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

    Workaround: Initiate a three-way conference call using the Conference command or invite another party to an existing call using the Invite command.

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

    Workaround: None.

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

    Workaround: None.

  • CRVC-17343: When the cross-site option Receive Offsite Calls is disabled, offsite calls are still allowed.

    Workaround: None.

  • 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-17121: When RejectMessageOnUrgentPlayback is set to true, the urgent email messages interrupt the playback of another urgent message.

    Workaround: None.

  • CRVC-14177: Install and Uninstall errors are not being suppressed, users are repeatedly presented with pop-up messages to reboot to apply changes.

    Workaround: Do not reboot when prompts are displayed. Wait until the installation or uninstall process is complete to reboot.

  • CRVC-12136: Urgent TextMessage through email is not being delivered with urgent priority to VCS.

    Workaround: None

  • CRVC-3274/DE7741: Multiple Choice Response (MCR) messages fail to be updated on the sender's side.

    Workaround: None

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

    Workaround: None

  • CRVC-2889/DE12345: The Vocera User Console allows a user to set call forwarding to another user when the permission is not available.

    Workaround: None.

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

    Workaround: None

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

    Workaround: None

  • 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-5998: Voice reminder commands are not available to users accessing Genie over VAA Direct Access.

    Workaround: None

  • VCXP-813/DE15526: Voice reminders are not played when "Announce Caller Name" is disabled.

    Workaround: Enable the Announce Caller's Name setting.

Known Issues with Vocera Clinical Workflow Engine (CWE)

  • CRVC-2423: Customers with Clinical Workflow Engine (CWE) are unable to upgrade to Vocera Voice Server, version 5.2.3.

    Workaround: None.

    Contact customer support if your Vocera Voice Server environment interoperates with CWE and you are upgrading to Vocera Voice Server 5.2.3. CWE is not compatible with VS versions newer than VS 5.2.2.

  • High and Normal alerts from CWE are not getting delivered on VCS client.

    Workaround: Two property name-and-value pairs are required. The properties are comma-separated, so if you use more than one CWE client ID, separate them with commas. The client ID must appear in both lists, and VMP must be in the SuppressAlertClientID list. Two flags have been added to the properties.txt file; The alerts are now being delivered in the VCS client and all alerts appear in the Secure Messages list.

    SuppressAlertClientID={CWE client id},VMP
    CWEClientIDs={CWE client id}

Deprecated Features

Starting with VS 5.0, the following features and components are no longer supported unless noted otherwise.

  • Windows Server 2003.
  • Users can no longer select Ring-Tone -15 to Ring-Tone -17. If you had previously selected one of these ring tones, your setting is reset to the system default during the upgrade process.
  • Vocera Telephony Server (The Vocera SIP Telephony Gateway completely replaces the legacy Vocera Telephony Server. Support for analog and digital PBXs is still provided by hardware gateways such as the Dialogic Media Gateway.)
  • SysAutoCheckLogin property in propeties.txt. This server-side feature has been replaced with an automatic login reminder played locally on the badge.
  • Voice Prints.
  • Care Transition (voice integration).
  • Vocera Connect for Smartphone.
  • Vocera Connect - Cellular.
  • Multiple recognition servers.
  • B1000a.
  • Dictation.
  • TCP Genie.
  • Client Redirect Utility.
  • Vocera Connect for Cisco (A component of the Vocera Voice Server which provided Vocera services to CUCM via Cisco JTAPI, a Java telephony interface that exposes full call control of Cisco Unified Wireless IP Phones.)
  • Vocera Motorola Smart Phone.