Before upgrading, make sure your servers, whether they are physical or virtual machines, meet Vocera recommended guidelines. See the Vocera Server Sizing Matrix.

You can upgrade to Vocera 4.4.0 from the following versions:

• Vocera 4.1 Service Pack 7

• Vocera 4.2 Service Pack 1

• Vocera 4.3 Service Pack 3

Before performing an upgrade, you MUST use the Vocera backup utility to back up existing data. Preserve this backup so that you're able to revert to the previous version.

During the upgrade process, the server restores data from a backup file. Consequently, when badges connect to the upgraded 4.4.0 server for the first time, users will be logged out automatically. Warn your Vocera users that after the firmware upgrade completes on their badge they will need to log in again.

The Vocera Installation Guide describes how to upgrade Vocera Report Server to version 4.4.0. However, note that Vocera Server 4.4.0 generates report logs with additional data to support new reporting features. This additional data is not contained in the backup file that you must restore after upgrading your previous Report Server version. Some reports will be empty or display little information until you accumulate a sufficient amount of Vocera 4.4.0 data.

After you upgrade, behavior changes in Vocera 4.4.0 may require modifications to your Vocera 4.3 or Vocera 4.4 data and settings. These modifications are described in below and in the section called "Required Post-Upgrade Tasks" in the Vocera Installation Guide.

In addition, you may want to make changes to your configuration to take advantage of enhancements in Vocera 4.4.0. While these changes are not required as part of the upgrade, you may decide that it is worthwhile to implement them at this time. These modifications are described in "Suggested Post-Upgrade Tasks" in the Vocera Installation Guide.

• Session 0 Isolation and the Vocera Control Panel – In Windows Server 2008, and later versions of Windows, the operating system isolates system services, such as Vocera services, in a hidden session called Session 0 to protect them from application attacks. However, Session 0 isolation also makes it more difficult to interact with services. To address this problem, Vocera 4.4.0 added a Vocera system tray icon that automatically launches the Vocera Control Panel in your user session when you connect to the server remotely. You can use the Vocera Control Panel to manage all the Vocera Voice servers, with the exception of the Vocera Report Server, which uses a web console instead. For details on how to use the Vocera system tray icon, choose Help > Contents in the Vocera Control Panel, or see the Vocera Administration Guide.

• Optimized Entity Prompts – The Vocera speech recognition parameters have been tuned to eliminate unnecessary silence at the beginning and end of recorded entity prompts, thus making the prompts play faster for a better user experience. Entity prompts are the recorded user names and group names stored in the \vocera\data\prompts folder on the Vocera Server. Entity prompts recorded prior to Vocera 4.4.0 are automatically optimized using a third-party sound processing utility called Sound eXchange, or SoX, which trims silence from the prompts after you upgrade the Vocera Server to Version 4.4.0.

  Important: Optimization of entity prompts may cause the upgrade to Vocera Server 4.4.0 to take longer on each machine. Also, the SoX utility reduces the size of the entity prompt files, consequently reducing the size of Vocera Server backup files. Results vary based on the number and size of entity prompts for your system.

• Updated JRE – The Java Runtime environment has been updated from JRE 5.0 (1.5.0_10) to JRE 6.0 (1.6.0_45).

• Updated Apache Tomcat – Apache Tomcat has been updated from version 4.1.39 to version 7.0.37.

• Fixed: Vocera install/uninstall should not delete an existing SSL certificate – When you install or uninstall Vocera 4.4.0, the SSL certificate located in the \apache\Apache2\conf\ssl folder is preserved. (Issues 13685, 18224)

• Simplified Badge Properties Editor user interface – The Badge Properties Editor has been simplified and enhanced to make badge configuration easier for today's wireless networks. For details, see the Vocera Badge Configuration Guide.

• Updated Vocera Prompts

  • "I'm busy at the moment."

  • "Low Battery."

  • "Searching for the server."

  • "Update complete."

  • "Uploading Badge diagnostic data."

  • "Upload complete."

  • "I'm updating the software on your badge. It may take a few minutes."

• New Vocera Prompts:

  • "Badge error detected. Please reset the badge by removing and reinserting the battery."

  • "Badge error. Please remove this badge and battery from service and return them to your system administrator."

• Updated Audio Engine:

  • Speech cone is slightly widened.

    • Will help to facilitate different badge wearing positions such as the left shoulder.

  • Microphone amplification has been reduced (comparable to B2000).

    • Will help to reduce the pickup of background noise.

  • Noise reduction algorithms have been tuned to better filter extraneous audio sources including beep tones caused by patient-monitoring equipment.

    • Badge is tuned to avoid causing a feedback “broadcast loop.”

