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. (US10405)

Enhanced badge and battery error detection. The badge now checks for additional error conditions, including situations in which you should take either the badge or battery out of service, and plays a message instructing you if you need to take an action.(US10592)

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)

When users boot the badge, they are asked if they want to log in. (US6149)

Logging enhancements help enable Vocera to troubleshoot badge events that occur at customer sites.

• ARP request/response logging is now recorded in log.txt.
• The badge now logs additional information about the reason for disconnections, such as disassociation, de-authentication, and link loss.
• The badge now logs additional debug information for events that cause a reboot.

Enabling WMM no longer requires you to enable U-APSD. Prior to this release, the B3000 firmware required you to enable U-APSD if you wanted to use WMM. This limitation no longer exists. (US6839)

The average VOS score (one metric of audio quality) is now captured more frequently. Prior to this release, the average VOS score was calculated for every call. It is now calculated every 5 seconds. (US150, US7841)

Easier access to the badge configuration menu. The configuration menu is still hidden to prevent badge users from inadvertently accessing it, yet easier for administrators to display (consistently with B3000n behavior). (US5409) The following steps allow you to access the badge configuration menu:

1. Remove the battery from the badge, then insert it again.

   The screen displays the word vocera.

2. Press and hold both the Hold/DND button (the button on top of the badge) and also the Call button (the large button on front of the badge).

   When the badge boots, the screen displays the following top-level configuration menu.

When the badge moves out of range, it now correctly alerts the user. This feature was not working in earlier versions of firmware. (US11528)

The B3000 no longer asserts if it receives 20 text messages with maximum allowed subject and message body length. (DE4425)

The B3000 no longer plays the login prompt when the user is already logged in. This situation occurred sometimes when the user had 20 unread text messages. (DE3441)

Log file lines in the B3000 no longer become out of order when the B3000 is upgrading. (DE7226)

When APSD is disabled, the B3000 no longer indicates that APSD is enabled when it associates. (DE3070)

The badge no longer generates a low SNR event when the SNR is good. (DE196)

The badge no longer incorrectly deletes text messages upon receipt of a long text message (a message with 256 or more characters). (DE4899)

Badge can occasionally stop communicating for a few seconds. This loss of communication was frequently noticeable by the badge asserting, searching for the server, or searching for an access point. This communication issue has been resolved. (18280)

In a Ruckus wireless environment, the badge occasionally disassociates with an AP every 6-7 seconds and then reassociates. This looping association behavior no longer occurs. (24217)

While roaming in some situations, the TX power control is not set appropriately for the intended operating channel. This situation occurred because the channel information for the targeted AP was not stored while roaming. It has now been resolved. (20364)

Badge sends management packets at AP's basic rate before association.

When the badge roams off network (for example, by stepping into an elevator or a low coverage area), the badge waits too long to scan again for an AP. The badge was waiting 12 seconds to initiate scanning for a new AP. The badge now scans at a more appropriate interval. (24809)

The badge occasionally shows a high VOS score (one metric of audio quality) even at times when packet loss is high. The VOS average was inappropriately calculated only once per call, and is now calculated more frequently. The resulting VOS score is more representative. (20328)

When debug statistics are enabled and a background update is in process, the badge could lose its connection to the server. This situation no longer occurs. (24853)

Badges do not alternate between the servers in a cluster setup when the active server is stopped and the Call button is pressed. This situation no longer occurs. (24854)

Advanced logging file name length increased to accommodate four-digit firmware version numbers. The erbin log filename is automatically generated, based in part on the number of the firmware version. The possible filename length has been increased to accommodate four-digit firmware version numbers. (24803)

When the badge is in handset mode, audio for a conference call sometimes is played at the volume setting for speaker mode. This situation no longer occurs. (23769)