This release addresses a registration failure scenario causing users to not be able to login to the app, messages having their delivery delayed while on the Vocera Wi-Fi under certain network conditions, and a call screen UI issue if network connectivity was lost while in a call. See the What's Fixed section of these release notes for more details.

The documentation for Vocera Collaboration Suite version 3.0.2 for Android is available online:

• Vocera Collaboration Suite Android User Guide

From this online help location, you can download the PDF version of the VCS 3.0.2 documentation.

For the MC40, the following are supported:

• MC40-HC Rev C with Android 4.4.4
• MC40-HC Rev C FIPS with Android 4.4.4

For other Android devices, Vocera Collaboration Suite version 3.0.2 provides support for Android OS 4.1 and later.

If you are using Android OS 6.0 or later, Vocera recommends that you add Vocera Collaboration Suite to the list of apps that is whitelisted from battery optimization doze mode.

VCS 3.0.2 clients require VMP Server 5.1.0 for full functionality. When a VCS 3.0.2 client is connected to VMP Server version 4.9.2 to version 4.9.4, the client uses version 2.0.2 backward compatibility mode to interact with the server.

Vocera Voice Server 4.4.1 or later is required. If your organization is using Vocera Voice Server departments and synchronizing them with VMP groups, Vocera Voice Server 5.1 or later must be installed.

VMP Server 5.1 does not support message templates in which one or more recipients are Escalation Distribution Lists and other recipients are regular users. Only one Escalation Distribution List can be listed as a recipient, and it must be the only recipient.

To install Vocera Collaboration Suite 3.0.2 for Android:

1. On your Android device, open the email sent to you from the Vocera administrator.

2. Tap the first link in the email to go to the Google Play Store to download and install the Vocera Collaboration Suite app.

3. If you are prompted to complete the action using either the Internet or Play Store, tap Play Store.

   Important: If you tap Internet instead, the link to the Google Play Store won't work.

4. When you see the Google Play Store page for Vocera, tap Install.

5. After the app is installed, open the email again, and tap the second link to configure the app to connect to your organization's server.

This release includes the following fixes:

• VCS client now sends session ID information when submitting a pre-timeout request to the Vocera Server. In previous releases of VCS, if the TCP Comet connection was blocked, the pre-timeout query stopped including session ID information its query to the Vocera Server. This meant that the Vocera Server closed the session and the device initiated a new session, which led to possible delays in delivery to Android devices. This problem has now been fixed. (DE9579)

• Login no longer fails if server field not specified in HTTP reply. During registration, the VCS client for Android checks the server field in the HTTP reply. If you have overridden this field in order to hide the location of your HTTP server, the client now sends a warning to the log file instead of rejecting the login. (DE9600)

• Phantom looping call problem fixed. On occasion, if you answer a call on your Android client but the call is dropped, you may see a phantom incoming call message from the caller, which reappears if you decline the call. If you accept the call, your client initiates a call to the original caller. This problem has now been fixed. (US18791)