This section summarizes the new features in the 4.4.2 release.
Note: When upgrading to 4.4.2 or later from previous versions the initial restore must be done using the “Legacy Restore” function in the VRS Administration Console. Subsequent backup / restore operations will automatically use the new process.
Windows Server 2012 Support – The Vocera Server is now supported on the Windows Server 2012 platform. On Windows 2012, you must use "Run as administrator" to start the Vocera Server and to edit any text files that the server uses. For best results, use the Services window to start the Vocera Server.
The Vocera Report Server, Vocera SIP Telephony Gateway, and Vocera Client Gateway are also supported on the Windows Server 2012 platform. The Vocera Telephony Server requires Windows Server 2008 or 2003.
3rd Party Software Support – The following 3rd party software updates are available with this release:
Tomcat 7.0.52
Apache 2.2.25
MySQL 5.1.73
Firmware build 3.1.0.36 is equivalent to firmware build 175, which was released as a separate firmware pack. Moving forward, B3000 firmware will be numbered with the 3.x.x.x convention.
Mixed Mode encryption now supported – A new badge property, B3.EnableMixedMode, lets you provide Mixed Mode functionality. When this property is set to true, unicast packets are transmitted in AES encryption and Multicast/Broadcast packets are transmitted in TKIP encryption, or vice versa.
PMK Caching can now be enabled – A new badge property, B3.EnablePMKCache, allows you to enable PMK caching, which is supported by many AP vendors. When this property is set to true, whenever a badge roams from one AP to another AP, the badge initially learns the PMK id generated for that specific AP. If the badge finds the same AP again, it sends the PMK id in an Association request packet or a Re-association request packet. When the AP approves the PMK id, the AP ignores the complete EAP packet exchange and goes directly to a four-way handshake. Note that PMK caching is supported with AES-CCMP encryption only.
The following list contains fixes and improvements made to the Vocera Voice product.
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)
Changes in behavior between product versions may require you to modify your configuration or your processes after you install. This section summarizes the changed behavior that you may need to accommodate.
The following changes in behavior occurred in Vocera 4.4.2 and continue in successive releases:
VRS requires reboot after install or uninstall – As of 4.4.2 you must reboot the server after installing or uninstalling the Vocera Report Server.
Confirmation prompt when calling back – When the “Call back” option is selected on a VMI message the genie will now play a prompt – “Okay, calling back” before placing the call. This alerts a user the call back is proceeding and allows time to cancel if the call back was done in error.
Change in speech recognition confirmation threshold on VMI message response – The speech recognition confirmation threshold has been adjusted to reduce accidental false recognitions on the response options played after a VMI message is received. Some users may notice they the genie requests a confirmation frequently (genie says “I think you said…”) as a result of the change. If you have any questions about the change please contact technical support for more information.
Before installing this release, make sure at least one of the following Vocera products is installed:
Vocera Server 4.4 or 4.4.1
Vocera Telephony Server 4.4 or 4.4.1
Vocera SIP Telephony Gateway 4.4 or 4.4.1
Vocera Badge Configuration Utilities 4.4 or 4.4.1
Vocera Client Gateway 4.4 or 4.4.1
Schedule downtime. The following table provides estimated installation times and server downtimes for this service pack. If you install the service pack on a Vocera clustered environment, downtime will be minimal (only seconds per failover) if you follow the installation instructions.
Estimated installation time and server downtime
| Server | Installation Time | Downtime |
|---|---|---|
| Standalone Vocera Server | 20 minutes | 20 minutes |
| Clustered Vocera Server | 20 minutes per node (* Remote restore time varies based on the size of the database). | Seconds per failover |
| Vocera Telephony Server or Vocera SIP Telephony Gateway (single server) | 20 minutes | 20 minutes |
| Vocera Telephony Server or Vocera SIP Telephony Gateway array (multiple servers) | 20 minutes per server | 20 minutes |
| Vocera Client Gateway | 20 minutes | 20 minutes |
After you install the service pack, verify that the Vocera version number has been updated to version "4.4.2". You can verify that the Vocera version number has been updated in the following places:
The following list contains all known product limitations to date:
The tone indicating that the Vocera Smartphone received a Normal and High VMI message is not always loud enough
Users wearing the device at waist level may not realize they have received a message until they look at the Smartphone. (US5211)
Staff Assignment Security options dialog is not disabled when Active Directory is configured
When Vocera Server is configured for Active Directory sign in, the Staff Assignment Security dialog should not be used. Any changes attempted via the setup security option do not take effect.
Mismatched badge and network settings can sometimes cause reduced battery life and/or warm badges
Under some rare conditions, B3000 and B2000 battery life may be degraded due to a mismatch in badge and network settings. If you are experiencing poor battery life or warm badges, contact Vocera Technical Support for assistance.
Problems with Intel/Dialogic software on FAT32 partitions
Vocera has identified issues installing and removing Intel/Dialogic software on FAT32 disk partitions.
It is highly recommended that you install the Vocera Telephony Server only on an NTFS partition.
If you must use FAT32, contact your Vocera Support provider for assistance.
Vocera supports only one ISDN T1 span per VTS
You can install multiple Dialogic analog and digital telephony boards on a single VTS. However, Vocera supports only one ISDN T1 span per VTS. Therefore, if your PBX protocol is ISDN-PRI, do not install more than one Dialogic digital telephony board on the VTS.
Voiceprint authentication
If voiceprint authentication has been enabled on the Vocera system and a user is having trouble logging in, the problem is often that the voiceprint was not recorded properly, or simply did not succeed. In such cases, you should erase the voiceprint, and then tell the user to log in and re-record it. Occasionally, someone will have no trouble logging in immediately after recording, but may have trouble doing so at a later time (when his or her voice has changed slightly). Once again, re-recording the voiceprint is recommended in these cases.
Renaming the data folder
The installation program must be able to rename the \vocera\data folder and create a new data folder during an upgrade. If any application, including Windows Explorer, is pointing to the \vocera\data folder during the upgrade, the rename operation will fail. Vocera must be able to rename this folder to upgrade the data structures properly. If the rename operation fails, the database will be left in an unusable state. If that happens, restore the backup file you created before upgrading.
B3000 and B2000 badges cannot scan all wireless channels when roaming
Scanning all wireless channels can cause performance degradation, so it is not currently supported on the B3000 and B2000. If you specify the B3.ChannelsToScan or B2.ChannelsToScan properties, the B3000 and B2000 scan up to 4 channels while roaming; otherwise, the B3000 and B2000 scan only channels 1, 6, and 11 while roaming.
Badge Updater program scans access point channels 1 through 11 only
Vocera badges use a built-in program called Updater during initial badge configuration. The Updater program scans access point channels 1 through 11 when the badge has not been configured yet. The Updater does NOT scan channels 12 through 14. Consequently, the access point that you use with your badge configuration computer should not use an access point set to channel 12, 13, or 14.
Performing system-level backups
To back up Vocera Server data, make a backup copy of the \vocera\backup folder.
All Vocera data (including messages and learned commands) is stored in the \vocera\backup folder, so you do not need to back up any other Vocera folders.
You should also make backup copies of the following properties files on the Vocera Server and the Vocera SIP Telephony Gateway or Vocera Telephony Server:
\vocera\server\properties.txt
\vocera\config\badge.properties
\vocera\telephony\vgw\vgwproperties.txt
\vocera\dialogic\telproperties.txt
If you are planning to back up Vocera Server data, make sure you do it AFTER the following Vocera Server scheduled processes:
The daily scheduled backup of Vocera data
To schedule backup in the Administration Console, click System in the navigation bar, and then click the Backup tab.
The daily scheduled sweep of Vocera messages
To schedule sweep in the Administration Console, click System in the navigation bar, and then click the Sweep tab.
Vocera Administration Console and User Console must run in separate Internet Explorer sessions
You cannot run the Vocera Administration Console and the User Console in separate tabs of the same Internet Explorer window. You must open a new Internet Explorer session. DO NOT use either File > New Window or File > New Tab.
Internet Explorer 7: Open a new session by launching Internet Explorer from the Start menu or from a shortcut.
Internet Explorer 8 or 9: Open a new session by choosing File > New Session.
Installing Vocera Server on a machine that already has Vocera Badge Configuration Utilities installed
If you try to install the Vocera Server on a machine on which the Badge Configuration Utilities are installed, the installer does not let you specify the drive, locale, or local IP address of the machine. If you need to change those settings, uninstall Vocera Badge Configuration Utilities, reboot the machine, and then install both Vocera Server and Badge Configuration Utilities.
Smartphones and subnet roaming
Unlike the Vocera badge, the Vocera smartphone cannot change its IP address mid-stream when moving from one AP to another on different subnets. Consequently, if you deploy Vocera smartphones you must either have a single subnet where the phones are used or you must enable IP Mobility (also called Layer 3 Mobility) on the WLAN controllers. When IP Mobility is enabled, the Vocera smartphone can roam across subnet boundaries while maintaining its original IP address.
Default gateway required for flat network
If you have a flat network, that is, one without subnets, B3000 and B2000 badges require a default gateway configured on the DHCP server to support broadcasts. This is opposite the behavior of B1000A badges, which do not support broadcasts when a default gateway is specified. (Issue 13512)
Workaround: If you have a flat network environment and a mixed deployment of B3000, B2000, and B1000A badges, insert the IP address of the Vocera Server into the DHCP scope as the default gateway (003 Router option).
VSTG does not support SIP systems that use asymmetric RTP
VSTG does not support SIP systems that receive and send RTP from different UDP ports. VSTG requires symmetric RTP. The following SIP systems support asymmetric RTP and are therefore incompatible with VSTG unless a workaround is implemented:
Rauland Responder 5—Workaround: The Brekeke SIP gateway can be set up to anchor media, which in turn provides the VSTG with a signaling partner supporting symmetric RTP.
Mitel Nupoint voicemail system—Workaround: None.
Administration Console and Report Console problems with JRE 7.0 (1.7)
Administration Console and Report Console both require JRE 6.0 (1.6). If you use JRE 7.0 (1.7), you will encounter security problems with some features that rely on unsigned applets (such as backup/restore operations). In such cases, you will see the following Java warning: "Application Blocked By Security Settings."
Workaround: Choose Edit Site List on the Security tab of the Java Control Panel and add the IP address of the Vocera Server and Vocera Report Server to the exception list.
The following list contains known product issues:
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:
Press Start > All Programs > Internet Explorer.
Press Menu > Tools (option 9).
Select Options (option 3).
Select Connections.
Uncheck the Automatically Detect Settings checkbox.
In the Select Network list, select Work.
Press Done to close the Connections window.
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:
Choose Start > Programs > Vocera > Telephony Server > Dialogic Configuration Manager - DCM.
Click OK in the confirmation dialog box.
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.