For more information see the
Utilization of Nuance Dual Speech Recognizer: This feature is designed for large customer sites when the number of user exceeds 3000.
When you enable Dual Speech Recognizer for a large site, the chance of voice
recognition delays can be reduced. You can enable this feature during the
Vocera Genie prompts disambiguated users / groups for global sites: The Genie prompts users for clarification when you need to distinguish a person or place from another whose name is similar. For example, the Genie prompts, " Do you mean Shannon Rodriguez in Critical Care?".
The Genie now prompts for identifying phrases at global site and prompts, "Do you
mean Shannon Rodriguez at Washington General?". This feature was only available for
local sites in previous
Support for improved wireless security and roaming: The Badge Property Editor contains new fields that supports the implementation of 802.11 r,k,w on the Vocera B3000n badge.
This section lists the prerequisites needed for
Prerequisites for
In Vocera Voice Server 5.2.2 and later, customers with the Rauland Direct SIP integration require a license key on the Voice Server in order for the Rauland SIP Gateway to properly connect.
Please contact Vocera Technical Support for more information.
The latest version of
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
Reminder for running the Vocera Consoles: Turn Compatibility Mode off in the browser you are using for the Administration Console, the User Console, the Staff Assignment Console, and the Report Server Console.
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.)
SysAutoCheckLogin property in propeties.txt. This server-side feature has been replaced with an automatic login reminder played locally on the badge.
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
B1000a
Dictation
TCP Genie
Client Redirect Utility
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
To upgrade from
Prerequisite: The Windows Operating System where you are installing Vocera Voice Server and any subsequent Vocera localization packs, should be installed with the English (United States) language pack only. Other languages may cause unexpected issues with Vocera software.
The server updates your database and removes any settings for deprecated features.
To perform a new install: Follow the steps in the section of the
The following list contains fixes and improvements made to the
For
French Command Poster is Available. Enhanced: The Vocera Command Poster with the latest 5x Genie commands has been translated into French. Contact Vocera Customer support for more information. (DE14954)
(French only) The Vocera badge is unable to learn names with accented characters. Fixed: You can now proceed with enrollments in French as usual since the badge is able to learn names with accented characters as expected. (DE14945)
Emergency Broadcast Failure. Fixed: When initiating an Emergency Broadcast, group members fail to receive the notification and the Vocera Voice Server fails. (DE15424).
WLAN Profiles. Fixed: Additional WLAN profiles created through the BPE, beyond the default Wireless profile, will not encrypt the credentials for PSK or WEP authentication types. (DE13475)
Transport Layer Security (TLS) support. Fixed: Apache configuration to enable TLS 1.1 and 1.2 is now standard.
Administration Console fails after the server stops and starts . Fixed: Sporadic condition causing the Administration Console to become unavailable after a server stop and start with a "Setting error standby server" error. (DE13655)
Sweep functionality not deleting old messages from the standby server. Fixed: In a cluster the standby node was not properly removing old voice mail messages leading to improper growth of the voice mail folder. (DE14276)
Port scan on standby server causes the server to restart. Fixed: UDP port scan against standby node caused the Vocera application to restart. (DE14060)
Vocera Voice Server failure due to dynamic grammar writing. Fixed: Under certain conditions an error in dynamic grammar writing can cause the server to stop. (DE13282)
Cannot hear a VCS responser's audio (1st attempt) when a broadcast is sent from another VCS device. Fixed: Audio from the first VCS client responding to a broadcast is not heard by the other broadcast recipients. (DE13714 )
Vocera Voice Server fails when using a voice command. Fixed: Rare server failure observed during use of the "add me to multiple groups" voice command. (DE12601)
Vocera Voice Server failover when a VCS user logs out. Fixed: Server failure caused by a VCS user logging out at precisely the same time that an incoming call is presented to the same user. (DE13658)
Vocera Voice Server cannot decrypt an encrypted password or key in profiles.txt. Fixed: Additional WLAN profiles created through the BPE, beyond the default Wireless profile, will not encrypt the credentials for PSK or WEP authentication types. (DE13475)
Vocera Server Telephony Gateway call hold logic fails. Fixed: VSTG properly handles a hold signal sent from a Nortel CS1000 PBX. (DE12816)
Single tap of a call followed by a double tap causes a failover. Fixed: Rare server failure caused by an emergency broadcast call which conflicted with a regular broadcast. (DE12706)
Vocera Voice Server fails during a phone call. Fixed: Server comes down during a failover event caused by unexpected client signaling. (DE12705)
Invalid enrollment file causes recognition failure. Fixed: Under certain conditions an invalid enrollment file is generated by the system. When this occurs, speech recognition for the user stops working, the user hears no response from the Vocera Genie, and an MRCP 407 error shows up in the log. Fixed: The invalid enrollment is now properly detected and automatically corrected. (Defects DE14181 & DE13656)
Protect for null pointer in VMI with extension integration. Fixed: Server failure caused by multiple VMI clients using the same client ID while continuously connecting to the Vocera Voice Server. (DE14310)
Code Blue: Enrollment for a group name not taking precedence during recognition. Enhanced: You can now enter yourself into a Code Blue group with confidence since a new configurable setting can be enable so that disambiguation of recognition results does not occur.
Please contact Vocera Technical Support for more information. (DE14058)
Standby Vocera Voice Server fails when syncing a blank value for a forwarded number. Fixed: A configurable setting added to enable disambiguation of recognition results where one result is a subset of the other. (DE13863)
A time out occurs on the Vocera Voice Server causing a failover. Fixed: This problem was caused by a locked log file which no longer is causing the server exception. (DE12361)
Enter key used in the Search By field caused a logout. Fixed: Using the "Enter" key to search in the Administration console on certain pages triggered a logout. (DE59)
Calls are forwarded before considering call blocking settings. Fixed: Call blocking settings are now being considered before call forwarding logic is applied. (DE3493)
Forwarded calls to off-network members fail. Fixed: When using the "Forward to an Off-Network Group Member" option the call will not be forwarded unless the target group has the appropriate forwarding permission granted. (DE12344)
Syntax error during the ASL log generation in IPv6 Environment. Fixed: You can use periods rather than colons as delimiters. (DE13923)
For Vocera Voice Experience:
(For French Canadian and French Only) Genie fails to recognize accented characters: Fixed: When you train the Genie to learn a name, you are prompted to spell the name. The Genie is unable to interpret accented characters like aigu and grave and continues to repeat with each attempt, "I did not understand". (DE14954)
Recorded names starting with a hard "K" sound often have the initial K sound dropped. Fixed: Recorded names starting with a hard "k" sound may be missing this sound in the recording. (DE12077)
Problem with commands. Fixed: Using 'Learn more commands' to learn a name for "Locate" does not work and the enrollment created for the "Locate" command causes an unexpected recognition failure. (DE10366)
Problem with recorded names starting with a hard "K". Fixed: Recorded names starting with a hard "k" sound may be missing this sound in the recording. (DE12077)
Learn a Name command for users at global sites. Fixed: You no longer need to say to the Genie, “connect to global” before using the Learn a Name feature. (DE54)
Urgent reminders not enunciate. Fixed: Urgent reminders to self where not being enunciated when the user was in a call. (DE9963)
Dead air eliminated when using the Vocera badge. Fixed: The dead air problem occurred because of invalid enrollments which the Vocera Voice Server is now handling without errors or failovers. (DE13656 & DE14181)
The Genie fails to announce the group and caller name. Fixed: The Genie correctly enunciates “accept call" instead of a simple chime. (DE10129)
The Vocera Genie drops the “sh” sound after you record your name. Fixed: When you record a name that contain an “sh” in the beginning of the name, the Genie correctly plays it back without dropping correct pronunciation. This was a problem for recorded names starting with the "sh" sound. For example, the name “Sherman” was played back as “Erman". (DE13669)
For Rauland SIP Gateway:
Unexpected response from Vocera when sending an alert or single message. Fixed: Messages from the Rauland SIP Server which do not require a response (For example, Code Blue) are no longer declined by Vocera eliminating repeated attempts to connect and multiple alerts to the client device or badge.
For Vocera Report Server:
Unable to create scheduled report package with B3000n. Fixed: You can select the B3000n badge type as a filter on a scheduled report. Previously, the selection was not saved. (DE12227)
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 Vocera Voice Server.
Known issues in 5.2.2:
Genie training fails when you have an apostrophe in your name: If the Genie has difficulty understanding your speech, you can train the Genie to recognize the way you say names and commands by using the “Learn xxx” command.
However, if you attempt to train the Genie and you have an apostrophe in your last name, the Genie will fail to learn the name and an error appears in the log file. This problem occurs only after you upgrade to Vocera Voice Server 5.2.2 and you attempt to train the Genie. Note that the leaned names that you added before the upgrade are unaffected. (DE15565)
Workaround: Edit your name in the Vocera User Console and remove the apostrophe. This issues is fixed in a later version of Vocera Voice Server.
Staff Assignment and Administration Server Console Connection Failure: If port 8080 is not open, the Tomcat connector fails to access the Staff Assignment and Administration Server Console rendering them unusable. (DE15472)
Workaround: Ensure that port 8080 is open before using the Staff Assignment and Administration Server Console.
No user in a group can respond to a normal or high alert call: When placing a call to a group with a normal or high alert status, the user is unable to call the sender back and results with the prompt "I'm sorry, no one answered". (DE12547)
Workaround: Only alerts with urgent priority can return calls.
Vocera Server fails to restart after an upgrade: After a successful upgrade, Vocera Voice Server does not start automatically or manually using the system menu. (DE13021)
Workaround: Uninstall the application and manually remove any lingering binary files (see DE12280) before installing 5.2.1.
Text-to-speech playback is incorrect for groups written in all capital letters. Group names using all capital letters resulted in the letters being individually read out by the text-to-speech engine. (DE12922)
Workaround: Spell group names using lowercase letters.
Learned names and commands are not available after an upgrade: You may encounter speech recognitions problems, after an upgrade from Vocera Voice Server 4x to Vocera Voice Server 5x. This problem occurs because of changes to third-party voice recognition software beyond Vocera’s control. (DE14443)
Workaround: If you encounter this issue, use the Learn a Name capability as usual to ensure speech recognition performance.
Speaker Icon fails to play when clicked: In Administration Console under Defaults → Genie Settings, the speaker icons fail to play the greetings and tones as expected. (DE12350)
Workaround: There is no workaround but a fix will be available in a future release.
User can set forwarding target without permissions: The Vocera User Console allows a user to set call forwarding to another user even when the permission has not been granted. (DE12345)
Workaround: Add the appropriate forwarding permission to the target group.
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. (DE8965)
Workaround: There is no workaround but a fix will be available in a future release.
Multiple Choice Response messages fail to be updated on the sender's side: Messages containing Multiple Choice Response (MCR) options from VCS clients or VMP web console, result in sent messages which are not being properly tracked on the sender side failing to be updated when the badge user responds. This situation can occur when the MCR options are too long for the badge to display or if the MCR options contain certain special characters. (DE7741)
Workaround: There is no workaround but a fix will be available in a future release.
Rauland SIP Integration and Vocera Voice Server ~ Alphanumeric values prohibited for VMI ClientID parameter: When modifying rsipproperties.txt file for the RSipVMIClientID parameter, do not use a numeric value or it will cause a failure. This restriction applies to the VMI Class Method for the Vocera Voice Server, sClientID as well. (DE14878)
Workaround: Use alpha character only.
Workaround: This issue will be addressed in a future release.
Workaround: This issue will be addressed in a future release.
Workaround: This issue will be addressed in a future release.
Workaround: Only alerts with urgent priority can return calls.
Workaround: This issue will be addressed in a future release.
Workaround: This issue will be addressed in a future release.