This is a maintence release and includes no new enhancements to the Vocera Platform.

This is a maintence release and includes no new enhancements to the Vocera Platform.

This is a maintence release and includes no new enhancements to the Vocera Platform.

This release includes enhancements to several components of the Vocera Platform.

• Data Purge Redesign

  Vocera has redesigned our Data Purge functionality. We have decoupled the purge function from the backup process, ensured that the purge functionality does not create an unreasonable load level on the platform server, and ensured that the purge can keep up and/or catch up with data creation rates.

• Azure Maintenance Event Support

  Vocera Enterprise can recover from Azure Maintenance Events including failing over when necessary and can auto recover failed nodes in order to prepare for another maintenance activity.

• Dual Mode Availability

  We are pleased to announce the availability of Dual Mode. This allows a user the ability to log into a badge and Vina simultaneously.

• Enhanced Voice Improvements and New Intents

  Enhanced Voice improvements including the following new intents:
  • Who is in group?
  • Ability to send reminders. (Note: sending a recurring reminder is not yet supported in Enhanced Voice).
  • Start Break
  • End Break
  • End Shift
  • Change Genie
  • Play test tone
  • Assign Location
  • Call screening
  • Cancel feature
  • AP Tour
  • Erase Voice PIN
  • Start/Delete Code Lavender
  • Play Mindfulness
  • Login
  • Surprise Easter Eggs

The following list includes the defects fixed in this version of the Vocera Platform.

• XMPP-1104, CASE-2974

  Purged conversations without read receipts leave a null conversation link in Messages.

• CRVC-22953, CASE-2921

  VS crashes with exception when V5 call on hold gets dropped after receiving alert.

• CRVC-22751, CASE-2808

  Voice failover due to NPE while calling another user and receiving an incoming urgent alert with response options.

The following list includes the defects fixed in this version of the Vocera Platform.

• SIV-9115 SIV-5507 CASE-2799

  The group call timeout was erroneously set to less than the 50 second default.

• PFM-16272 PFM-16023 CASE-2838 CASE-2897

  The default Postgres setting has been updated to 60 seconds for both the Core and Audit databases.

• OT-2379

  Non-US customer is able to download files in Operational Tools.

• OT-2391

  Agent: Not able to open Remote Support after Agent Connection Service restart in Operational Tools.

The following list includes the defects fixed in this version of the Vocera Platform.

• XMPP-981 XMPP-1010 CASE-2738

  When a group call was initiated, the receiver of the call would receive a banner that read "Incoming Message" while the phone was ringing.

• XMPP-976 XMPP-1010 CASE-2738

  When a group call was ended, an Apple Pushkit Notification (APN) was sent.

• SIV-9033

  The voice server could failover while in dual mode and a group conference call.

• SIV-9034

  While using iOS Vina in dual mode, with a B3N while that B3N is offline, the accept/decline call windows were missing.

• OT-2379

  Non-US customer is able to download files in Operational Tools.

• OT-2391

  Agent: Not able to open Remote Support after Agent Connection Service restart in Operational Tools.

The following list includes the defects fixed in this version of the Vocera Platform.

• XMPP-741 CASE-2518

  When a user forwarded a call, the call would forward correctly, but the updates were sent to the wrong user.

• XMPP-486

  While inside a multi-user chat that includes a legacy badge, a null pointer exception was displayed when a user attempted to send an image. Now, the legacy badge holder will receive a message stating that the media message is unavailable.

• XMPP-23

  While logging in, there were instances where the logout would fail, but cause memory leaks that can slow down the system. The memory leak has been patched and failed logouts are now being treated as logouts in memory management.

• CASE-2567 WEB-12430 WEB-12346

  If a user was attempting to send a message via the web messaging panel, the Send button was obscured. This has been corrected.

• WEB-12011

  When a user added others to Mass Alerts, the UI appeared to add them to the conversation, however the user was not added. This has been corrected.

• WEB-11814 WEB-9499 WEB-7707

  The sub pages of the Workflows were not displayed alphabetically. They have been moved to appear alphabetically.

• WEB-11771 WEB-11768

  If a user only had Console system management allowed permissions, they could not see the Device Monitor menu.

• CASE-2605 VCXP-15193

  The Voice Server would crash on logout if any deactivated user was in the list of inner circle users. We have added a check to look for, and remove, any deactivated users.

• VCXP-14914

  There was a defect when a user would set a reminder between 12:01am and 12:59am, the reminder would default to PM.

• CASE-2546 VCXP-14882 VCXP-12104

  The system was enunciating numbers incorrectly. For example, if the system was enunciating "25" it would say "Two, Five".

• SIV-8923 SIV-4313

  If a user was the only person in a group and was set to Do Not Disturb, (DND), a user with VIP credentials could not break through.

• SIV-8922 SIV-4313

  If a user was the only person in a group, and forwarded their calls to a covering user, the covering user would not receive calls after the initial requester logged out.

• CASE-2530 SIV-8630

  When a user placed a call and put the recipient on hold, there were instances when the Voice server would get into a bad state and report that the call was already on hold.

