For Vocera Voice Server:

• Care Team Sync reconnect on Voice Cluster failover can lead to a crash condition: Fixed: A race condition can occur when the Care Team Sync server reconnects to the Voice Server during a Cluster failover. The race condition can cause a portion of the server to silently crash which results in cluster sync failure and web console failure. (DE13059)

• Add back multiple 4.x pronunciations of commands: Fixed: The recognition dictionary for common hospital terms was not properly being applied resulting in reduced recognition accuracy of these terms when compared to 4.x. The dictionary is now properly applied. (DE12225)

• Learn a name command causing Vocera Server to fail: Fixed: A rare condition occurs causing the server to restart when a user records an enrollment and the file is not properly created. This condition is now handled properly. (DE12067)

• Urgent call enrollment not working: Fixed: If a user had learned a command enrollment for "Urgent Call" it was not properly being referenced. (DE12362)

• Administration Console logs out when wrong location is searched: Fixed: Searching in the Administration Console for an invalid entity could cause the Administration Console to log out. This has been resolved. (DE12290)

• SpokenGroupName is empty leading to MRCP Exception 407: Fixed: Recognition fails in a new site where the Everyone group has been set as "permission only" and all other groups in the site are empty. This condition is now properly handled. (DE11772)

• Script Error is prompted when accessing the tracking date calendar: Fixed: In Administration Console on the Devices Tab, you’ll receive a Java script error message which includes an option to continue running the Java script. This error massage will not affect the functionality of the User Interface. (DE10860)

• Message response grammar does not adhere to the threshold configured in speechparms.xml: Fixed: The confirmation threshold was incorrectly set higher than expected resulting in users frequently hearing "I think you said" confirmation prompts. The value has been adjusted. (DE12047)

• Java script error on the Devices tab in the Administration Console: Fixed: 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: Fixed: 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)

For the Badge Configuration Utility:

• The Badge Configuration Utility (BCU) does not successfully install from the Vocera Installer: Fixed: The Vocera Server Installer (VoceraSuiteInstaller.exe) fails to complete the BCU Installation. (DE10598)

  The workaround is to run the BCU.exe file included in the \VoceraSuite\{2602B985-683B-4A02-9733-A2DB45FD423C}\ folder in the install media or contact Technical Support for a standalone BCU.

For Vocera Report Server:

• The report header shows an incorrect date format for non-US locales: Fixed: Vocera Reports Server reports with Canadian locales show date header in yy-mm-dd format. This has been corrected. (DE11311)

• System Call Volume Trend report has incorrect label on y-axis: Fixed: The System Call Volume Trend report graph incorrectly displayed a label of "Call Duration" instead of "Number of Calls" on the Y-Axis. This has been corrected. (DE11085)

• Tomcat failure when that site is selected in the Report Scheduler: Fixed: If an apostrophe is used in a site name then selecting that site in the VRS Report Scheduler would cause an error. This condition is now properly handled. (DE10189)

For Vocera Communication Suite:

• Tomcat memory leak on the standby server when VCS clients connect to the cometservice: Fixed: Memory leak can lead to tomcat outage on standby server – The condition leading to the memory leak is now properly handled. (DE11384)

For Vocera SIP Telephony Gateway:

• VSTG SIP route header corrupt in CANCEL when SIP transport is TCP: Fixed: 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 could result in the call continuing to ring on the Avaya side. (DE10272)

• Deadlock occurs during SendDTMF and StopAudio conditions: Fixed: When DTMF digits are being sent through the VSTG a deadlock condition happens which causes the VSTG to stop processing calls. This condition has been resolved. (DE12477)

The following list provides information about known product issues in the Voice Server.

Known issues in 5.2.1:

• Vocera Server fails to restart after an upgrade: After a successful upgrade, 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.

• 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.

• Forwarded call fails to reach the target: 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)

  Workaround: There is no workaround but a fix will be available in a future release.

• Unable to create scheduled report package with B3000n: Selecting the B3000n badge type as a filter on a scheduled report fails to save the selection. (DE12227)

  Workaround: There is no workaround but a fix will be available in a future release.

• Problem with recorded names starting with a hard "K": Recorded names starting with a hard "k" sound may be missing this sound in the recording. (DE12077)

  Workaround: There is no workaround but a fix will be available in a future release.

• VMI Broadcast multicast packets problem: When the VMI Broadcast setting is enabled, the TTL on the multicast packet sent by the Vocera Voice Server is set to 1. This issue is found in Vocera Server 5.1 and 5.2..x  (DE11884)

  Workaround: Disable the VMIBroadcast feature to use the optimized large group VMI behavior.

• (For the French local only) Restore from a backup fails: During a database restore operation, the progress dialog box doesn't properly update the status and at 0% the message "Le serveur est demarre" is displayed even though server is up and active. (DE11853) 

  Workaround: Close and reopen the dialog box.

• 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.

• Problem with searches for users: In the Administration Console, searches for users with spaces in the User ID field will fail. (DE10846)

  Workaround: There is no workaround but a fix will be available in a future release.

• Problem with commands: 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)

  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.

• Message failure when calls are accepted on a Vocera badge and VCS client: If a user is active in a call and then accepts a Rauland SIP Integration message, the Rauland call is not connected. (DE12546)

  Workaround: Disconnect the current call before accepting the Rauland SIP integration call.

The following list provides information about known product issues in the Vocera Rauland SIP Gateway.

Known issues in 5.2.1:

• The Rauland SIP Gateway is not freeing up the channels when it hits the max allowed: The Rauland SIP Gateway does not clean up calls if the Rauland SIP Server stops responding. The expected behavior is that any sessions that is not handled within the timeout period should be released and made available for the next request. (DE12528)

  Workaround: Restart the RSIP Gateway Server to clear the abandoned calls.

• RSIP client unable to receive a message even when configured to breakthrough: When a Rauland SIP integration alarm is configured to breakthrough a DND, the receiving user will not be able to connect the call due to the user's device being set to DND. (DE12778)