• Enhancements from B3000 firmware build 170:

  • User notification for warm badges

  • User notification for warm badges (see KB article 1967)

  • Secured credentials in badge logs

  • Smart battery logging enabled by default

• Fixes from B3000 firmware build 170:

  • Fixed: Badge may scroll through menu when in close vicinity of a GSM cellular device

  • Fixed: Asserts when adjusting volume very quickly

  • Fixed: Fails WPA-PEAP external certificate authentication in non-FIPS mode

  • Fixed: Fails CRC check when downloading unique certificates from server

  • Fixed: Badge can experience a short “Searching for Server” due to “User Specific Settings” signal mismatch

  • Fixed: Wired headset microphone unable to receive a command

  • Fixed: Custom alert tones can only be played if present in /g3/badge/res and /g3/badge/res/prompts/common

  • Fixed: Badge could enter WEP mode when configured for AES resulting in “Searching for Server”

  • Fixed: Badge does not return from sleep state if taken off network during initial boot

  • Fixed: Certificate-based authentication fails because badge sometimes boots up with date that is outside Certificate validity

• New notifications for entry and exit of dual mode – An alert now notifies users when the voice functionality moves to and from a smartphone (or other device) and the badge.

• Speech recognition is now improved to ensure that callbacks only occur when the user used the callback prompt.

• Messaging Notification Improvements – The following enhancements are added to minimize inadvertent callbacks and improve messaging notifications:

  • Speech recognition is now improved to ensure that callbacks only occur when the user used the callback prompt.

  • Users are now prompted with a call back notification before a triggered callback is initiated.

• New phonetic name dictionary. – This release improves name recognition by installing a phonetic dictionary with 160,000 names and pronunciations. The phonetic dictionary replaces the names.dict file in the \vocera\server\grammars\custom directory.

  The new phonetic dictionary should already include all the pronunciations in a custom dictionary (names.dict) from any previous Professional Services engagement. The installer backs up your existing names.dict to vocera\restore\vocera_pre_4.4.2\vocera\server\grammars\[locale]\names.dict. You may compare the entries in your custom dictionary to the pronunciations in the new dictionary; if you find pronunciations in your custom names.dict that are not in the new phonetic dictionary, please contact Tech Support for information on how to merge the files into one dictionary.

• 100 Staff Assignment Premier licenses included with Vocera Server Enterprise. – As of this release, 100 Staff Assignment premier licenses are provided with a Vocera Server Enterprise license. If you are an existing enterprise user, navigate to the Administration Console System Info tab to confirm your available licenses.

• New Genie Personas for English-Speaking Locales – After upgrading to Vocera 4.4.0, the Genie personas for English-speaking locales are replaced with new personas:

  Locale	Old Genie Personas	New Genie Personas
  United States (US)	Mark, Jean	Dan, Jennifer
  Canada (CA)
  United Kingdom (UK)	Simon, Liz	George, Emma
  Australia (AU)
  New Zealand (NZ)

  The prompts for these new Genie personas have been recorded with different voiceover talents, so users may notice a change in the Genie's voice.

  Note: Vocera's text-to-speech voice is different from the Genie persona voices and it has not changed for this release. The text-to-speech voice is always a female voice regardless whether you select a male Genie persona.

• Revised settings for System Preferences and Defaults – For new installations, the following settings have new default values:

  • System > Preferences > Enable Auto-Logout – disabled by default and set to log users off after two hours off network.

  • System > Preferences > First Name, Last Name, and Department – disabled by default.

  • System > Preferences > VMI Preference – set to block non-urgent VMI messages for users in DND by default.

  • System > Sweep > Sweep Age – set to delete messages older than two weeks.

  • Defaults > Genie Settings > Genie Greeting – set to Speech Only.

  • Defaults > Genie Settings > Call Announcement > Announce Name of Called Group – enabled by default.

  • Defaults > Notifications > Reminders > Voice Message Reminder – enabled by default.

  • Defaults > Notifications > Reminders > DND Reminder – enabled by default.

  For customers upgrading to Vocera 4.4.0, Vocera recommends changing these values and selecting Override User Settings to Yes.

• Active Directory authentication – Configure the Vocera Server to use Active Directory for Vocera client authentication.

• Vocera System Tray Icon – The server now provides a system tray icon to manage server stop and start tasks, and to access the Vocera Control Panel.