• SIV-8415 SIV-6527

  When performing a partial 5x to 6x migration, there was the potential for a MySQL failure and partial user data was not migrated.

• CASE-2429 SIV-8248 SIV-8145 PFM-14203 SIV-8242

  The telephony adapter was missing a heartbeat and restarting VSTG. This was due to the Glassfish garbage collecting process running overlapping jobs and taking up resources. In turn, the heartbeat would not be reported back in 10 seconds and caused VSTG to restart.

• CASE-2413 CASE-2548 CASE-2577 SIV-8820 SIV-8240

  The Voice server was allowing a user to log into Vina after that user was already logged into Vina. This caused the Voice server to get into a bad state and potentially crash.

• SIV-8233

  In rare instances, when the VSTG log file would roll over, VSTG could crash.

• SIV-8230 SIV-8387 SIV-8232 SIV-8169 SIV-6011 SIV-8228

  In rare instances when the load on VSTG was extraordinarily high, there were call leaks in VSTG that would result in active VGW calls to be maxed out.

• SIV-8184 CASE-2406 CASE-2428

  VSTG could crash if a call to a user was being forwarded and the caller canceled the call.

• PFM-16507 CASE-2531 CASE-2384 SIV-8136 SIV-8434 SIV-8222

  Voice and system automated backups were not running appropriately in every case.

• SIV-8107 CASE 2532 SIV-8242

  The VSTG adapter would crash with a segmentation fault. This has been corrected.

• SIV-8101 CASE-2359

  When a user would call in via VSTG and used call blocking, the call would not go through.

• CASE-2631 PFM-16766

  XMPP failed to start up when restarting Glassfish and required a reboot of the server. XMPP now starts up when restarting Glassfish.

• PFM-16763 PFM-14909 SIV-8899

  When a user was removed from a conference group, the user still appeared in the Conference Group.

• PFM-16655 PFM-16663 PFM-15296

  The Jenkins Appliance set up job was using the incorrect garbage collector. It is now using the G1 garbage collector.

• CASE-2576 PFM-16629

  There was an error in PostGres that caused the Vina client and console to go crash.

• RE-1634 PFM-16565

  There were corner cases where the connection pool stats were not being read by the Prometheus text file collector.

• PFM-16507 SIV-8222 PFM-11266

  Restoring a database backup changed the ownership of the backup folder and prevented the user from taking another backup.

• CASE-2653 PFM-15805

  When upgrading to Platform 6.4 the autoscaler files were missing and prevented a successful upgrade.

• CASE-2273 PFM-15777 PFM-13848 PFM-15503 PFM-13848

  Dates received from third party sources, such as HL7, were incorrectly stored as a day early in the database. This only effected customers who are ahead of the UTC time zone.

• CASE-1881 CASE-1891 CRCV-16830 SIV-2333 SIV-6670 CRVC-1905

  When a user is set to Do Not Disturb, (DND), the calls are not being forwarded; instead the caller is given voice mail.

• PFM-14624 PFM-14581 PFM-15000

  In some instances, duplicate menu items were appearing on clustered appliances.

• PFM-16111

  When running a failover, there was a potential that a service or an adapter may not restart.

• ADP-10410

  The datalink name of the reverse link between Alerts and To was updated to recipient_alerts.

Platform Issues

• CRVC-22751 Voice failover occuring due to NPE while calling another user and receiving an incoming urgent alert with response options.

  Version introduced: Vocera Platform 6.3.4

  Workaround: None.

• CRVC-22953 The Voice Server crashes with exception when a V5000 call on hold gets dropped after receiving an alert.

  Version introduced: Vocera Platform 6.4

  Workaround: None.

• CRVC-23493 Presence receives a legacy login event for Vina device.

  Version introduced: Vocera Platform 6.4

  Workaround: None.

• PFM-11104 On Vocera Platform Web Console, deleting a facility with user history may partially delete the facility.

  Version introduced: Vocera Platform 6.0

  Workaround: Contact Vocera Technical Support to delete the facility directly from the database.

• PFM-11115 On the Vocera Platform Administrative Console, deleting users with extensive data history impacts the system’s performance.

  Version introduced: Vocera Platform 6.0

  Workaround: Deactivate users, enable data purge to reduce performance impact, and only delete users that have been inactivated for 90 days.

• PFM-11915 On the Vocera Platform Administrative Console, the system displays an error if a username is changed and changed back to the original username.

  Version introduced: Vocera Platform 6.0

  Workaround: Delete the original username, save the user profile, and then update the username back to the original.

• PFM-14641 Adapters services may fail to deploy during platform version upgrades that include multiple services.

  Version introduced: Vocera Platform 5.5

  Workaround: After upgrading the platform version, restart the upgraded node. If services fail to activate, restart the glassfish system service.

• PFM-15277 During a cluster failover, the audit database may be left in an activating state on the failed node, preventing a recovery.

  Version introduced: Vocera Platform 6.0

  Workaround: Stop the audit Postgres service, start glassfish, and repair the cluster.

