This release includes the following new features and functionality. An asterisk * indicates a feature that requires VMP Server version 4.9.4.

• * Email communication can now be disabled by the system administrator. A VMP Server configuration option now controls whether Vocera Collaboration Suite users can send email to contacts. The system administrator can disable email communication to ensure that only secure modes of communication are available on client devices.

• * Support provided for new search scope features in the Vocera Collaboration Suite API. The VMP Server now supports searches for the Public ID and Active Directory account name in user definitions, and searches for the Distribution List ID field in Distribution List definitions. This enables the searchScope field in the Vocera Collaboration Suite URL API interface to be set to adID, userPublicID, or dlPublicID.

• * Device certificate validation support added. You can now specify that devices running Vocera Collaboration Suite must possess a device certificate. This certificate must correspond to the certificate referenced on the VMP Server.

• Audio packets now marked with QoS. Data packets created using Vocera Collaboration Suite are now marked with QoS to ensure greater quality and reliability.

• * Chat messages can now be sent to Vocera badges. Vocera Collaboration Suite users can now send Chat messages to Vocera badge users. Vocera badge users can respond with a predefined "On my badge" response, or call the initiator back.

• * User creation and deletion can now be automatically synchronized with Active Directory. If the VMP Server has been configured to synchronize with an Active Directory server, users are now automatically created or deleted in the Vocera Collaboration Suite when they are created or deleted in Active Directory.

• * Support provided for site-specific Vocera Client Gateway IP address capability in Vocera Voice Server. If a version of the Vocera Voice Server has been installed that supports site-specific IP addresses, when the Vocera Collaboration Suite connects to the VMP Server, the server now obtains location information for the client, and uses this information to obtain a list of Vocera Client Gateway IP addresses for that site. This ensures that client applications do not become connected to remote Vocera Client Gateway locations, which could adversely affect the quality of voice communications.

• Audio quality improved in Android clients. The PJSIP communication library is now included with Vocera Collaboration Suite for Android, and the standard volume keys can now be used to adjust the volume level.

Vocera Collaboration Suite version 2.0.2 provides support for all devices running Android OS 4.0 and later.

Vocera Collaboration Suite 2.0.2 clients are compatible with VMP Server 4.9 and later.

Vocera Collaboration Suite clients are not compatible with VMP Server 4.8. To use the Vocera Collaboration Suite, you must upgrade your VMP Server.

If you are using the Vocera Collaboration Suite 2.0.2 client with VMP Server 4.9.1, the following limitations exist:

• Unread counts of Alert messages and Chat sessions may not be completely accurate.
• Some Alert Template functionality may not be available.
• Alert and Chat content is not suppressed in popup notifications.
• In Dual Mode, Calls cannot be originated on the app and connected on the badge.
• Alerts with more than 200 recipients cannot be sent.
• Response notification to a sent Alert is not available.
• Users cannot enable the use of a PIN.

To install Vocera Collaboration Suite 2.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:

• Limitation period removed for messages downloaded to shared devices. In previous releases of Vocera Collaboration Suite, there was a 2-day limitation period placed on the messages downloaded for shared devices. This limitation has been removed. Message downloading is now based on user preferences.

This release includes the following known issues and limitations for versions of the Vocera Collaboration Suite running on Android operating systems.

1. SIP call not made through URL API if recipientKey search fails. If the Vocera Collaboration Suite URL API is used to make a call, and the recipient is not found using the recipientKey search parameter, the phoneNumber parameter, if provided, should be used to place a SIP call, but is not. This capability is available in the iOS version of the Vocera Collaboration Suite. (24816)

2. Return button is displayed when Vocera Collaboration Suite is invoked through the URL interface without a callback URL. When an application uses the URL interface to access the Vocera Collaboration Suite, the Return button is displayed on the Menu screen even when no callback URL has been provided. (24909)

3. Alert and Chat notifications may be received during a Call. If you are in a Call, you may receive a popup notification and vibration when an Alert or a Chat request is sent to you. The Alert vibration may last up to 30 seconds. (24912)

4. No notification tone or vibration for second incoming Call if vibration disabled in profile options. If you have disabled vibration in the Call Notifications section of the profile options and you are in a Call, the short notification tone or vibration that is supposed to be played to indicate a second incoming Call is not provided. (24922)

5. The recipient ID in the Vocera Collaboration Suite API interface is case-sensitive. If you use the Vocera Collaboration Suite API to create a URL, the "recipientKey" parameter in this URL should be case-insensitive but is not. (24945)

6. "Push to Talk" button enabled during Panic Call (HTC One). On the HTC One device, if you initiate a Panic Call, the "Push to Talk" button is incorrectly enabled. (24958)

