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.21 |
| C1000 | 1.2.284 |
|
B3000n |
4.3.3.18 |
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 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.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:The following list contains fixes and improvements made to the
The following list includes the defects fixed in this version of the
SIV-9115 SIV-5507 CASE-2799
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.
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
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.
The voice server could failover while in dual mode and a group conference call.
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
XMPP-741 CASE-2518
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 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.
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.
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.
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 Device Monitor menu.
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 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.
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.
When performing a partial 5x to 6x migration, there was the potential for a MySQL failure and partial user data was not migrated.
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.
In rare instances, when the VSTG log file would roll over, VSTG could crash.
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.
In some instances, duplicate menu items were appearing on clustered appliances.
When running a failover, there was a potential that a service or an adapter may not restart.
The datalink name of the reverse link between Alerts and To was updated to recipient_alerts.
This section contains a list of known product issues and limitations in the
When using Enhanced Voice Permission with Suki, sending a Page via voice does not always work as intended.
When using Enhanced Voice Permission with Suki, sending a Page to an outside telephone number via voice does not always work as intended.
There is an issue with the Genie voice. When the female persona is selected, the male persona voice is used.
If a user is attempting to send a page via a voice prompt, the page will not be recognized and sent. This is for both internal and external telephone numbers.
The Genie will not respond to voice responses if the MCR alert has special characters included.
Reminders sent to self/myself are not being delivered.
On B3N devices, once an alert is escalated and completed, the alert remains on the device.
Deleting a user from the web UI is possible, even if that user has message activity already recorded.
A conversation will remain unread if the only message in the conversation is an unread, played, and deleted voicemail.
Creating a user with the same login as a deleted user results in presence issues. These issues appear to exist for both the badge and the Vina client.
When a user is created with the same login as a previously deleted user, they can successfully log in to Vina on iOS but are forcefully logged out after about 10 seconds. This only appears in the iOS version of Vina.
XMPP is storing a blank subject when no subject is sent and causing conversations with no messages to be returned in bookmarks.
Administrators and moderators of mass alerts are not granted their affiliations when the XMPP adapter is restarted.
There are registration issues with recreated users. When logging in with a user that shares a login (and thus a UID) with a deleted user, neither the device nor the XMPP identity become registered in engage.devices as expected.
Voicemail status should be changed to ‘Replay Voicemail’ once the user plays the voicemail, but it remains ‘New Message’ in Android and iOS.
Data that has been acknowledged but not yet processed by XMPP is lost on failover.
Facility and Unit Name is not updated in the Vina App after renaming it in Vina/Gen5.
Incoming calls are reported as a declined call when another incoming call is ringing at the same time.
The XMPP cache connection pool can get into a bad state for a prolonged period of time. There is an internal workaround to watch for and mitigate this issue for clients.
While using Vina, calls are not logged if the user is forwarding calls to an external number.
When starting a new chat or call in Vina Web, you cannot search users and nested groups after navigating to the home department group.
Users are not able to add themselves as a member of a second group, when the permission is set to "Group of users permitted to add or remove themselves from this group".
Importing Assignment Roles to Groups gets stuck at the 50% completion mark.
When the appliance runs out of Apache threads, the system can slow down and become sluggish for users.
The system is unable to immediately add or delete a member when there are mass group members.
Canceling or saving a group with mass members causes a slow refresh and/or a page unresponsive error.
Creating a user with a client PIN, without proper permissions, results in the UserVoiceProfile to not be created. This causes the user to receive an undefined error when logging into messaging or staff assignment.
For B3000n badges, if the Authentication Type is "Use Custom EAP-TLS Certificates" the configuration fields are not present.
WORKAROUND: Select "BPE -> Security Settings -> Authentication Type > EAPTLS" and uncheck "Use Custom EAP-TLS Certificates". Configure all the required fields and then click on "SUBMIT".
UID's with mixed case or upper case letters are failing to login into Platform 6.x.
When using SIP INVITE with IPv6, VSTG will restart.
When upgrading from 5x to 6x, if the default user password is not used when using the optional command parameter, it results in Voice being disabled.
WORKAROUND: Always use the system-info parameter even if it’s optional for live migrations.
When Group Conferencing is configured in Dual Mode, the Voice server can crash when a user tries to start a group conference call after playing a voice message.
If a badge is off network, the Voice server can get into a loop trying to deliver a call when that call is rejected by a Vina device that is in Dual Mode.
Running a partial migration on Platform 6.5.0 to a THR environment on version 5.7.0 appears to complete, but the process does not finish and summarize.
There is an issue with the Voice server where pieces of information are cut off, such as "Please press the star key".
Occasionally, when a user attempts to merge a call the call does not merge and a Null Pointer Exception is thrown.
The badge enunciates an urgent alert with None Type responses through the badge speaker instead of the headset speaker when "Announce through speaker" is turned off.
Logging out of a smartbadge, while in Dual Mode, will create both a logout and a login entry for the Vina device.
A logout event is not generated until a user logs into another Vina device. This only occurs in Dual Mode.
If the Multiple Active Calls (incoming and outgoing) exceed the max line configured, not all calls are ended.
A login event is created approximately every two minutes while a Vina user is off network. This only occurs in Dual Mode.
Audit searches have poor performance.
iOS devices, in a clustered environment, will not be unregistered if the app is in the background during a failover.
If an adapter is disabled, the queue for the adapter continues to stay active and consume messages.
The highest priority node in a PIP cluster cannons be replaced.
Secondary node shows as "Unknown" in Cluster Status but shows as "Slave" in .state file.
During a failover, if a split brain situation is caused by cutting of the network communication between two nodes, the higher priority secondary node immediately goes to a failed state.
During a failover, Glassfish may not restart if the postgresql-audit service is in an activating state.
During a failover, the secondary node can enter a failed state even when both databases are showing as "OK".
WORKAROUND: Disable and re-enable the failed node.
While upgrading, the Felix OSGi framework can deadlock. This results in the Web UI being inaccessible.
WORKAROUD: Restart Glassfish.
During an failover, security certificates are not synchronized from the Primary node to the Secondary node. Voice Group Sync will stop synchronizing with an SSL enabled Voice Server after a failover.
Upon initial login to badges, the app Location is not being stored in engage.devices.access_point_mac_address.
On occasion, during a failover, the secondary node may not repair properly.
WORKAROUND: Force failed node into a standalone state and restart Glassfish.
If a user name is changed and then the user name is changed back to the original name, the system displays an error.
A cascade delete of any user introduces long wait times for alarm/alert delivery.
When deleting a user, the audit log will flood with "Failed to process event" messages.
PFM-12469 PFM-11104
When deleting a Site or Facility only the first user is deleted.
When adding new trusted certificates for adapters, Glassfish must be restarted.