The
XMPP issues often relate to client behavior; see Vocera Vina iOS 6.0.0 , Vocera Vina Android 6.0.0 , and Vocera Platform 6.4.0 for additional information.
This section summarizes the new features in this release.
The
This section provides information about fixes and improvements made to the
The following issues are fixed in
This issue has been resolved.
This section provides information about known product defects and limitations in the current release.
User's presence is not updated to "Available" after the defined duration expires. (PFM-9544)
Workaround: When XMPP is restarted, all clients that were in DND presence will be reset to Available when they reconnect.
Presence information is reported inconsistently if you create a user who has the same login as a deleted user. (PFM-11097)
If you create a user with the same login as a previously deleted user, that person can log into the iOS version of the Unified Client but is automatically logged out after approximately 10 seconds. (PFM-11102)
If you create a user with the same login as a previously deleted user, neither the recreated user's device nor the recreated user's XMPP identity are registered with the system correctly. (PFM-11109)
When you delete a user, the audit log incorrectly reports a "Failed to process event" statement for every message that the deleted user has previously sent. (PFM-11108)
The user is successfully deleted, but the audit log contains misleading information. Performance may be adversely impacted if the deleted user has many messages.
Deleting a user who has many (approximately 4,000) combined messages, conversations, and assignments may delay the delivery of a critical alarm or alert by approximately 40 seconds. (PFM-11115)
Workaround: Restart the XMPP adapter. This will rebuild the XMPP cache creating the missing identities.
Workaround: Pre-populate the pillow_number for every bed to the value that will be reported by alerts. This will prevent the alert creation from generating a Bed subscription message, which in turn will make it extremely unlikely this particular deadlock will occur.
Workaround: After updating the Facility or Unit name in Vina Web, restart the XMPP adapter.
Workaround: Contact the Support Desk so they can run a corrective script.