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.2.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.2.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 release and contains all the features previously delivered in Firmware.
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.
When a user is on DND or rejects a call by pressing DND, the FirstName, and the LastName of
the person leaving a message is displayed even though only the
FirstName and LastInitial should be displayed when the badge property
In some instances, B3000n badges upgrade their firmware each time they are powered up, even though there is no need to do so. (B3SF-137)
With an Opportunistic Key Caching (OKC) profile, sometimes a B3000n badge sends a pairwise master key ID (PMKID) during the initial association request. (B3SF-1417)
An SFS (Search For Server) condition may sometimes occur if the B3000n badge does not handle an ARP response correctly. (B3SF-1398)
802.11r roams may sometimes fail a four-way handshake due to the Fast BSS Transition IE (FTIE) mismatch. (B3SF-1407)
In standby mode, sometimes a B3000n badge does not respond correctly to a Groupkey exchange. (B3SF-1401)
EAP PAC authentication may expire when both Cisco ACS5.8 and Cisco ACS5.4 are in a cluster and, authenticated PAC provisioning is enabled. (B3SF-1400)
B3000n badges may enter an SFS state after checking for SNR just after an 802.11r FT authentication fails. (B3SF-144)
The B3000n badge may record an incorrectly low noise floor, resulting in the SNR value being approximately 6dBm higher than it should be. Which in turn may lead to sticky roaming behavior. (B3SF-135)
The four-way handshake may fail for a Temporal Key Integrity Protocol (TKIP) profile when the B3000n is associating with an Access Point. (B3SF-124)
Cisco ACS 5.8 may send an incorrect error code for EAP-FAST when attempting to delete the PAC file. Vocera has implemented a workaround to accommodate this behavior in B3000n firmware. (B3SF-125)
When 802.11r FT is enabled, a four-way handshake fails with Cisco WLC 8.3. (B3SF-134)
When a Bluetooth headset is connected, sometimes there is a Genie audio delay that exceeds 1 second. (B3SF-150)
When the multi-profile scan is enabled on multiple SSIDs, with both 2.4 GHz and 5GHz bands selected (Ex: ABGN), some 5GHz channels probe request sets 802.11 B rates. (B3SF-161)
When channel switch announcement is received on a Non-DFS channel, the B3000n may sometimes assert. (B3SF-136)
B3000n badges may go into a Manufacturing Mode if the badge properties file is corrupted. (DE12409)
When a B3000n badge is switched from one Cisco ACS to another Cisco ACS within the same ACS cluster, proxy auto-config (PAC) files are not deleted automatically for EAP-FAST. This is a non-standard configuration, but Vocera has added a mechanism to support this configuration. (DE15906)
When a B3000n disassociates from an AP and then reconnects, any roam trigger event immediately after the disassociation will trigger a scan. (DVCS-427)
Cisco ISE 2.0 and later, have deprecated support for the RC4 cipher when PEAP or EAP TLS
authentication method is used. The B3000n can be configured to use only AES when
authenticating with Cisco ISE 2.0 or later through the use of the badge property
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.
The following provides information about known product issues:
In very rare instances the B3000n badge may enter a loop when scanning 5GHz channels after a failed roam attempt. A workaround is available for this issue and is not included in the 4.3.1.17 firmware. Contact Vocera Technical Support if you notice this symptom in your environment. (B3SF-1415).
The following list provides information about known product issues:
An SFS (Search For Server) condition may sometimes occur if the B3000n badge does not handle an ARP response correctly. (B3SF-1398)
On rare occasions when 802.11k and 802.11r are enabled together, a timing error in the scan and roam operation causes the B3000n badge to fail the fast transitioning (FT) roam. Workaround: Disable 802.11k. This issue will be resolved in a future release. (DE13047)
When proactive scanning is enabled, the improved scanning performance may have a small impact on battery lifetime. Workaround: If this is found to impact the end user experience, proactive scanning can be disabled through a badge property. Contact Vocera Customer Support for instructions. (DE13534)
On rare occasions the Cisco Wireless LAN Controller sends a deauthorization command to the badge with message type 3, reason code 7. Workaround: This problem is believed to be an error with the Cisco FT implementation which is under investigation by Cisco through defect CSCvd96678. Contact Vocera Customer Support for more information. (DE13062)
Additional WLAN profiles created through the BPE, beyond the default Wireless profile, cannot not encrypt the credentials for PSK or WEP authentication types. Workaround: This is a limitation of the initial release of this BPE and will be resolved in a future release. (DE13475)
If Bluetooth is enabled in a WLAN profile and a different WLAN profile without Bluetooth is invoked, the B3000n may assert. Workaround: Ensure that the WLAN profile being invoked is Bluetooth enabled. (DE10790)
During proactive scanning if a B3000n badge determines the current AP is the best candidate then receives a beacon from that AP, the B3000n may assert. Workaround: There is no workaround at this time. (DE11019)
If a user is in an active call with a wired headset and removes the wired headset, the call may not switch to the Bluetooth headset. Workaround: Manually reconnect the Bluetooth headset. (DE11169)
On rare occasions with a very low battery, the B3000n badge may shutdown ungracefully and will not write log files. Workaround: There is no workaround at this time. (DE11472)
When using a Bluetooth headset, on calls over 10 minutes in length, on rare occasions the B3000n may assert. Workaround: There is no workaround at this time. (DE11541)