Firmware release 3.1.1.11 applies to any existing B3000 installation (Vocera Voice Server 4.1 SP7 or later).
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.
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:
Remove the battery from the badge, then insert it again.
The screen displays the word vocera.
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.
Badge can occasionally stop communicating for a few seconds. This loss of communication was freqently 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 occassionally 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 situtaion 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 initaiate scanning for a new AP. The badge now scans at a more appropriate interval. (24809)
The badge occassionally 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 privacy mode, audio for a conference call sometimes is played at the volume setting for speaker mode. This situation no longer occurs. (23769)
The following list provides information about known product issues:
Using U-APSD causes the badge to assert and results in stability issues. Do not enable U-APSD at this time.
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. (DE4899)
How to install on a stand-alone server:
Shut down Vocera by selecting Run > Exit on the Vocera Control Panel.
Run the firmware installer: B3000_FWR_Update_3_1_1_11.exe.
When it completes, the installer restarts the Vocera services. The B3000 badges update automatically when they connect to the Vocera Server.
How to install in a clustered server environment:
On the standby cluster node, shut down Vocera by selecting Run > Exit on the Vocera Control Panel.
Run the firmware installer: B3000_FWR_Update_3_1_1_11.exe.
When it completes, the installer restarts the Vocera services.
After the remote restore finishes, the cluster node returns to standby status.
On the active server, shut down Vocera by selecting Run > Exit on the Vocera Control Panel. This initiates a failover, and the cluster node that was previously the standby becomes active. The B3000 badges update automatically when they connect to the new active Vocera Server.
On the new standby node, run the firmware installer: B3000_FWR_Update_3_1_1_11.exe.
When it completes, the installer restarts the Vocera services and the server returns to the standby state.
How to uninstall this firmware release:
To uninstall this firmware release, run the installer again.