This section summarizes the new features and fixed defects in VMI product version 1.1.5.2. (vmi.dll version 1.1.5.2).

• Fixed bug for writing UTF8 characters to the Vocera Voice Server. (DE79)

  Prior to this fix, certain characters passed in a VMI message could cause the VMI connection to drop.

This section summarizes the new features and fixed defects in VMI product version 1.1.5.1. (vmi.dll version 1.1.5.1).

• Logging updates.

  Supports library logging enabled by setting environment variable VOCERA_RTSLOG.

• Fixed bug in which multiple reader threads can get created. (DE2251)

  This was a race condition around VMI::Close, where receiving signals may cause an exception.

This section summarizes the new features and fixed defects in VMI product version 1.1.4.0. (vmi.dll version 1.1.4.0).

• IPv6 support

  The VMI library now supports IPv6 addresses in addition to IPv4.

This section summarizes the new features and fixed defects in VMI product version 1.1.3.0. (vmi.dll version 1.1.3.0).

• VMI client gets stuck in an endless loop using SSL. (17506)

  For VMI clients using SSL, when the connection is closed by the Vocera Voice Server to the client, you will see the VMI client spin in an endless loop (100% CPU utilization).

• Vocera Server should log the VMI version on connect. (16908)

  The VMI client library has been updated to pass the product and file version information of the library when connecting to the Vocera Server. VS 4.3 SP2 will provide this information in a log line.

This section summarizes the new features and fixed defects in VMI product version 1.1.2.0. (vmi.dll version 1.1.2.0).

• VMI over SSL. (16659)

  VMI communication can now be encrypted using SSL. The VMI library SSL functionality is enabled via a registry setting on the server on which the VMI library is running.

• Signal write should be buffered so as to write a complete signal to TCP socket to avoid fragmentation, increase performance. (16516)

  VMI packets are no longer fragmented in to multiple packets before being sent to the Vocera server. Each message is sent as one packet.

• TCP_NODELAY setting not initialized correctly causing it to be set to false. (16514)

  In 1.1.1.0 a bug was exposed which limits the speed at which VMI messages can be sent by the client. This has been fixed in 1.1.2.0.

• VMI LogEvent() sEventInfo field should support 10 items with 64 maximum length per item. (16237)

  A bug was found in 1.1.0 which was inadvertently limiting the sEventInfo string to 25 characters instead of the documented 64 characters.

This section summarizes the new features and fixed defects in VMI product version 1.1.1.0. (vmi.dll version 1.1.1.0).

• LogEvent API.

  Log Event API allows integration partners to provide transactions arround messaging events. Minor revision number incremented. Since the API has changed GetVersion() has been updated to return "4.3", although binary backwards compatibility remains. Thus, this DLL can be dropped in replace of an older version with out recompilation.

• VMI trims initial or trailing spaces from sVoceraIPAddr parameter of VMI::Open(). (14949)

  Previously, the VMI library caused an application to crash when calling VMI::Open() if the IP address specified for sVoceraIPAddr had initial or trailing spaces. VMI now trims initial or trailing spaces from the sVoceraIPAddr string.

• Update VMI build to VS2005 and add x64 (64-bit) support. (15354)

  This release now provides 32-bit and 64-bit libraries built with Visual Studio 2005. The directory structure has been reorganized in order to support this.

This section summarizes the new features and fixed defects in VMI product version 1.0.0.1. (vmi.dll version 1.0.0.1).

• Argument and range checking added to public API. (13213)

  The methods in the VMI class now to range and argument checking. There was no new error code added, in order to preserve API backwards compatibility. The API will simply return rcFailed if the call fails due to an argument or range check failure.

• Added embedded windows version information into the VMI dll. (13789)

  The VMI dll now contains embedded version information and implements it's own revision numbering. Right click on the vmi.dll, select Properties and then Details. Product version versions updates to the VMI dll itself. The File version number indicates the Vocera Server release in which the VMI dll was packaged.

• Windows handle leak during open/close. (13759)

  The VMI dll was leaking handles. One leak per successful open/close and three handles on an unsuccessful open.

This section summarizes the VMI-related changes in VS 4.4.0.

• Logging of active VMI connections – At the top of each Vocera Voice Server log file, the log indicates the number of active VMI connections and lists each VMI client and its version information.

• Configure text messages to be played aloud on Vocera badges per VMI client, site, or both - The MsgEnunciateMode property in properties.txt allows you to enter a comma-delimited list of values to specify the enunciate mode for a VMI client, a site, or both. This helps you control which text messages are enunciated for each VMI application or site.

  For details, see the Vocera Administration Guide.

• VMI broadcast prompts can cut into message enunciation - VMI broadcast messages now have an initial three seconds of silence, thus allowing prompts to finish playing before the message starts. (Issue 19852)

  The initial silence for VMI broadcasts is configurable via a Vocera Voice Server property that you can add to \vocera\server\properties.txt:

  VMIBroadcastInitialSilence = 3

  Note: If your organization has deployed Vocera smartphone applications, you may need to increase the value of VMIBroadcastInitialSilence. If you modify the properties.txt file, you must stop and start the Vocera Voice Server to load the properties into memory.