Vocera Server release 5.2.0 introduces the following new features:
Urgent messaging port enhancement: The mechanism used to enunciate urgent messages on devices has been enhanced to use a single urgent messaging port without requiring the use of multicast. This new behavior is enabled by default.
Forwarding of group calls to offline members: A new option is available to enable calls to a group without online members where the off-network forwarding behavior places the call to the first available group member. See the Vocera Administration Guide for more information on enabling this new feature.
Auto add-me: An optional feature is available to prompt users to add themselves to groups at login time. Contact Vocera Customer Support for more information.
Prevent Vocera User Console users from changing their site: The Vocera User Console has been modified to no longer allow logged in users to change their own site.
Package JRE 1.8: All Vocera Server products (for example, Vocera Report Server, Vocera Collaboration Suite, and Vocera Care Team Synchronization) install JRE Version 1.8.
Text-to-speech enunciation enhancement: The Vocera Genie enunciates using the gender consistent with the user’s selected persona.
Implement data check ability to export to CSV: The Data Check feature in the Vocera Administration Console has been enhanced to allow an administrator to export the list of results to a CSV file for review. The new export function allows exporting up to 300,000 errors or warnings. The data check window will continue to limit the display to 3000 results.
The "Add me to Multiple Groups" voice command now utilizes user enrollments: The “Add me to Multiple Groups" dialog has been enhanced to make use of a user's personal group name enrollments.
Learned command now available for “Learn a Name”: The “Learn a Name” command is now available for enrollment creation during the “Learn More Commands” Genie instruction.
User login prompts enhancement: The login dialog has been enhanced to remind the user to spell their first and last name when they are having problems logging in with their full spoken name.
Voice reminders: A new feature has been added to allow users to record scheduled voice reminders for playback at a later time.
Temporary license key enhancements: The license expiration mechanism of temporary Vocera Voice license keys has been modified to allow the server to resume using the permanent key when the temporary key expires. The expiration process will automatically restart the server within 24 hours after a license key expiration at which point it can continue operation using the existing permanent license key. For clustered servers the restart will trigger a cluster fail-over.
Changes to the installation executable: The name of the executable used to launch the Vocera Voice server installation has been renamed from Launcher.exe to VoceraSuiteInstaller.exe
Guest access optional call command: The Guest Access voice recognition grammar has been modified to allow callers to optionally say “call” before saying the name of the user or group they wish to reach. Callers can also continue to speak the name without saying “call” first.
BCU authentication protocol unique certificate support: BCU has an improved EAP-TLS unique certificate configuration support for B3000N badges. Please contact Vocera Technical Support for more information.
Don't play "Who Called" for VCS clients: The automatic “Who Called” announcement has been suppressed for VCS clients with missed calls. The alerting of missed calls and voice mails is now visually presented in the UI of the VCS client.
The latest version of Vocera Voice Server and its related servers (the VRS, VSTG, and VCG) require a 64-bit operating system (Windows 2012 R2 or Windows 2008 R2).
If you're upgrading from an earlier version of Vocera, make sure one of the following Vocera products is installed:
If you require a telephony connection to Vocera Voice Server 5.x and you have an analog or digital PBX, you must connect to the Vocera SIP Telephony Gateway through a hardware gateway such as the Dialogic Media Gateway. If you have a SIP PBX, you can connect to the Vocera SIP Telephony Gateway directly.
Starting with VS 5.0, the following features and components are no longer supported unless noted otherwise below.
Windows Server 2003
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.)
Voice Prints (May be replaced by another form of verification in a later release)
Care Transition / voice integration
Vocera Connect for Smartphone
Vocera Connect - Cellular
Multiple recognition servers
Client Redirect Utility
Frequently Called Departments (May be supported in a later release)
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
SysRecParms and SysFreqDeptRecParms (These custom settings are ignored if they are specified in properties.txt, and they are not necessary in the 5.0 release)
To upgrade from Vocera Server 4.3.x, 4.4.x, 5.0.1, or 5.1.0:
The server updates your database and removes any settings for deprecated features.
To perform a new install:
The following list contains fixes and improvements made to the Vocera 5.2.0 platform.
For Vocera Voice Server:
Server failure when a badge user is dictating DTMF digits: The server fails when a badge user says the command Cancel while using the DND double-tap feature to dictate DTMF digits during a badge call. This situation is now properly handled. (DE10257)
VCS client displays Operation Failed error: Under certain conditions involving poor wireless coverage, VCS users get stuck in a state where attempted new calls see the error "Operation Failed" and inbound calls are treated as if the user is offline. This situation is now properly handled. (DE9310)
DND override setting doesn't apply to CWE messages: Messages from the Vocera Clinical Workflow Engine ignore the DND override settings. This can result in unexpected behavior. (DE9706)
Error heard while recording name prompt: In certain situations when recording a name the user may hear "I'm sorry, the prompt you are recording is in use". This situation is now properly handled the and the user will be able to successfully record the name. (DE7068)
Urgent broadcast initiated via VAA causes server failure: Using the urgent broadcast inbound dialing macro with VAA causes the server to fail. This situation is now properly handled. (DE9732)
VS denies VAI application from standby but allows from active: The VAI application running on a standby node is not automatically trusted. The logic is changed so that VAI applications are trusted on a standby node. Because of this change, Vocera Server cluster IP addresses are no longer required in the VAI application IP address list in Vocera Administration Console. (DE9249)
The importcert.bat file missing in Vocera Version 5.1.0: Active Directory configuration tool importcert.bat missing from \vocera\server directory. The importcert.bat is now present in the \vocera\server directory as mentioned in the documentation. (DE9161)
Using accent characters in Last Name can result in a duplicate entity name: Accented characters used in identical user first name and last name combinations can result in a system crash. Certain locales allow the use of accented characters in user names, installs in these locales can now correctly handle users with identical first and last names when accented characters are used. (DE112)
Standby server fails with error during synchronization: The standby server fails and restarts due to an error during synchronization. The error is now properly handled and the standby server no longer restarts. (DE3238)
Server failure caused by overlapping calls with urgent conference: The Vocera Server fails caused by a rare scenario involving four users participating in overlapping calls and urgent conferences. The situation is now properly handled and the server no longer crashes. (DE6586)
When calling through VSTG, the audio drops out intermittently after silence suppression on genie prompts: Phone calls to Guest Access or VAA hear server prompts with intermittent audio cut-offs. The audio now plays correctly. (DE1606 and DE2151)
VMI Messages not marked as read: VMI messages do not get marked as read when a call back is invoked via voice command. The VMI message is now correctly marked as read when call back is used. (DE8268)
4.x to 5.x enrollment conversion doesn't fully complete with some files: Users with a large number of enrollments can cause those enrollments to fail to be fully converted during the upgrade from 4.x to 5.x. The problem has been resolved and all enrollments are now properly converted during upgrade. (DE8043)
4.4.x backup of enrollments with 150+ learned names do not convert to 5.x enrollments properly, causes problem with remote restore: Users with a large number of enrollments can cause those enrollments to fail to be fully converted during the upgrade from 4.x to 5.x. The problem has been resolved and all enrollments are now properly converted during upgrade. (DE7859)
If a buddies list contains only a group and no buddies, there will be no buddies rule generated in the grammar: When a user’s Buddy list includes a group but no individual users, the server does not update the voice grammar, and the user will be unable to place calls. This situation is now properly handled and the user can place calls. (DE1518)
Names displayed in the AutoComplete results list box are not sorted in alphabetical order: Names displayed in the AutoComplete results list box are not sorted in alphabetical order. The names are now sorted correctly. (DE5420)
Vocera server fails to properly shut down: Certain situations cause the Vocera Server halts the shutdown sequence and displaying the message "in bye() loop not done...". The server now properly detects this situation and will recover which allows the shutdown sequence to finish automatically. (DE7592)
The Vocera Server Cluster fails to be established when the server has multiple IP address configured: Servers with multiple IP addresses are not able to join a VS cluster. This configuration is now properly handled and the cluster can now properly be established. (DE122)
Using site transfer triggers Tomcat to reconnect to the server controller: Using site transfer option causes an interruption to web console activity. The site transfer option no longer causes an interruption. (DE6421)
Null pointer exception with AddToMultipleGroups: A rare server failure caused by improper processing of the Add Me to Multiple Groups command. This situation is now properly handled and the server no longer fails. (DE5223)
Blank device label after an upgrade: The device label is now properly preserved during upgrade. (DE3661)
The standby node fails become active: A timing issue caused a cluster fail-over to take longer than expected. This situation is now properly handled and the cluster fail-over proceeds as expected. (DE3659)
For Vocera Report Server:
For Vocera Collaboration Suite:
This section provides information about known product defects and limitations in the current release.
The following list provides information about known product issues in the Voice Server:
Using 'Learn more commands' to learn a name for "Locate" does not work: An enrollment created for the "Locate" command does not work correctly which can cause unexpected recognition failures when using the "Locate" command. (DE10366)
Java script error on the Devices tab in the Administration Console: In Administration Console on the Devices Tab you may receive a Java script error message when adding or editing a device. Workaround: Enable IE compatibility view for the page. (DE10860)
Broadcasting to Everyone Everywhere results in the standby server to go in discovery mode: In a large system a broadcast from a Vocera device to a group containing many users (such as the Everyone Everywhere group) can result in the standby server disconnecting from the cluster. This standby server will automatically recover from such a situation and rejoin the cluster. (DE10233)
Non-VMI messages are not being enunciated: Non-VMI messages are not correctly enunciated when setting the MsgEnunciateModeSmartphone setting in properties.txt to a value of 1 or 3. (DE8956)
VMP Server messages are not updated on the sender side: Messages containing Multiple Choice Response (MCR) options from VCS clients or VMP web console might not be properly tracked on the sender side when the badge user responds. This situation occurs when MCR options are too long for the badge to display or if the MCR options contain certain special characters. (DE7741)
The following list provides information about known product issues in the Badge Configuration Utility:
The Badge Configuration Utility (BCU) does not successfully install from the Vocera Installer: The Vocera Server Installer (VoceraSuiteInstaller.exe) fails to complete the BCU Installation. (DE10598)
The workaround is to use the BCU.exe file included in the
The following list provides information about known product issues in the Vocera Telephony Gateway:
SIP CANCEL message not processed correctly on Avaya PBX: If a call from a Vocera device to an endpoint on an Avaya PBX is cancelled then the SIP CANCEL message sent by the VSTG may not be properly handled. This can result in the call continuing to ring on the Avaya side. (DE10272)