• Up to 100 free Staff Assignment Premier licenses included with Vocera Voice enterprise license – If you have a Vocera Voice enterprise license, you automatically receive up to 100 free Staff Assignment Premier licenses when you upgrade to Vocera 4.4.0. You do not need to change your Vocera Server license to receive the Staff Assignment Premier client licenses.

  Note: Upgrading to Vocera 4.4.0 does not add 100 more Staff Assignment Premier licenses. If you have a Vocera Voice enterprise license and fewer than 100 Staff Assignment Premier licenses, upgrading to Vocera 4.4.0 automatically increases your Staff Assignment Premier licenses to exactly 100.

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

• Play Test Tone and Broadcast Test Tone improvements – The Play Test Tone and Broadcast Test Tone commands have the following improvements:

  • The commands are supported in all Vocera 4.4.0 locales, not just the United States. (Issue 18207)

  • The commands are supported for users with administrator privileges in all sites, not just Global. (Issue 17910)

  • If all your calls are forwarded, Broadcast Test Tone still works. (Issue 20538)

• Badge MAC address is now listed with the user information in logs  – To help in troubleshooting badge problems by reviewing the server logs, the badge MAC address is now listed with the user information. The LogMACAddress property is disabled by default. To enable this property, set it true in the in properties.txt file. For details, see the Vocera Administration Guide. (Issue 17845)

• Fixed: DTMF tone received by the Vocera Server is not resent to distant connection during a two channel call  – An issue where the DTMF tone received by the Vocera Server was not resent to distant connection during a two channel call, is now resolved. (Issue 15569)

• Fixed: Administration Console transposes the month and day of the Expiration Date field for a temporary user in the Add/Edit User dialog box – The Administration Console no longer transposes the Expiration Date that you enter for a user. (Issues 17883, 19127)

• Fixed: ServerQ timeout in java.io.WinNTFileSystem.getLastModifiedTime() – This Vocera Server crash has been fixed by using another means to determine a file's timestamp. (Issue 18034)

• Fixed: Using a number with an underscore in a user's name can cause grammar compilation to fail – If you enter a user's first or last name with an underscore character, the underscore is removed from the spoken grammar file. (Issue 18157)

• Fixed: AU and NZ locales treat 10 digit phone numbers as literals – The maximum phone number length has been changed to 10 digits for AU locale and 11 digits for NZ locale.

  AU and NZ both support 10-digit dialing for local and long distance calls. Additionally, NZ supports 11-digit dialing for mobile calls (defaults to long distance). (Issue 18291)

• Fixed: POP3 connection prevents MailChecker from running – An issue where the server would get stuck waiting for a response is now fixed. A response time out now kills the task if it does not complete in a configured time period. For information about configuring the time out value, contact support.(Issue 18950)

• Fixed: The play icons on the Genie Settings page of Administration Console and on the Announcements page of the User Console do not play audio files – If you click the play icons in the Administration Console and User Console, they now play the appropriate audio files. (Issues 20324, 18318)

• QoS Manager installs with Vocera SIP Telephony Gateway and Vocera Client Gateway – The QoS Manager service, which prioritizes voice packets over the network, now installs on the Vocera SIP Telephony Gateway and the Vocera Client Gateway. Previously, it was installed only on the Vocera Server.

• Fixed: Exception thrown in thread SIP stack thread causes restart of Vocera SIP Telephony Gateway – An issue where an exception cause the Vocera SIP Telephony Gateway to restart unexpectedly is now resolved.(Issue 20343)

• Enhanced: Reports that were deprecated in Report Server 4.3 have been removed –The following deprecated reports are no longer available and have been replaced by newer reports. Make sure you update any scheduled report packages that use these reports.

  Report removed from Report Server 4.4.0	Use this report instead
  Summary Reports > VMI Message Activity	Integration Reports
  Summary Reports > Speech Recognition Distribution Chart	Speech Reports > Speech Recognition Distribution Chart
  Diagnostics Reports > Recognition Results by User	Speech Reports > Recognition Results by User
  Diagnostics Reports > Recognition Results by Access Point	Speech Reports > Recognition Results by AP
  Diagnostics Reports > Low Recognition Results By Access Point	Speech Reports > Recognition Results by AP
  Diagnostics Reports > Recognition Results by Device	Speech Reports > Recognition Results by Device
  Diagnostics Reports > Low Recognition Results by Device	Speech Reports > Recognition Results by Device
  Diagnostics Reports > Recognition Results by Device	Speech Reports > Recognition Results by Device
  Diagnostics Reports > Low Recognition Results By User	Speech Reports > Recognition Results by User
  Diagnostics Reports > High Recognition Results By User	Speech Reports > Recognition Results by User
  Custom Reports > Login-Logout Report	Call Reports > User Activity Report (select Login/Logout for the Activity Type parameter)

