Before installing this firmware update, ensure that one of the following Vocera products is installed:
This section includes installation instructions for the Vocera version 4.3.3 Firmware release. This release applies to B3000n badges only and does not apply to B1000, B2000, and B3000.
If you do not have the standalone version of BPE, contact Vocera Customer support or open a case in the Support Portal. You will receive an email with a KB article that contains a link to download the executable file after your request is processed.
To update the badge properties, perform the following tasks:
This directory is the location where you saved the 5.3.1 BPE executable.
The Badge Properties Editor opens.
For specific instructions on how to configure your badge using BPE and the new 4.3 features, refer to Vocera Device Configuration Guide.
To install Firmware on Vocera Badges from a standalone Vocera Server, perform the following tasks:
A confirmation dialog box appears.
The dialog box closes, and the Control Panel also closes.
Result: The Firmware is automatically downloaded to the B3000n badges after they reconnect to the Vocera Server.
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.
To install firmware on Vocera Badges in a Vocera cluster, perform the following tasks:
A confirmation dialog box appears.
The dialog box and the Control Panel closes.
This initiates a failover and cause the Standby server to become active.
To uninstall 4.3.3 firmware, perform the following tasks:
Vocera undertakes interoperability testing with Wireless LAN equipment from several vendors. The following table lists the specific Wireless LAN controllers, Access Points, and software versions with which the B3000n firmware has been tested.
For guidance as to whether different versions of Wireless LAN controller, Access Points or software versions would be preferred, consult with the respective vendors.
| Vendor | Model Type | Model Number | Firmware Version |
|---|---|---|---|
| Aruba | Controller Model | 3400 | 6.4.2.8 |
| AP Model | AP105 | - | |
| Avaya | AP Model | WAP9132 | 8.3.7 |
| Cisco | Controller Model | 2500 | 8.3.122.0 |
| AP Model | 2600/2700 | - | |
| Extreme | Controller Model | Virtual Controller | 10.41.02.0014 |
| AP Model | AP3935i | - | |
| Ruckus | Controller Model | ZD1200 | 9.13.3.0.106 |
| AP Model | R510 | - |
This section summarizes the new features in the 4.3.x release and contains all the features previously delivered in Firmware.
Internal VMC supports both SHA1 and SHA2 certificates.
Validation of SHA384 and SHA512 hashed certificates when used in conjunction with Wi-Fi authentication is now supported in the B3000n.
Multicast diagnostic badge property B3N.MulticastDebug [true | false] enables the screen to display the Multicast status, and the number of multicast audio packets received when the badge joins a multicast broadcast. The default value of multicast diagnostic badge property is false.
When the battery reaches the threshold limit, the low battery prompt plays every 1 minute during a call. If the call is longer than 1 minute, the low battery announcement is played. Then the 1-minute timer starts again during the active call until the badge shuts off.
When a B3000n is unable to stay associated with the network and loses the connection to the Vocera Server for more than 60 seconds, it returns to the First Ping state to re-establish the session.
The badge property B3N.ExtendServerHello [true | false] enables the badge to authenticate with Free Radius Authentication Server and Fortinet Authentication Server.
Bluetooth error handling commands
Some Bluetooth headsets will issue commands that are unique to Apple devices, the B3000n will now respond with error messages when it receives these Apple specific commands.
Certificates used by the B3000n badge are visible through badge logs and internal hidden menu.
SHA256 Certificate support
Validation of SHA256 hashed certificates when used in conjunction with Wi-Fi authentication is now supported in the B3000n.
Audio prompts in the B3000n badge are now using the same persona as those prompts in the V5000 Smartbadge and the Vocera Genie.
The B3000n was validated by the CMVP to comply with the FIPS 140-2 standard for cryptographic security and was granted certificate # 2619 in April 2016.
In early 2018 a KRACK vulnerability in the WPA2 supplicant was resolved and integrated into the 4.3.1.17 firmware. The WPA2 supplicant makes use of a cryptographic module that is included in the FIPS 140-2 validation program, and the changes integrated into the WPA2 supplicant will be re-submitted to the CMVP for re-validation in the future.
To maintain the integrity of the FIPS 140-2 certification, the B3000n firmware 4.3.2.3 contains both the KRACK mitigation for the WPA2 supplicant and the validated FIPS cryptographic module. If FIPS mode is enabled in the 4.3.2.3 firmware, the original FIPS cryptographic module will be activated. If FIPS mode is not enabled in the 4.3.2.3 firmware, the updated cryptographic module containing the KRACK mitigation for the WPA2 suppliant is activated.
5GHz Channels Support
Support for additional channels 120,124, and 128, for operation with the US locale.
Voice Server version signal increments should not force firmware downloads in the foreground.
Periodic date and time stamp in badge logs to assist with reading badge logs are included in this release.
Enhanced Battery Statistics
B3000n badges are enhanced with the 4.3 firmware to record the serial number of a battery that is inserted into the badge. The B3000n badges will also record the number of charge cycles that an inserted battery has completed. This information will be reported to the Vocera Server in a future release.
Dynamic WLAN Profiles
This feature is intended for use in campus environments where B3000n badges may frequently be transported between locations that have different WLAN connectivity requirements. The B3000n badges store up to 4 profiles for WLAN connectivity and dynamically switch between them. Each profile may contain different WLAN connectivity parameters and permit the B3000n to operate in different WLAN environments without manual intervention. This feature also eases the transition of B3000n badges when undertaking WLAN migration.
IGMP Optimization
B3000n badges send IGMP leave/join requests more frequently when roaming. This feature will assist the convergence of Protocol Independent Multicast (PIM) tables when B3000n badges are moving during broadcast calls.
Proactive Scanning
B3000n badges scan continually during an active call to proactively determine the best candidate access point (AP). This feature will speed up the roaming decisions when a user is on an active call while moving.
Multicast Session IP on the Vocera Badge
View the current Multicast Session IP address that your badge is using in real time from the Vocera Badge Menu.
The following list contains fixes and improvements made this firmware release and the B3000n product.
There are no new fixes in this release.
When roaming between different vendor's access points with 802.11r enabled, the B3000n badge becomes deauthorized. This issue has been addressed. (DE6797).
The B3000n may fail PEAP authentication with Cisco ACS when an unexpected MSCHAPv2 challenge packet type is received. With this fix, B3000n authenticates successfully. (DE10950)
The B3000n no longer reports “Address already in use” when roaming during a broadcast call while in transmit mode. This issue has been addressed. (US18730)
Audio artifacts may be heard when releasing the volume buttons if connected to a Bluetooth headset. Audio artifacts are no longer heard. (DE8148)
When the B3000n is connected to a Bluetooth headset, occasionally button press events are missed. Button presses are no longer missed. (DE8883)
Setting the badge property B3N.HandsetMode to false, is ignored where the B3000n badge indefinitely attempts to connect to a Bluetooth headset and displays the message “Connecting ...”. This issue has been addressed. (DE11340)
The following list contains known issues in this firmware release and the B3000n product.