New and Enhanced Features in 5.10.4.40

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

Simultaneous login―Users can now simultaneously log in to both the Vocera badge and the Edge client for voice calls and messaging.
Unified messaging―Users of the Vocera badge and Edge client can now participate in one-to-one or group messaging with features such as message prioritization, read receipts, patient-tagged conversations, quick messages, media attachments, and acknowledgment requests.
Unified alerting―Alerts can now be sent to both Vocera badges and Edge clients.
Edge Mobile client licensing―Edge Mobile clients are entitled under a separate license model and will no longer consume concurrent Voice user licenses when connected to Vocera Voice Server.

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.62
Apache Tomcat	9.0.91
JRE (Zulu built on OpenJDK)	1.8.0_482 (Zulu 8.80.0.17)/17.0.8.1 (Zulu 17.52.17)
MySQL Server	8.0.38(VS)
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.13
C1000	1.6.0.104
V5000	5.6.1.12

Note: If your Voice Server is connected to Edge 4.15.0 or later, you should upgrade the V5000 firmware to 5.7.0.217 or later, to enable the new features such as simultaneous login, unified messaging, and unified alerting.

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:
  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.10.x platform.

Fixed Issues in Version 5.10.4.40

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

VCXP-19405 When Enhanced Voice is enabled, forwarding all calls to a group with a name containing five consecutive digits (such as Room 12345 Respiratory) can result in a failure which causes the badge to be stuck in a listening state until it is rebooted.
CRVC-27986 The default Root files for Tomcat were located in the WEB-INF directory alongside the tomcat_deliver files.
Now, only the tomcat_deliver files are present.
CRVC-28282 The “urgent message” prompt is announced twice when an urgent message is automatically enunciated on a Smartbadge.
CRVC-28030 When a Smartbadge user receives a voice message, they are prompted to press the Call button to play it. However, pressing the Call button does not function as expected.

Known Issues

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

CRVC-27900 Ringback tone observed on calls made to badges following the system upgrade from version 5.8 to 5.10.
CRVC-27909 When a badge user in handset mode has the “announce through speaker” setting enabled, incoming voice messages will play on the main badge speaker instead of the handset speaker.

Vocera Communications System Release Notes

Vocera Voice Server Version 5.10.4.40

Release Date: November 2024

Updated: December 11, 2024