Vocera Communications System Release Notes
Vocera Voice Server Version 5.10.0.329
Release Date: June 2024
Updated: July 18, 2024
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.0.329
This is a maintenance release that does not introduce any new features.
New and Enhanced Features in 5.10.0.328
This is a maintenance release that does not introduce any new features.
New and Enhanced Features in 5.10.0.316
The following list displays new features in this version of the Vocera Voice Server.
Vocera Voice User Interface
- The Vocera Voice Server administrators can now enable the Enhanced
Voice feature for the users with an Enhanced Voice license. This feature uses a
cloud-based Natural Language Understanding (NLU) speech recognition system to provide more
accurate and flexible results. For more details, refer to the Voice Server Release Notes specific to Enhanced Voice.
Vocera Voice Server
- Firmware and configuration for the following older badge models have
been removed from BPE and Voice Server:
- Smartbadge clients now use a different port for the signaling
connection to the Voice Server. If a network Access Control List (ACL) or firewall is in
place, the configuration may need to be updated to allow ports 49152-65535 between
Vocera badges and the Vocera Voice Server. For more information, refer to the Vocera IP Port Reference Guide.
- The Vocera Voice Server users can now configure email integration
with OAuth 2.0 authentication through Microsoft Graph, utilizing the Client Secret
method.
- The call routing logic for extension dialing has been enhanced. Calls
to specific extensions configured on users, groups, or address book entries no longer
loop through PBX or VSTG.
- The Vocera Voice Server now allows to preserve customized properties
in the properties.txt file during the Vocera Voice Server upgrade by creating a new
property file called properties.txt.user file.
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.57 |
| Apache Tomcat |
9.0.82 |
| JRE (Zulu built on OpenJDK) |
1.8.0_382 (Zulu 8.72.0.17)/17.0.8.1 (Zulu 17.44.53) |
| MySQL Server |
8.0.34(VS)/5.7.42 (VRS) |
| ODBC Connector |
Not installed; used at install-time only |
| TLS |
1.3 and 1.2 |
| PJSIP |
2.9 |
Vocera Firmware Versions
The following firmware versions are included in this release:
| Vocera Device |
Firmware Build Number |
| B3000n |
4.3.5.10 |
| C1000 |
1.5.0.115 |
| V5000 |
5.6.0.204 |
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.
- 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.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:
- Open the Vocera Voice Server
Administration Console and navigate to the System > Preferences
page.
- 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.9.x
platform.
Fixed Issues in Version 5.10.0.329
The following list includes items fixed or improved in this version of the Vocera Voice Server.
- CRVC-27152 V5000 badges remain in the 'Searching for Server' state after a
Signaling Gateway network error.
Fixed Issues in Version 5.10.0.328
The following list includes items fixed or improved in this version of the Vocera Voice Server.
- CRVC-27040 For customers with the VST connector configured, updates to call log
information may cause the VST connector to disconnect from the Voice Server, requiring a
manual refresh to resolve the issue.
- CRVC-27044 Modifying and saving a group with more than 1000 members may result in
the loss of some group membership or permission information.
Fixed Issues in Version 5.10.0.316
The following list includes items fixed or improved in this version of the Vocera Voice Server.
- CRVC-21606/CASE-2519 Unable to select and perform right-click actions on
text in the VS Admin Console when accessed through the Edge browser.
- CRVC-22026 Character limit in the Call Signaling Address field doesn't allow VSTG
to start. After upgrading to VS 5.7.0 or higher version, VSTG doesn't connect to the Voice
Server when the Call Signaling Address field value exceeds 60 characters. The Vocera Control
Panel status remains to display the following message:
“Connecting to Vocera
Server..”
- CRVC-22921 During timezone or daylight savings time changes, the V5000 device
screen and Voice server logs show a one hour time difference.
- CRVC-23579/CASE-3129
Vocera Voice Server groups marked for
deletion remain in the database as 'not active.'
- CRVC-23790 Passwords longer than 15 characters are not supported for mail
configuration on the VRS while the VS supports passwords up to 64 characters.
- CRVC-23849/CASE-3342 In Chromium browsers (version 5.6 and above), column
resizing is not supported in the VS Admin Console.
- CRVC-24121 A call placed to a badge from a VCS client while the smartphone is
changing to a new wireless network can cause the badge to restart.
- CRVC-24544 Certain situations such as forced failover due to maintenance upgrade
can cause the staff assignment data file to be incorrectly written. Staff Assignment console
displays some or none of the expected sites, units, staff, or assignments, and it displays
the following error message:
"Vocera Staff Assignment Error: Unexpected exception. You
may need to refresh or log back in to Vocera Staff Assignment. Please note the error and
contact your Administrator."
- CRVC-25489/CASE-3848 The disconnection of V5000 devices during login may
lead to the Voice Service crashing.
- CRVC-25152/CASE-3761 Using a Carriage Return in the Phone Number field
causes corruption during the Unload process.
- CRVC-25159/CASE-3741 C1000 users experiencing excessive call retries leads
to Vocera Voice Server
failovers.
- CRVC-25162/CASE-3778 The Vocera Voice Server crashes when a user tries to
rejoin the call that has already ended.
- CRVC-25416/CASE-3818 Experiencing intermittent audio loss during calls from
Cisco phones to VCS on iOS.
- CRVC-25429/CASE-3843 In a rare scenario, Tomcat vulnerabilities were
reported during security scan.
- CRVC-25672/CASE-3920
Vocera Voice Server generates a VMI
message response to VMP before sending the initial message, resulting in an error alert from
the VMP server.
- CRVC-26187/CASE-4025 VMI message causes a thread leak.
- CRVC-26230/CASE-4007 The Tomcat service experiences a failure due to an
exception but remains operational.
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.