The Vocera XMPP Adapter manages stored data in Vocera Platform datasets to represent conversations and resources. An XMPP cache database stores the roster for the mobile devices. Using these datasets, conditions and rules are configured to interact with other endpoints that are not XMPP-enabled. Vocera XMPP Adapter rules are configured to send conversation, message, and presence information to the Vocera XMPP Adapter when this information is created by an external resource.

XMPP issues often relate to client behavior. View the latest documentation for Vocera Vina iOS, Vocera Vina Android, and Vocera Platform 6.6.0 for additional information.

This section summarizes the new features in this release.

This section provides information about fixes and improvements to the Vocera XMPP Adapter product.

This section provides information about known product defects and limitations in the current release.

• XMPP-32: An incoming call can be reported as a declined call when another incoming call is ringing at the same time.

  Version introduced: Vocera Platform 6.3.0

  Workaround: None

• XMPP-1217: Some users are getting logged out after rebooting the server.

  Version introduced: Vocera Platform 5.3.0

  Workaround: None

• XMPP-1221: A user cannot log in to Vocera Vina because of an invalid MRN. This issue is caused when a user starts a patient-linked conversation with a Group using Vocera Vina for Android version 10.2 or earlier. After the XMPP server moves the conversation out of memory, the users are unable to log in to Vina.

  Version introduced: Vocera Platform 6.0

  Workaround: This issue is fixed in the Vocera Vina for Android 10.3 release. If you are running Vocera Vina for Android 10.2 or earlier, upgrade to version 10.3.

• XMPP-1306: When a message recipient's Android device has the Vocera Vina app in the background, the Alert Notification does not disappear and the ringtone does not stop playing after the creator completes an urgent alert.

  This issue occurs under the following conditions:

  • The recipient is using an Android device. This issue does not occur on iOS devices.
  • The alarm event is Urgent.
  • It is a templated event.
  • The adapter configuration uses an 'urgent-alarm-playtime' custom parameter.
  • The creator of the event completes the alert before the participants accept it. If a participant accepts the alert, the alarm tone stops.

  Version introduced: Vocera Platform 6.5.0

  Workaround: This issue occurs under the specific conditions outlined above. If you are using Android devices, we recommend that you remove the 'urgent-alarm-playtime' custom parameter.