• Fixed: VRS dataload should fix wildcarded access points in the database to report Unassigned APs correctly – An issue where the Unassigned APs report did not include access points that were specified by wildcard, is now resolved. (Issue 17597)

• Fixed: Badge Usage report returns an empty data set – An issue where the Badge Usage report returned empty data, is now resolved. (Issue 18843)

• Fixed: Device Last User Access report data cannot be exported – An issue where the Device Last User Access report data could not be exported from the Vocera Report Server, is now resolved. (Issue 19721)

Vocera Messaging Interface

• Logging of active VMI connections – At the top of each Vocera 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.

• Fixed: 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 Server property that you can add to \vocera\server\properties.txt:

  VMIBroadcastInitialSilence = 3

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

Vocera Administrative Interface

• New VAI class methods for Active Directory authentication – The following new methods have been added to support using Active Directory credentials to connect to the Vocera Server:

  • checkADAdminCredentials()

  • checkADUserCredentials()

  • openWithADLogin()

  For details about these methods, see the Javadoc for the VAI class.

• Faster call completion – Vocera calls complete up to 33% faster due to the following enhancements:

  • Removed excess silence in user and group name recordings

  • Enabled Fast Call Setup by default

  • Optimized the “Can you take a call?“ prompt

  • Shortened Genie prompts

• Three no-speech timeouts maximum – If you don't reply to three Genie prompts in a row, the call ends automatically.

• Reminder to record your name on login – If you have not recorded your name, the Genie reminds you to record one the next time you log in.

• Enhanced voice user interface notification on first login – When users log into Vocera 4.4.0 the first time, the Genie announces the voice user interface enhancements that have been made, such as faster Genie interactions and new prompts.

• Fixed: Vocera Smartphone rebooting in areas of poor Wi-Fi coverage – Previously, Vocera Smartphone devices manufactured by Motorola sometimes rebooted if users roamed into an area of poor Wi-Fi coverage (such as an elevator). This issue has been fixed in Vocera Smartphone firmware 2.4.2.0125. (Issue 19353)

The following changes in behavior occurred between Vocera 4.3 and Vocera 4.4.0:

• QoS Manager installs with Vocera Server, Vocera SIP Telephony Gateway and Vocera Client Gateway – The Vocera QoS Manager, which prioritizes voice packets over the network, is now installed with the Vocera Server, Vocera SIP Telephony Gateway, and Vocera Client Gateway.

• Recorded Genie prompts – Users may notice a change in the Genie's voice. All English Genie prompts, both male and female, have been re-recorded using different voiceover talents. Several new prompts have been added.

• Faster call announcements – Call announcements are much shorter, saving users valuable time. It may take a few calls for users to adjust to the shorter call announcement. The response to the prompt (Yes or No, using a voice response or buttons) has not changed.

• Recorded name reminder – If users have not recorded their name, the Genie reminds them to record one at the next login.

  If you'd rather not remind users to record their names, you can disable the system preference for this feature.

• Active Directory authentication – If Active Directory authentication is enabled in the Administration Console, users must log into the Administration Console, User Console, and Staff Assignment using their Active Directory credentials.

  If you enable Active Directory authentication, make sure you notify users of the change. Otherwise, they may try to log in using their Vocera user ID and password.

  When Active Directory authentication is enabled for the Vocera Server, the Password field for users in the Administration Console and User Console is required only for Vocera Connect users. Otherwise, it is not used. Also, Vocera administrators cannot log into User Console as any Vocera user using the Administrator password.

• Change if “Announce Caller's Name After Tone” is NOT selected – There is a change in behavior when the “Announce Caller's Name after Tone” default setting is NOT selected. With Vocera 4.4, the recipient of a call heard only a chime to announce the call. With Vocera 4.4.0, the recipient of a call now hears a chime plus “Accept call?”

• Changes to the Badge Properties Editor – To simplify the Badge Properties Editor user interface and make it easier to configure badges for today's wireless networks, several badge properties have been removed. The removed properties are still supported and their default values have not changed. For details, see the Vocera Badge Configuration Guide.

• Vocera Report Server Diagnostics reports removed – The Diagnostics reports, which were deprecated in Vocera Report Server 4.3 and replaced by the Speech Reports, have been removed from the product. Make sure these reports are not used in any of your scheduled report packages. For a complete list of the deprecated reports that have been removed, see .