• PFM-15632 During split-brain and upgrades, the active node in the cluster stops processing messages on some queues after a failover.

  Version introduced: Vocera Platform 6.3

  Workaround: Failover to the standby node and restart the old active node.

• PFM-16102 When a node is manually disabled to trigger a failover, the disabled node can continue to process messages that are not replicated to the new active node.

  Version introduced: Vocera Platform 5.5

  Workaround: Stop Postgres on the node to trigger a failover to avoid data loss.
• PFM-16173 Performing audit searches using a single term in the default 24-hour search field intermittently takes a few minutes for the search to complete.

  Version introduced: Vocera Platform 6.0

  Workaround: Change the audit page size to 300, add additional search items, and narrow the search with a top and bottom date range.

• PFM-16830 When over 200 users use Vina Web or Staff Assignment simultaneously, the system gets sluggish, and messaging services may disconnect and reconnect.

  Version introduced: Vocera Platform 6.0

  Workaround: Adjust the maximum allowed Apache threads.

• PFM-17207 Removal of groups within a group from a different facility does not display Parent Group after group removal.

  Version introduced: Vocera Platform 6.2

  Workaround: None.

• SIV-8124 If you turn off the “Announce through Speaker” option on your Smartbadge, an urgent message with no response options through the speaker is enunciated.

  Version introduced: Vocera Platform 6.0

  Workaround: None

• SIV-8243On Smartbadge and Vina app, when you attempt to merge an active call with the call on hold, the merge action may fail intermittently if the first call receiver gets another incoming call.

  Version introduced: Vocera Platform 6.0

  Workaround: Try to merge the call again.

• SIV-8269 If you initiate a call using the Vina Web Console or Staff Assignment, you might only hear a part of the “Please press the star key” prompt.

  Version introduced: Vocera Platform 4.x

  Workaround: Answer the prompt in the middle of the sequence, and the prompt is automatically repeated.
• SIV-8809 Under certain conditions, when all the available Telephony Gateway lines are in use, one line may fail to release when the call is disconnected, resulting in fewer lines being available to service future calls.

  Version introduced: n/a

  Workaround: Restart the Telephony Gateway.
• VCXP-14987 When the Beta enhanced voice feature is enabled, using the command “send reminder to myself” may not be recognized.

  Version introduced: Vocera Platform 6.4

  Workaround: Use the alternative command “send reminder.”
• VCXP-15100 When the beta enhanced voice feature is enabled, the genie does not recognize the user response of a Smartbadge or Minibadge when you use special characters in a Multiple Choice Response (MCR.).

  Version introduced: Vocera Platform 6.0

  Workaround: Select the response from the device screen for Smartbadges and use the button option on the Minibadge instead of voice response.
• VCXP-15225 When the beta enhanced voice feature is enabled, a page sent to a contact may not recognize the contact.

  Version introduced: Vocera Platform 6.4

  Workaround: None
• WEB-12361 You may not be able to add yourself to groups using “My Profile” in the Vocera Web Administrative console.

  Version introduced: Vocera Platform 6.4

  Workaround: Add and remove yourself from groups using Vina Mobile.
• WEB-12687 When you navigate to the Vina Home Department and start a new chat or a call, you cannot search nested groups.

  Version introduced: Vocera Platform 6.4

  Workaround: Search for the department group and open it from the search results.

• XMPP-342 Recipient might not receive messages that were sent while recipient is off network.

  Version introduced: Vocera Platform 6.4

  Workaround: None.
• XMPP-1000 Bookmark unarchives for caller when callee logs into B3000N.

  Version introduced: Vocera Platform 6.4

  Workaround: None.
• XMPP-1104 Purged conversations without read receipts leave a null conversation link in Messages.

  Version introduced: Vocera Platform 6.5

  Workaround: Disable purge on the Conversations dataset after upgrading to 6.5. Contact Technical Support for help.
• XMPP-1172 Ghost notifications can be sent to iOS devices that are meant for other recipients.

  Version introduced: Vocera Platform 6.4

  Workaround: None.
• XMPP-24 When the XMPP messaging service encounter SQL errors in queries for large numbers of assignments, additional queries may fail.

  Version introduced: Vocera Platform 6.0

  Workaround: Use the Data Purging feature to remove old assignments. You can also contact Vocera Technical support to run a script that clears the connection pool when the following error occurs: asadmin flush-connection-pool xmppCachePool.
• XMPP-32 The Smartbadge and Vina app report missed calls as declined calls when a second call comes in while the first call is ringing.

  Version introduced: Vocera Platform 6.3

  Workaround: None
• XMPP-474 On Vocera Platform 6.3.3, XMPP identity creation may not be completed by a standby node that takes over due to a failover of an active node in vSphere. Data acknowledged but not processed by XMPP is lost during the failover.

  Version introduced: Vocera Platform 6.0

  Workaround: Restart XMPP to rebuild the XMPP cache to create the missing identities.

• XMPP-2715 On Smartbadge and Vina app, call logs are not reported if you forward calls to an external number.

  Version introduced: Vocera Platform 6.0

  Workaround: None