Welcome to Vocera Server 5.0.1! This section summarizes the new and enhanced features in this release.
The latest version of Vocera Voice Server provides the following enhancements:
VCS client enunciation setting enhancement: You can set the VCS clients to not enunciate urgent messages using the MsgEnunciateModeSmartphone property. See the Vocera Server Administration Guide for more information about setting the MsgEnunciateModeSmartphone property.
The following list contains fixes and improvements included in Vocera 5.0.1 Hot Fix 2.
Fixed: Incorrectly formatted signals from VCS clients can cause the Vocera server to restart. – The server now correctly ignores these signals. (US13302)
Fixed: A race-condition in the recognition process can result in recognition services becoming unavailable. – When this occurs users will begin to hear “I’m busy at the moment, please wait” when they try to summon the genie. This problem has been resolved. (DE6661)
Fixed: The Vocera server is restarted because the system fails to properly store the audio when a user is performing the “Record a Name” sequence. – With this fix and when the scenario is encountered, instead of restarting the server, the system retries the operation and in the event of a failure reports the error and continues to run normally. (DE6056)
Fixed: The system restarts in certain instances if a user attempts to answer a Yes/No question via a voice command and also presses the call or DND button on the badge at the same time. – If this situation occurs the system now ignores the extra response and does not fail. (DE6054)
Fixed: In some cases when a “Learn a Name” enrollment is created the system does not immediately begin to reference the new enrollment. – This has been fixed so that the system now immediately will be begin using newly created enrollments. (DE6186)
Fixed: Certain situations involving “Learn a Name” can result in corrupted data being returned from the recognition system. – This corrupted data causes the server to fail. This situation has been fixed so that the server now properly handles the bad data. (DE6239)
Fixed: A problem exists when a user in the “Learn commands” sequence skips the last recognition attempt on a command. – This issue can cause the server to fail. The situation is now properly handled by the server. (DE6267)
Fixed: Certain conditions exist which can cause the disk cache used by the recognition engine fail to clean up old content. – The disk cache is now properly emptied every time the server is restarted. (DE6356)