• Vocera Report Server report results below generation thresholds are no longer highlighted in red – Report Server report results that fall below a report generation threshold are no longer highlighted in red.

• Smaller Vocera Server backup files – Due to optimization of entity prompts, Vocera Server backup files may be noticeably smaller after you upgrade to Version 4.4.0.

• Java Runtime Environment (JRE) update – Vocera Administration Console, Report Console, and VAI applications all require JRE 6.0 (1.6).

  Note: Staff Assignment and User Console do not use applets and therefore do not require a client-side JRE.

The following changes in behavior occurred between Vocera 4.2 and Vocera 4.3:

• Changes made to the signaling between badges and the server – Users will experience a short outage (several minutes) while their badges connect to the upgraded 4.4.0 server for the first time and download new firmware. Due to changes made to the signaling between badges and the server, the badges cannot download the new firmware in the background. Plan for downtime accordingly. Subsequent badge firmware updates that don't involve a signaling change should occur in the background.

• Frequently Called Departments – The Vocera Server accumulates call history data, calculating the frequency of calls made from one department to another. The data is used at recognition time to apply probabilities to user names in the speech recognition grammar files, resulting in overall improvements in speech recognition.

  The Frequently Called Departments feature replaces the Inner Circle mechanism that was available in Vocera 4.1 and earlier releases.

  For information on how to administer Frequently Called Departments, see the Vocera Administration Guide.

• Change to behavior of sWAVFiles parameter of the VMI Message method – Previously, you could specify multiple WAV files in the sWAVFiles parameter to use as responses to a VMI message. This parameter has been modified. It now takes only one WAV file as a custom alert tone. The WAV file must be located in the \vocera\config\custom\prompts folder on the Vocera Server so that it gets loaded on the badges. Only the first WAV file specified is used; other comma-separated WAV files are ignored. For details, see the Vocera Messaging Interface Guide.

• New location of custom audio prompts – Here is the location on the Vocera Server computer for custom audio prompts used by VMI messages:

  \vocera\config\custom\prompts

  To use custom audio prompts, place the WAV files in the above folder on the Vocera Server and then stop and start the server to force devices to download the custom prompts.

• By default, the "Skip" response to VMI messages that are played aloud has been disabled – By default, when users play VMI messages aloud they must either Accept or Reject the message (or say another valid response); they cannot respond by saying "Skip," which skips the message. However, you can enable the "Skip" response by adding a property to the properties.txt file on the Vocera Server. For details, see the Vocera Messaging Interface Guide.

• Change to Report Server filtering by department – Previously, if you filtered Report Server reports by department, any calls or VMI messages made directly to a department were listed under "Department: Not Assigned" in reports. Now such records are listed under their own department along with other groups in that department. This change affects the following VRS reports:

  • Group Entry Summary

  • Incoming Calls to Groups- Summary

  • Incoming Calls to Groups- Detail

  • Broadcasts

  • VMI Message Activity

  For details, see the Vocera Report Server Guide.

• Improved: No autocomplete for password fields – Text autocomplete is turned off for password fields.

• Fixed: The Voice Server fails when the badge initiates a phone call to a number or extension that is busy with an existing call - The Voice Server no longer fails in this situation. (Issue 22831)

• Fixed: The Voice Server may fail during the setup of a badge conference if a user presses the Call button to accept the conference invitation and then immediately presses the Call button to disconnect - The Voice Server now handles the disconnect without failing. (Issue 22923)

• Fixed: Vocera Server report logs do not include auto-logged out events  – An issue where auto-log out events did not appear in the report server log is now resolved. Additionally, the User Activity report and the Simultaneous User Login report include the login/logout information for improved accuracy. (Issue 18675)

• Fixed: Email sent from Vocera Messaging is not delivered – An issue where email triggered from the messaging feature was not being delivered properly, is now resolved. (Issue 19722)

• Fixed: Broadcast Announcement is not correct  – An issue where the broadcast announcement was not the same as for non-broadcast announcements of the same type, is now resolved. (Issue 20791)

• Fixed: Joining completed broadcast causes server crash  – An issue where the server would crash when a user attempted to join a completed broadcast is now resolved. (Issue 21399)

• Fixed: Users are not removed from groups upon logout – An issue where users would log out but would still be assigned on the escalation list for assigned groups is now resolved. (Issue 21720)

