The
With the intelligence of the
In addition, the
Use this document in conjunction with the following:
The following third-party software versions are included in this release:
Third-party Software | Versions |
---|---|
Apache HTTP |
httpd 2.4.6 x86_64 |
Glassfish |
extension-glassfish 5.1.0 |
Java |
java-1.8.0-openjdk 1.8.0.292.b10-1 |
PJSIP |
PJSIP version 2.7.2 |
PostgreSQL |
postgresql 13.4 |
Red Hat Enterprise Linux Server release 7.9 (Maipo) |
Kernel: 3.10.0-1160.42.2.el7.x86_64 |
The following third-party software versions are included in this release:
Vocera Device | Firmware Build Number |
---|---|
V5000 |
5.1.6.23 |
C1000 | 1.2.296 |
B3000n |
4.3.4.12 |
This section summarizes the new features in this release.
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This is a maintence release and includes no new enhancements to the
This release includes enhancements to several components of the
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.Using a Vocera Device with Smartphone Apps
This allows a user the ability to use a Vocera smartbadge/minibadge/badge with the Vina client. In this configuration, the user's primary device becomes their smartbadge/badge so that they can be hands free while still receiving all audible notifications on the badge.Enhanced Voice Improvements and New Intents
Enhanced Voice improvements including the following new intents:The following list contains fixes and improvements made to the
The following list includes the defects fixed in this version of the
XMPP-1284 Mass alerts are now sent to all B3000N badge recipients even if the first badge recipient in the list is off network. The XMPP gateway no longer waits for the first badge recipient to be on network before sending the mass alert.
The following list includes the defects fixed in this version of the
CRVC-24151 Pushkit notifications are now delivered to Vina when the caller initiates a console call and their Vina client was sent to the background 5-20 seconds prior.
XMPP-1279 The XMPP adapter can now suppress the Apple Push Notification service (APNs) when an iOS device is off-network. In the adapter configuration, select the new Suppress Off-Network Notifications checkbox to suppress all APNs messages to off-network devices. This feature is recommended for sites without an XMPP proxy, because it simulates the behavior of notifications being suppressed when devices are not connected to the site's network.
VCXP-16591 Certain situations caused the
The following list includes the defects fixed in this version of the
CRVC-24096
Vina call initiation from Vina Web was failing on iOs devices when app is in the background.
The following list includes the defects fixed in this version of the
XMPP-1257
XMPP now correctly sends re-alert notifications to iOS users when re-alert is enabled on the rule. Previously the re-alert functionality was not working for iOS users if the initial notification was received when the Vina app was in the background.
The following list includes the defects fixed in this version of the
CRVC-23886
The Presence service could fail to mark off network users unavailable for voice calls causing off network users to be included in group calls.
XMPP-1020
XMPP no longer fails to start if there are devices registered to inactive or removed users.
XMPP-1181
XMPP now removes invalid device registrations in the database when a user logs into a device.
XMPP-1236
XMPP has a Disabled Nested Results in Group Directory Search policy that revokes the display of nested users and groups.
XMPP-1248
XMPP now correctly tracks iOS device registration after a restart. Previously, the adapter might fail to clear registration and keep the user logged in to multiple devices. The adapter would log the user out of one device automatically.
The following list includes the defects fixed in this version of the
PFM-17368
The gold image for 6.5 had incorrect referential integrity for foreign keys that represent dataset keys.
PFM-17384
Data purge issue caused by Not Null Foreign Keys that did not cascade in the gold image.
The following list includes the defects fixed in this version of the
XMPP-1036
Restoring a patient linked conversation where the user who first made the association of the patient is inactive was causing inconsistent notifications.
The following list includes the defects fixed in this version of the
CRVC-23493
The Voice server wasn't sending any logged in events for Vina devices.
PFM-17207
Removal of groups within a group from a different facility did not display Parent Group after group removal.
XMPP-342
Recipient did not receive messages that were sent while recipient was off network.
XMPP-1000
Bookmark was unarchived for caller when callee logs into B3000N.
XMPP-1172
Ghost notifications were being sent to iOS devices that are meant for other recipients.
The following list includes the defects fixed in this version of the
XMPP-1104
Purged conversations without read receipts left a null conversation link in Messages.
CRVC-22953
VS crashed with exception when V5 call on hold gets dropped after receiving alert.
CRVC-22751
Voice was failing over 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
SIV-9115
The group call timeout was erroneously set to less than the 50 second default.
The default Postgres setting has been updated to 60 seconds for both the Core and Audit databases.
The following list includes the defects fixed in this version of the
XMPP-981
APNs message for an invite to a patient linked conversation during a call was sent to the callee, who was already assigned to that patient. The APNS message is now suppressed.
XMPP-976
When receiving a call a banner on the home screen
appeared that read
The voice server could failover while in dual mode and a group conference call.
While using both a B3000N and a Vina device, and the B3000N went offline, the accept/decline call windows were missing on the iOs Vina device.
OT-2379
Non-US customer was able to download files in Operational Tools.
OT-2391
User was unable to open a new Remote Support session
after
The following list includes the defects fixed in this version of the
XMPP-741
When a user forwarded a call, the call would forward correctly but the updates were sent to the wrong user.
While inside a multi-user chat that included 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.
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.
If a user was attempting to send a message via the web messaging panel, the Send button was obscured. This has been corrected.
The Web UI appeared to add users to coversations when the user was added to Mass Alerts, but the user was not actually added. This has been corrected.
The sub pages of the Workflows were not displayed alphabetically. They have been moved to appear alphabetically.
If a user only had Console system
management allowed permissions, they could
not see the
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.
There was a defect when a user would set a reminder between 12:01am and 12:59am, the reminder would default to PM.
The system was enunciating numbers incorrectly. For example, if the system was enunciating "25" it would say "Two, Five".
SIV-8923
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.
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.
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.
There was the potential for a MySQL failure and partial user data was not migrated when performing a partial 5x to 6x migration.
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.
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.
VSTG could crash in rare instances when the VSTG log file would roll over.
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.
VSTG could crash if a call to a user was being forwarded and the caller canceled the call.
Voice and system automated backups were not running appropriately in every case.
The VSTG adapter would crash with a segmentation fault. This has been corrected.
When a user would call in via VSTG and used call blocking, the call would not go through.
XMPP failed to start up when restarting Glassfish and required a reboot of the server. XMPP now starts up when restarting Glassfish.
When a user was removed from a conference group, the user still appeared in the Conference Group.
The Jenkins Appliance set up job was using the incorrect garbage collector. It is now using the G1 garbage collector.
There was an error in PostGres that caused the Vina client and console to go crash.
There were corner cases where the connection pool stats were not being read by the Prometheus text file collector.
Restoring a database backup changed the ownership of the backup folder and prevented the user from taking another backup.
When upgrading to Platform 6.4 the autoscaler files were missing and prevented a successful upgrade.
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.
When a user is set to Do Not Disturb, (DND), the calls are not being forwarded; instead the caller is given voice mail.
Duplicate menu items were appearing on clustered appliances in some instances.
When running a failover, there was a potential that a service or an adapter may not restart.
The dataset link name of the reverse link
between Alerts and To was updated to
This section contains a list of known product issues and limitations in the
Version introduced: Vocera Platform 6.0
Workaround: Contact Vocera Technical Support to delete the facility directly from the database.
Version introduced: Vocera Platform 6.0
Workaround: Delete the original username, save the user profile, and then update the username back to the original.
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.
Version introduced: Vocera Platform 6.0
Workaround: Stop the audit Postgres service, start glassfish, and repair the cluster.
Version introduced: Vocera Platform 6.3
Workaround: Failover to the standby node and restart the old active node.
Version introduced: Vocera Platform 5.5
Workaround: Stop Postgres on the node to trigger a failover to avoid data loss.
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.
Version introduced: Vocera Platform 6.0
Workaround: Adjust the maximum allowed Apache threads.
Version introduced: Vocera Platform 6.0
Workaround: None.
Version introduced: Vocera Platform 6.0
Workaround: Try to merge the call again.
Version introduced: Vocera Platform 4.x
Workaround: Answer the prompt in the middle of the sequence, and the prompt is automatically repeated.
Version introduced: Not applicable (N/A).
Workaround: Restart the Telephony Gateway.
Version introduced: Vocera Platform 6.4
Workaround: Use the alternative command “send reminder.”
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.
Version introduced: Vocera Platform 6.4
Workaround: None.
Version introduced: Vocera Platform 6.4
Workaround: Add and remove yourself from groups using Vina Mobile.
Version introduced: Vocera Platform 6.4
Workaround: Search for the department group and open it from the search results.
Version introduced: Vocera Platform 6.4
Workaround: Refresh the browser or navigate to another area of the web console and navigate back to messaging.
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.
Version introduced: Vocera Platform 6.3
Workaround: None.Version introduced: Vocera Platform 6.0
Workaround: Restart XMPP to rebuild the XMPP cache to create the missing identities.
Version introduced: Vocera Platform 6.0
Workaround: None.