7. Unexpected behavior when Bluetooth headset and wired headset are both connected. If you have connected a Bluetooth headset and a wired headset to your device, audio should go through the Bluetooth headset. Instead, it initially goes through the wired headset for about 5 seconds, and then is routed to the Bluetooth headset. Note that there are no problems when only one headset is connected. (24959)

8. Handset icon not properly highlighted when headset unplugged. If you are in a Call while using a wired headset, and you unplug the headset, the call is properly routed through the handset on some devices, and is routed through the speaker on others. The Handset icon is not highlighted. (24960, 24964)

9. Audio not behaving properly in broadcast if Bluetooth headset provided. From the Contacts list, if you make a Call to a Distribution List while a Bluetooth headset is attached to your device, the audio does not behave as expected. Audio input is taken from a wired headset if it is provided, or from the handset otherwise. (24961)

10. Backspace not working in dialpad. If you are using the dialpad to call a phone number, the backspace key does not remove the display of the last digit that you typed. Typing a new digit overwrites the old one. (24965)

11. Do Not Disturb for Voice not turned off after callback. If you have received a page or other VMI message, you tap "Vocera Call Back" to call the number provided in the page while "Voice - Do Not Disturb" is set, and then you end the call yourself, the Do Not Disturb setting should be turned off, but is not. (24969)

12. New Chat requests are not indicated in Chat session. If you are in the Chat screen, new Chat requests appear, and you join an existing Chat session, the new requests are not included in the count of the number of outstanding new Chat messages. (24980, 24981)

13. Shift ending at midnight displayed in next day. When displaying your shifts in the My Shifts screen, a shift that ends at midnight is shown as being on both its day and the next day. (24993)

14. Blank screen may appear when Back button pressed after application launched from lock screen. On some devices, if the device settings have been configured to show all notification content when the device is locked, and you receive an Alert while your device is locked, a blank screen appears when you tap your device's Back key after displaying the Alert. (25012)

15. Screen may not be turned on when notification received. In specific scenarios, when you receive a notification while your screen is turned off, the screen does not turn on and the volume buttons do not control the notification volume. To get around this problem, turn your screen on. (25042)

16. Dragging a Favorite causes other Favorites to disappear (Android 5). On some devices running the Android 5 operating system, when you are viewing Favorites in the Contacts screen and you drag a Favorite to rearrange the order in which the Favorites are displayed, other Favorites disappear from view. If you close the app and restart it, the Favorites reappear in the rearranged order. (25046)

17. After logging into a second device, the VMP Server does not immediately log out of the first device. If you are logged into a device, and then log into a second device, the voice capabilities become immediately unavailable on the first device, but the VMP Server waits approximately two minutes before logging the first device out. This problem appears on Android clients only, not on iOS clients. (25101)

18. Ringtones and vibrations for Vocera calls are sometimes not received while recording through the phone camera. On some Android devices, if you are recording using your camera's phone and the Vocera Collaboration Suite receives a Vocera call, you will neither hear a ringtone nor detect a vibration. (25105)

19. Device must be unlocked if device and application level PIN are required and a second call is received. If your device requires a PIN to unlock, the use of an application-level PIN is enforced in the Vocera Collaboration Suite, and you are in a Vocera call, you must supply your device PIN when you receive a second call. (25117)

20. DMTF tones through dialpad not heard or observed in logs. When you are placing a call through the dialpad, pressing the * and # keys produces no sound, and the key presses do not appear in the logs. (25129)

21. Email address containing underscore not matched in search. When performing a search, email addresses containing the underscore _ character are not matched. (25138)

22. Vocera Collaboration Suite may crash if device rebooted or app killed and app not restarted. If you have rebooted your device or have killed Vocera Collaboration Suite, and you have not restarted the app, it may crash if an incoming call is received. (25159)

23. Search in Word document in Content module does not limit heading links displayed. In the Content module, if you open a Word document and type in the Search field, only the heading links that match the search criterion should be displayed. At present, all heading links remain displayed. (25161)

24. Search in Excel spreadsheet in Content module does not limit sheet links displayed. In the Content module, if you open an Excel spreadsheet and type in the Search field, only the sheet links that match the search criterion should be displayed. At present, all sheet links remain displayed. (25162)

25. Search results not updated if text removed from search criterion. If you delete characters from the end of a search criterion, the search results are not automatically updated. (25163)

26. Schedules for current week not displayed properly on Samsung Galaxy S5 devices. When you display My Shifts and select the Week view, the schedule is displayed for Saturday only. This problem has been detected on Samsung Galaxy S5 devices only. (DE4494)

27. Some text not displayed on some devices when Vocera call received while in cellular call. If you are in a cellular call, and you receive an incoming Vocera call, the text indicating what happens when you tap Answer may not be displayed properly. This problem has been detected on devices with a screen size of 1920x1280. (DE4496)