• Fixed: Multiple badge log in attempts cause the server to crash – An issue where the server would crash during multiple log in attempts is now resolved. (Issue 21930)

• Fixed: Installer incorrectly indicated installation success when Tomcat is not installed correctly  – An issue where the installer did not report an error when Apache Tomcat was not installed correctly is now resolved. (Issue 22160)

• Fixed: VCS Voice login /logout events are not written to the report logs  – An issue where shared mode VCS client does a login and logout events were not recorded in the report logs is now resolved. Additionally, the User Activity report and the Simultaneous User Login report include the login/logout information for improved accuracy. (Issue 22264)

• Fixed: Certain VAI API actions with a pre-4.4.1 server.jar against a 4.4.1 server cause a VAI Exception – VAI operations against a 4.4.1 server using a pre-4.4.1 VAI library no longer result in a failed operation or a Java exception. (Issue 22299)

• Fixed: VRS connection to mail server does not work properly when using self-signed certificates with the SMTP over SSL option enabled – The SMTP over SSL option now works correctly when self-signed certificates are in use (20375)

• Fixed: User Activity report does not display auto-logout events –The User Activity report now displays entries showing when a user is automatically logged out due to being off network longer than the specified Auto-Logout period (18643)

• Fixed: Special characters + and % need to be supported in messages to mobile and Cisco clients – The server now encodes + and % characters properly so they can be sent and received with mobile and Cisco clients. (Issue 18301)

• Fixed: The server may crash when a call is put on hold before an attempt to transfer a call – The server now handles this multiple call scenario properly. (Issue 18582)

• Fixed: If a smartphone running Vocera Connect roams off network while receiving a call, the server does not follow the user's specified forwarding rules – If the user has forwarding enabled, the server now honors the user's forwarding rules whether he is using a badge or Vocera Connect. (Issue 20027)

• Fixed: Session number reuse in startaudio signal causes incorrect audio flow – This issue sometimes occurred when a device roamed off network, causing an erroneous near hangup to be sent from the server, which affected another active call. The server now sets the line to null so that it is not reused. (Issue 20849)

• Fixed: Text messages from VMP that have a pipe (|) character can result in an invalid Vocera Server backup file – The special logic around pipe characters in VMP messages was removed. Pipe characters in VMP messages no longer cause invalid Vocera Server backup files. (Issues 21307, 21385)

• Fixed: New features prompt needs to tell users to wait until the Genie is done speaking before accepting a call – The prompt that users hear the first time they log in describes how Vocera has changed the way you receive incoming calls, and it now instructs users to wait until the Genie asks them to accept the call before saying "Yes" or "No." (Issue 21398)

• Fixed: VCG client switching VCG's in the middle of the call causes a server assert – The Vocera Server now handles this situation and does not end the call when a reconnect to another VCG is expected. (Issues 21945, 22022)

• Badges configured to use TCP-to-Genie can assert because of network errors – When a TCP error event is invoked, the error is presented, but the failover to UDP does not occur. This will be fixed in an upcoming release. (Issue 13189)

• When you remove a headset, the B3000 sometimes assumes the Call button has been pressed – If you remove a headset from the B3000, the badge could assume incorrectly that the Call button was pressed. If you are on a call, removing a headset could end the call. (Issue 15639)

• The badge does a full roam in CCKM mode – The badge sometimes does a full roam when CCKM is enabled on the badge and AP. This issue will be fixed in an upcoming release. (Issue 16122)

• Badges placed in the charger with their batteries sometimes hang – When a B2000 badge is placed into a charger with its battery, the badge can sometimes hang (the display is frozen and the badge does not respond to button presses). (Issue 6987)

  Workaround: Remove the badge from the charger, pop out the battery, and insert the battery again. To avoid the problem, charge the battery without the badge.

• When CCKM is enabled on the badge, and not the AP, the badge does not associate with the AP – In certain configuration scenarios, where CCKM enabled on the badge and disabled on the AP, the badge gets stuck in SFAP mode. This issue will be fixed in an upcoming release. (Issue 7942)

• Badges configured to use TCP-to-Genie can assert because of network errors – See known issues. (Issue 13189)

• The badge does a full roam in CCKM mode – See known issues (Issue 16122)

• Speech cutouts due to overhead beeps or other background noises – Acoustic echo cancellation sometimes causes speech to cut out when there are overhead beeps or other background noises. (Issue 19874)

• Text messages limited to 150 characters – Text messages that you receive on the phone are currently limited to 150 characters. (Issue 11420)

