Vocera Communications System Release Notes
Vocera Voice Server Version 188.8.131.52
Updated: February 5, 2021
VS and VMP 5.5.x On Hold
Important: Vocera is investigating several issues related to the 5.5.x releases.
Until further notice, do not use VMP 5.5.x or VS 5.5.x; continue using VMP 5.4.0 and VS 5.4.0.
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.0
The following list displays new features in this version of the Vocera Voice Server.
Vocera Voice User Interface
- Administrators can send an emergency broadcast as an urgent call to a
member of the emergency broadcast group. Using the Administration Console, Administrators
can enable the Send Emergency Broadcast as Urgent Call option from
the Add New/Edit Site > Info page.
Vocera Voice Server
- Deletion of location, user, and group entities can be controlled using the
HastyDelete property. This hidden property is set to
true by default.
- The messages or names containing a number were pronounced as a string of digits. For
example, Genie enunciated "123" as "one two three" and not "one hundred twenty three".
With this release, numbers up to 3 digits in length are pronounced as numbers (one
hundred twenty three) by default and not as a string of digits (one two three). This
behavior is controlled by the new hidden property,
DigitLengthForEnunciation and can be disabled, if desired.
Third-party Software Versions
The following third-party software versions are included in this release and provide
64-bit compatibility or security enhancements:
|Apache HTTP Server
|JRE (Zulu built on OpenJDK)
||1.8.0_252 (Zulu 184.108.40.206)
Vocera Firmware Versions
following firmware versions are included in this release:
||Firmware Build Number
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
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 or 4.4
- 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
- If you have an analog or digital PBX, connect to the Vocera SIP
Telephony Gateway through a hardware gateway such as the Sangoma Media
- If you have a SIP PBX, connect to the Vocera SIP Telephony Gateway
Follow these instructions to install Vocera Voice Server or upgrade it to
the latest version. .
- 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
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.
- 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.
- 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
- Update the values in your database as follows:
- Open the Vocera Voice Server
Administration Console and navigate to the System > Preferences
- Choose Save Changes.
The server updates
your database and removes any settings for deprecated
- 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.
The following list contains fixes and improvements made to the Vocera Voice Server 5.5.x
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
- 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
- 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
- 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.
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
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.
Workaround: Create an empty vsa_data2.txt file and restart the application.
- 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
creating a new SSL certificate, delete all the files available at
- 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.
BPE > Security Settings >
Authentication Type >
EAPTLS, uncheck Use Custom EAP-TLS
Certificates, configure all the required fields, and click
- 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
- 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
a Name command as usual to ensure speech recognition
- 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
Workaround: Enable the Announce Caller's
- 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.