The documentation for Vocera Messaging Platform version 4.9.4 is available online:

• VMP Administrator Help
• VMP Web Console Help

From these online help locations, you can download PDF versions of the VMP 4.9.4 documentation.

This release includes the following new features and functionality. An asterisk * indicates a feature that requires Vocera Collaboration Suite version 2.0.2 clients.

• * Email communication can now be disabled on client applications. A VMP Administrator configuration option lets you control whether client applications can send email to contacts. You can disable email communication if you want to ensure that only secure modes of communication are available on client devices.

• The Public ID field can now be used for user synchronization. When importing users from multiple sources, you can now use either the email address or the Public ID as the key field for user synchronization. If user entries from multiple sources have the same Public ID, they are merged into a single VMP user entry.

• * 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 a client application 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.

• * 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.

• 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, you can specify that users are to be automatically created or deleted in the VMP Server when they are created or deleted in Active Directory.

• * Chat sessions can now be started with Distribution Lists created from Vocera Voice Server groups. When you are editing a Distribution List created from a Vocera Voice Server group, you can now select the Enable for Vocera Chat option to allow users to start Chat sessions with this Distribution List.

  Note: Setting Enable for Vocera Chat for the Distribution List does not automatically enable users to start Chat sessions with members of this Distribution List.

• Installer now checks whether the required Microsoft .NET Framework is present. The VMP Server installation program now checks whether Microsoft .NET Framework 3.5.1 is installed on the system. If it is not present, the installation program requires you to install the .NET components before continuing with the installation.

• URL API interface now available for VMP Web Console. A URL API interface now allows applications to perform specified tasks within the VMP Web Console. This interface is similar to the API interface that already exists for the Vocera Collaboration Suite.

• * Device certificate validation support added. A new configuration option has been added to the VMP Administrator that enables you to specify a device certificate. Devices must possess a corresponding certificate before they can use the Vocera Collaboration Suite to log into this VMP Server.

• App PIN specification can now be overridden for individual users. When editing user information in the VMP Administrator, you can now force the user to provide a PIN, or specify that the user does not require a PIN.

• Availability testing now added to Vocera Smartphone Proxy. The Vocera Smartphone Proxy now includes two availability tests that can be started from a web browser:

  • http://<serverid>/vsptest: A query that checks the status of the VSP.
  • http://<serverid>/WIC?query=test: A query that is terminated on the VMP Server that tests the status of VMP and the connection between the VSP and the VMP Server.

  <serverid> is the VSP IP address or domain name. These tests can be used to implement a high availability solution for VSP.

• Large VCS client deployment support. A new configuration option, Enable Enhanced Voice Server NIO Tomcat Feature, optimizes the connection between Vocera Collaboration Suite clients and the Vocera Voice Server. This allows more than 2000 simultaneous VCS clients to connect. When this feature is enabled, the network port used by VCS clients to connect to the Vocera Voice Server will change. This change could have an impact on connectivity if you are filtering traffic between the wireless VLAN used by VCS clients and the Vocera Voice Server.

Use the following steps to upgrade to VMP Server 4.9.4.

1. Stop the Vocera Data Exchange service on the VMP Server:

   1. Open the Windows Services application:

      Windows > Start > Administrative Tools > Services

   2. Click to select Vocera Data Exchange Service.

   3. Right click and select Stop.

2. Execute the updated VMP setup file on the VMP installation server.

3. Accept the License Agreement, and click Next.

4. In the Software Type dialog, select VMP Server and Administrator, and click Next.

5. Accept the existing Install Location and click Install.

6. At the Create VMP Database Wizard prompt, enter the following information and click Next.

   1. Enter the SQL Server name.

      Tip: Vocera recommends you type the name of the server and do not use the dropdown list to select a server.

   2. Select the SQL Server Authentication radio button.

   3. Enter the SA Login and Password.

7. Click OK to confirm that the existing database will be upgraded, and click Next.

8. To install the BlackBerry client using the VMP server, you must install the OTA.xml file included with the client installation files.

   Browse to the client folder, select the OTA.xml file, click Open and click Complete.

9. The installer creates the VMP databases on the SQL server. When the script is complete, click OK.

10. If the VMP Enterprise Manager opens after the database script is complete, close the application to complete the installation process. Click Finish to close the installer.

11. Restart the server.

12. The VMP Server is now updated. Confirm a good installation by opening a supported Web browser (Internet Explorer 9 or later) and pointing to the server URL. If VMP is installed correctly, the VMP Web Console opens.

This release includes the following known issues and limitations:

1. Subject line of Alert not displayed correctly if sent in UTF-8 format from a third-party system. If a third-party system sends an Alert in UTF-8 format, the subject line is not displayed correctly. To work around this problem, use EWS. (24576)

2. Large HTML and text files cannot be opened in the Content module. If an HTML file or a text file that is larger than 16KB is added to the Content module, it cannot be opened in Vocera Collaboration Suite client applications. (24938)

3. Server must be restarted if SSL is enabled on the Vocera Voice Server. If SSL is enabled on the Vocera Voice Server, the VMP Server must be restarted to ensure that Chat sessions are properly responsive. (24971)

4. Duplicate Chat messages may be sent out if client Send button pressed repeatedly. If a user in a Chat session presses the Send button more than once, duplicate Chat messages may appear. (24972)

5. Edited schedules are not updated in real time. When an on-call schedule is set to Unpublished in the VMP Web Console, any changes that are made to the shift assignment in the current shift are not applied to the associated On-Call Distribution List in the VMP Administrator when the schedule is set back to Published. (24977)

6. Email activation may not contain registration key. If you are sending installation information to a user device, the email message sent to the user may not contain a registration key. If you resend the installation information, the registration key is contained in this subsequent email message. (24995)

7. Alert notification tone sent for Chat messages when using APNS. When the VMP Server is sending through APNS, it sends the notification tone for an Alert even if it is sending a Chat message. This behavior will be fixed in the next release of VMP. (25187)

8. Schedule marked as invalid if empty shifts exist in the past. If you create a new schedule in the VMP Web Console that contains empty shifts for a date before the current date, the schedule is considered invalid when you attempt to validate it. (DE4250)