• Vocera Smartphone phone does not show the Reply option on receiving a message when VMP is not connected – If a User Console text message is sent to a user with a Vocera Smartphone when VMP is not connected, the message does not have a Reply option. A Vocera Smartphone hotfix is planned to fix this issue. Please contact Vocera Technical Support for details. (Issue 20495)

• Not all listed ring types are supported – "Ring," "Vibrate," "Vibrate and Ring," and "Silent" are the supported ring types. "Ring once" and "Increasing Ring" translate to "Ring". All other ring types except "Vibrate and Ring" and "Silent" type behave like "Vibrate".

• Rebooting the phone clears the speakerphone setting – If you reboot the phone, the speaker phone setting is cleared. When the phone is updated remotely by MSP and it is rebooted, the speakerphone setting will be set to the default (off).

• Phone stuck in "Searching for Gateway" mode – Occasionally, the phone will get stuck "Searching for Gateway". If this happens, reboot the phone.

• Call history is not currently supported on the phone – The phone currently does not have a Call History list that you can use to call users whom you called or who called you previously.

• The Welcome Tutorial does not describe how to use the phone – The Welcome Tutorial that's available when you say the command "Play Welcome Tutorial" is badge-specific and does not describe how to use the phone's features.

• Internet Explorer requires configuration before it can work.

  To enable Internet Explorer on the Vocera Smartphone:

  1. Press Start > All Programs > Internet Explorer.

  2. Press Menu > Tools (option 9).

  3. Select Options (option 3).

  4. Select Connections.

  5. Uncheck the Automatically Detect Settings checkbox.

  6. In the Select Network list, select Work.

  7. Press Done to close the Connections window.

  8. Press Done to close the Options window.

• Non-administrative users are unable to use the Client Redirect Utility to log into the Administration Console or User Console – Users without administrative access to the local machine are unable to use the Client Redirect Utility to access the Administration Console or User Console on the active Vocera Server. (Issue 12008)

  Workaround: Log into the Administration Console or User Console by entering the URL for the active Vocera Server rather than using the Client Redirect Utility.

• In Internet Explorer 8 or later, the Client Redirect Utility opens a new window rather than a new session – If you install the Client Redirect Utility, click the Administration Console shortcut to open the Administration Console, and then click the User Console shortcut to access the User Console, a warning message will appear telling you that you must open a new Internet Explorer session. (Issue 12249)

  Workaround: Choose File > New Session, and then enter the URL for the User Console.

• Client Redirect Utility does not work if SSL is enabled – When SSL is enabled on the Vocera Server, the Client Redirect Utility can no longer find the active Vocera Server. (Issue 14619)

  Workaround: Log into the Administration Console or User Console by entering the URL for the active Vocera Server rather than using the Client Redirect Utility.

• Cannot use voice commands to assign access points to locations at sites other than your home site – If your Vocera system has multiple sites, you cannot use the "Begin Tour" command on a badge to assign access points to locations at a site different from your home site. If you try to assign an access point to a location at another site, the Genie will not recognize the location name, and therefore responds, "I'm sorry, I didn't understand." (Issue 15164)

  Workaround: Import access points data into the Vocera system using the access points data-loading template.

• If VTS is no longer running, the Dialogic system service is not stopped automatically – If VTS has been stopped or shut down from the Telephony Control Panel, or the server has crashed, the Dialogic system service is not stopped automatically, which means existing calls are not dropped and new calls are still accepted by that telephony server. This affects telephony redundancy. (Issues 7277, 8294)

  Workaround: Use the Dialogic Configuration Manager (DCM) to stop the Dialogic system service on the inactive telephony server to ensure it does not accept new incoming calls.

  To stop the Dialogic system service:

  1. Choose Start > Programs > Vocera > Telephony Server > Dialogic Configuration Manager - DCM.

  2. Click OK in the confirmation dialog box.

  3. In the Dialogic Configuration Manager window, choose System > Stop System.

• Choppy Audio when multicast is enabled on clients with multiple VCGs – Multicast should not be enabled for clients with multiple VCGs. Using multicast may result in choppy audio and other degradation of system communications. (Issue 18824)

• Cannot ignore a Vocera call by pressing the red Power/End button on Cisco wireless IP phones – If you receive a Vocera call on a Cisco wireless IP phone, you cannot reject the call by pressing the Power/End button (the red button on the keypad). Instead, the Power/End button turns off the ringer. To reject a Vocera call, press the Reject softkey. (Issue 15125)

