Before installing this firmware update, make sure one of the following Vocera products is installed:
This section summarizes the new features in this release.
Bluetooth support
The badge firmware now provides support for Bluetooth headsets. After you pair your headset with any badge, the pairing information is saved in the Vocera User Profile on the Vocera Server, and you do not have to pair your headset again when you change badges. The Bluetooth feature is supported on Vocera Voice Server version 4.3, 4.4, and 5.x !
Speech Zone Fallback
The Speech Zone Fallback feature allows the badge orientation sensor to automatically enable a wider speech zone when the badge is not in an optimal position to pick up speech.
Easier Access to Handset mode (privacy mode)
Press and hold the Select button (the middle button in the set of three buttons along the badge) for three seconds to turn handset mode on or off. Handset mode will only be active for the duration of the call and will return to hands-free mode at the end of the call.
Updated power and transmit tables for ETSI WiFi regulations. (US7161)
New policies for WPA and WPA2 mixed mode operation. (US8895)
The Wi-Fi Alliance has mandated new policies for WPA and WPA2 mixed mode operation with regard to the use of TKIP and CCMP. This release of firmware conforms to those Wi-Fi alliance regulations on WPA/WPA2 mixed mode operation.
Easier access to badge configuration menus. (US10219)
With this release there are now several methods to access the detailed badge menus in the B3000n:
Login reminder. (US7519)
With this release, the B3000n will prompt an end user to log into the badge when the badge is connected to the Vocera Voice Server. The B3000n halo will periodically flash white to remind the end user that the B3000n badge is not currently logged in.
Radio with 802.11a/b/g/n support
802.11a/n support allows the B3000n to operate in the higher 5GHz frequency range, avoiding the congestion and interference in the 2.4GHz range of 802.11b/g. The radio allows use of either or both frequencies, as desired.
Call button halo
The B3000n uses an LED-lighted Call button to indicate the status of the badge, allowing other people to see if you are in a call.
|
Color |
Meaning |
|---|---|
|
Green |
On an active call |
|
Amber |
In DND mode or on hold |
|
Cycle through colors |
Off network |
Orientation sensor
The B3000n badge display contains an orientation sensor that automatically inverts the text on its display when you tilt up the bottom of the badge, making it easy to read the screen. To conserve power, the display is activated only when you press buttons, use menus, or are on a call; otherwise, the display is powered off.
Enhanced roaming performance. (US8381)
Roaming no longer results in a de-authentication event if the badge fails to associate with the new access point for any reason. If the badge fails to associate with the new AP, it remains connected to the current AP and starts scanning.
This section includes installation instructions for the Vocera version 4.1 Firmware Release. This release applies to B3000n badges only and does not apply to B1000, B2000, and B3000.
Prerequisites:
For more information, see the Badge Configuration Guide .
B3N.DisplayBluetooth True
How to install Firmware on Vocera Badges from a standalone Vocera Server
Result: The firmware is automatically downloaded to the B3000n badges after they reconnect to the Vocera Server.
How to install Firmware on Vocera Badges in a Vocera cluster
In a cluster environment, you must install the firmware on the standby server first, followed by the active server. This workflow is designed to create the smallest amount of downtime in your environment and update your badges quickly.
Result: When the Standby becomes active, and the badges connect to it and the firmware is automatically updated on the Vocera Badges.
This will initiate a failover and cause the Standby server to become active.
How to uninstall 4.1 Firmware
The following list contains fixes and improvements made to the B3000n product.
Fixed: The B3000n badge fails to acquire an IP address when connecting to access points that use the "802.11ac wave 2" technology - This includes access points such as Cisco AP1852, Aruba (AP-325 802.11ac wave 2), some Ruckus access points, and possibly other vendors and models. (DE6753, DE6919)
This situation has been fixed in firmware release 4.1.0.
Fixed: Problem displaying the badge serial numbers -If you reset a badge with 4.0.2 firmware to factory defaults prior to performing an over-the-air update, the hardware.properties file is deleted. This results in the badge being unable to display its serial number. (DE6326)
This situation had no workaround, and it has been fixed in firmware release 4.1.0.
Fixed: Support for HT protection mechanisms - The badge fully supports 802.11n HT protection mechanisms.
The following list provides information about known product issues.
The following list provides information about known product issues:
If an incoming call is received while the badge is scanning for a Bluetooth headset, the call may not connect. (DE7945)
If a wired headset is removed while a badge is first booting up, the badge may not detect that the headset has been removed. (DE9062)
Pressing the select button for 4 seconds while in Bluetooth menus does not return the badge to the home screen. (DE8563)
While the badge is scanning in a low SNR area, connecting and disconnecting a Bluetooth headset may interrupt the scanning. (DE8425)
The following list provides information about known product issues in the 4.0.2 code branch
The B3000n badge fails to acquire an IP address when connecting to access points that use the "802.11ac wave 2" technology. This includes access points such as Cisco AP1852, Aruba (AP-325 802.11ac wave 2), some Ruckus access points, and possibly other vendors and models. (DE6753, DE6919)
If you are in privacy mode and "Announce Through Speaker" is enabled, the chime to indicate an incoming urgent message plays at low volume. (24014, 23958)
If the BCU computer is set to a date prior to 1 April 2011, the badge will not download a configuration from it.
Workaround: set the BCU computer to the current date/time. (23661)
Pressing the Call button may result in a mild "popping" sound from the badge speaker.
The sound occurs just before the beginning of the chime, after the Call button is pressed. (22902)
Using the badge in handset mode results in excessive background noise.
The background noise may be as much as 3-4dB higher than the B3000. (21988)
The badge wakes up too slowly from its low power "sleeping" state.
The initial audio may be lost while the badge transitions from sleep. Workaround: pause 1-2 seconds before initiating conversation. (21944)
When using Opportunistic Key Caching (OKC), the B3000n may not roam optimally, possibly resulting in audio gaps during a call.
Roaming will be optimized in a future firmware release. (23086, 23261)
The badge does not fully support 802.11n HT protection mechanisms.
Support will be provided in a future firmware release. (21441)
If you are using UAPSD, the badge may restart while scanning wireless channels, resulting in a dropped call.
Enabling Active Power Save can result in the badge using less power during calls, but it also increases the likelihood that the badge will encounter an error and restart. To enable Active Power Save, set the following property in the badge.properties file: B3N.EnableActiveRadioPowerSave true (22395)