Before installing this firmware update, make sure one of the following Vocera products is installed:
This section summarizes the new features in this release.
Updated power and transmit tables for ETSI WiFi regulations. (US7161)
New policies for WPA and WPA2 mixed mode operation.
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. (US8895)
Easier access to badge configuration menus.
With this release there are now several methods to access the detailed badge menus in the B3000n: (US10219)
Login reminder.
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 pink or voilet to remind the end user that the B3000n badge is not currently logged in. (US7519)
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. 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. (US8381)
The following list contains fixes and improvements made to the B3000n product.
Badge may display misconfiguration warning unnecessarily.
In some situations, a badge may display the warning "scan due to configured Auth algo WPA-PSK and Enc AES-CCMP is not matching" warning, even though the badge and the access point have the same configuration. The badge should display this warning only when its configuration does not match the access point configuration. (DE2470)
When an Access Point is configured to require 802.11w Management Frame Protection, the B3000n badge may still attempt to associate even if 802.11w is not enabled in the badge. (DE2446)
In some situations, the badge inappropriately prompts you to log in.
The B3000n would play out the invitation to log in to the badge when it was already logged in and had 20 text messages waiting. (DE3441)
The B3000n would sometimes write the incorrect date and time in system history event logs. (DE2577)
In some situations, the B3000n badge fails and restarts repeatedly.
The B3000n badge may assert repeatedly if it receives messages containing over 30 characters in the subject line and 256 characters in the message body. (DE4426)
If the badge receives a long text message (256 or more characters), it deletes that message and all previous messages when it restarts.
After receiving a long message and then restarting (for example, after being powered off or after a failure), a badge signal inadvertently causes the server to delete all messages. The badge should preserve these messages when it restarts. (DE4420)
Missing support for Kuwait and Oman.
The B3000n omitted to include country codes for Kuwait (KW) and Oman (OM). (DE4810)
The B3000n battery consumption may remain high after a call has been completed.
The battery consumption now returns to the lower standby state after a call is completed. (DE4137)
The B3000n badge may not be able to associate with an access point when both 802.11w and 802.11i are enabled. (DE2572)
When viewing the RSSI the B3000n may display a value 10dBm lower than the B3000.
Due to a difference in the radio calibration offset, the B3000n may display a lower value than the B3000 even though the received signal power level is the same. The B3000n now displays an RSSI value that is consistent with the B3000 RSSI value. (US5255)
Off-network notification
The B3000n now plays a notification tone when the badge leaves WiFi coverage. (US11171)
The badge occasionally fails to recognize pressing and holding the Select, Scroll Up, or Scroll Down buttons.
These button events are now recognized and processed correctly. (20897)
If a user presses the Call button while the badge displays "Searching For Server" during a failover, the badge may not connect to the new active node.
This corner case is now handled correctly. (23748)
The BPE does not successfully change the value of the WirelessBand badge property.
The BPE now correctly saves whatever value you specify for the WirelessBand property. (20760)
The following list provides information about known product issues:
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)
If you are in privacy mode and "Announce Through Speaker" is enabled, the chime to indicate an incoming broadcast or urgent broadcast plays at low volume. (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)