• Cisco wireless IP phones do not display an appropriate error when the Vocera Server is down – When the Vocera Server is not running, Cisco wireless IP phones display a screen that reads, "Warning - Not Available" instead of a message that clearly indicates that the Vocera Server is temporarily down. (Issue 15134)

• Cisco wireless IP phones are not automatically loaded into the Vocera system for device management purposes – When a Cisco wireless IP phone connects to the Vocera Server, it is NOT automatically loaded into the system for device management purposes. Vocera Server does not support device management of Cisco phones. (Issue 15135)

• Badge Status Monitor in Administration Console does not display the location of Cisco wireless IP phones – When a Cisco wireless IP phone is connected to the Vocera Server, its location is not shown in the Badge Status Monitor, unlike other Vocera devices. (Issue 15137)

• Keypad lock on Cisco wireless IP phone does not get enabled if the Vocera popup is displayed – If you press the application button, the Vocera popup prevents the keypad lock from being enabled. Workaround: Exit the Vocera popup to return to the home screen; the keypad lock will be enabled after the appropriate interval (15, 30, or 60 seconds). (Issue 15237)

• Entering an invalid CUCM IP address on the Telephony > Cisco tab of the Administration Console causes Vocera Server failover – If you enter an invalid Cisco Unified Communications Manager (CUCM) IP address (for example, 10.37.62.5444) on the Telephony > Cisco tab of the Administration Console, and then click Save Changes, the CUCM does not return a signal back before the JTAPI connection times out, causing Vocera Server to failover. Make sure you enter the correct CUCM IP address before clicking Save Changes. (Issue 15306)

• Cisco wireless IP phones do not support SSL – Cisco wireless IP phones do not support SSL, and consequently they cannot connect to the Vocera Server if SSL is enabled on the server. For information on how to allow Cisco wireless IP phones to connect to the Vocera Server when SSL is enabled, contact Vocera Technical Support. (Issue 15365)

• Cisco wireless IP phone switches to speakerphone mode when answering a call by pressing the application button or the Accept softkey button – Cisco wireless IP phones automatically switch to speakerphone mode when you answer a call using either the application button or the Accept softkey button. (Issue 15368)

  Workaround: Use the green Answer/Send button to answer calls instead.

• CUCM configuration changes to Cisco wireless IP phones are not read on the Vocera Server unless you force JTAPI to reconnect – CUCM configuration changes (such as line changes) are not re-read by the Vocera Server unless you force a JTAPI reconnection on the Vocera Server. Currently, the best way to do this is to log into the Vocera Administration Console, go to the Telephony > Cisco page, cut the value from the Last Line field, paste the value back into the Last Line field, and then click Save Settings. (Issue 15370)

• Vocera Connect for Cisco Yes/No softkeys communicate with the Vocera Server on port 8080 even when SSL is disabled – Although Vocera Connect for Cisco generally uses TCP inbound port 80 to communicate with the Vocera Server when SSL is disabled, the Yes/No softkeys for the application are using TCP inbound port 8080, which may not be opened. (Issue 16100)

  Workaround: Enable inbound TCP connections to port 8080 on the Vocera Server. For a list of other ports that need to be opened, see the “IP Port Usage” appendix in the Vocera Infrastructure Planning Guide.

• Messages softkey button not displayed on the Vocera status screen after pressing the application button – If you press the application button to place a Vocera call, the Messages softkey button is no longer displayed on the Vocera status screen. (Issue 16745)

  Workaround: Use the Message softkey button on the Home screen to display the Vocera Message Inbox. However, your system may have configured the Message softkey button to access voicemail messages instead.

• Error not displayed when you try to call a user who has gone off-network – If you try to call a user who has gone off-network, the Vocera Server takes up to 30 seconds before the call attempt times out and the server reports an error. Consequently, if you try to call another user before the Vocera Server is finished trying to make the first call, the second call attempt will fail and you won't see an error for the first call. (Issue 14239)

• Microsoft Excel produces inconsistent output for empty columns when you save to CSV, causing import problems for Vocera. – Microsoft Excel has a known problem in the way it saves data to CSV format. It saves text files in 16-row blocks. If the last column is empty, when you save the file to CSV format Excel may save certain rows with a different number of commas. This causes problems when you try to import the CSV data into the Vocera system. (Issue 10344)

  Here’s Microsoft’s KB article about the problem: http://support.microsoft.com/?kbid=77295.

  Workarounds: Before saving an Excel file to CSV, perform one of the following workarounds:

  • Replace all empty cells in the sheet with a space.

  • Add a dummy last column. In each cell in the column enter a space or a period.