Vocera Communications System Release Notes

Vocera Voice Server Enhanced Voice

Release Date: December 2023

Updated: May 21, 2024

New and Enhanced Features

The Vocera Voice Server 5.10.x platform has new features and enhancements.

This section summarizes prominent features and functionality for each release.

New and Enhanced Features in 5.10.0.316

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

Fixed Issues

The following list contains fixes and improvements made to the Vocera Voice Server Enhanced Voice.

Fixed Issues in Suki-platform 1.7

Deployed on March 21, 2024

  • VOCERASUKI-387 Member singular name and Member plural name fields are not being used for recognition.

  • VOCERASUKI-384, VOCERASUKI-360 Identical group or addressbook entry names in the global site and the current site may not always disambiguate properly.

  • VOCERASUKI-349 Long recognition delay during periods of high activity related to group membership changes can result in recognition delays or the user hearing “system unavailable.”

  • VOCERASUKI-378 “Call” is being misrecognized as similar sounding names.

Fixed Issues in Suki-platform 1.6

Deployed on March 7, 2024

  • Poor recognition for group names in the following categories:
    • VOCERASUKI-334 Group names containing acronyms such as PICU and NICU.

    • VOCERASUKI-347, VOCERASUKI-353 Group names containing acronyms with trailing numbers like NICU CS.

    • VOCERASUKI-335 Groups containing "test broadcast" - misrecognized as the broadcast intent.

    • VOCERASUKI-343, VOCERASUKI-344, VOCERASUKI-351, VOCERASUKI-374 Group names containing numbers.

    • VOCERASUKI-361 Group names which sound like two words such as Biomed and Microbiology.

    • VOCERASUKI-385 Groups with names similar to other group ASN's - "Surgery" vs. "O R" (with ASN "Surgery").

    • VOCERASUKI-364 Groups containing "transfer" (ICU Patient Transfers) - misrecognized as the transfer intent.

    • VOCERASUKI-365 Group names containing multiple consecutive ‘1’s.

    • VOCERASUKI-354 Groups with zero in the middle when the user says "oh" instead of "zero."

    • VOCERASUKI-341 Groups with similar name variations - F Pod Occupational Therapy vs. E Pod Occupational Therapy.

  • VOCERASUKI-346 Poor recognition for specific user names.
  • VOCERASUKI-357, VOCERASUKI-375 Poor recognition for some site names including those with acronyms.

  • VOCERASUKI-342 Poor recognition on guest access for group names with numbers.

  • VOCERASUKI-377 Forward to extension command not consistently recognizing the number.

  • VOCERASUKI - 369 "Broadcast to group" intent is incorrectly matching user names instead of groups.

Fixed Issues in Enhanced Voice

There are no new Enhanced Voice related fixes in this release.

Known Issues

A few issues are known to exist in the Vocera Voice Server Enhanced Voice and this section summarizes all the known issues in the release.

Known Issues in the Vocera Voice Server Enhanced Voice

This section summarizes known product defects and limitations, including any workarounds we may have, for the Vocera Voice Server Enhanced Voice.

  • VCXP-16694 The updated value of the outside buddy's first name is not inserted into the Suki DB during reconciliation.
  • VCXP-17072 When a user and a group have similar-sounding names, and the user calls a group, although Suki returns the group as part of the response, the group is ranked lower than the user. Since only three results are presented to the user, the group is not visible to the user when there are items with a higher ranking.
  • VCXP-17332 Partial intent is broken for the 'Send a reminder' command.
  • VCXP-17348 Bluetooth command recognition is poor.
  • VCXP-17355 Some of the Yes/No utterances result in no Intent Response.
  • VCXP-17786 Sending a reminder at noon or midnight does not work.
  • VCXP-17867 Suki misrecognizes user names(with numbers) in SoS environment.
  • VCXP-17870 The conference command is being recognized as the stop forwarding command.
  • VCXP-17891 The Santa Claus command (Easter egg) results in genie change.
  • VCXP-17892 The Call Caption Kirk command (Easter egg) sometimes is being recognized as the call command.
  • VCXP-17901 Forward Intent: Partial forward to an entity is broken.
  • VCXP-17903 If an ordinary group is converted to a department, users are no longer available for recognition.
  • VCXP-17904 Some users were not available for recognition even after five hours in the production environment.
  • VCXP-17905 The urgent broadcast command yields varying slot accuracy for two groups with the same name.
  • VCXP-17906 The delete voice messages command not returning the slot TEXT.

Known issues - SUKI

  • Poor recognition for group names in the following categories

    • VOCERASUKI-373 Specific groups - F Pod, Main OR 1, IHMS, CVICU HUC, CVICU West Swat.

    • VOCERASUKI-386 Group names containing the word "and" - (One and Two East).

    • VOCERASUKI-391 Group names containing the keyword "extension" - misrecognized as the "dial extension" intent –

    • VOCERASUKI-383 Spelled-out group names.

    • VOCERASUKI-396, VOCERASUKI-355 Group names containing numbers starting with 1 (Room 1846 Nurse).

    • VOCERASUKI-399 Group names containing “Two” or 2 being confused with “to” –

    • VOCERASUKI-398 Group names containing “First.”

    • VOCERASUKI-389, VOCERASUKI-390 Groups with zero at the beginning or end of a digit sequence (11110 or 08) when the user says "oh" instead of "zero."

  • VOCERASUKI-388 User Identifying phrase and the Dr. prefix option are not being used for recognition.

  • VOCERASUKI-394 Schedule Code lavender does not work with relative time (in 5 minutes).

    • Workaround: Use partial intent "Schedule Code Lavender" then state timeframe when prompted 

  • VOCERASUKI-367 “Remove user from group” is misrecognized as “Delete Message."

  • VOCERASUKI-408 Misrecognition of phone numbers can occur when compound numbers are misrecognized as part of the longer digit string – for example “seventy one” can be misrecognized as “seventy” and “one” resulting in a result of 701.

  • VOCERASUKI-404 Users with “NULL” as their first or last name fail to sync to the recognition database resulting in those users not being callable.