• The B3000n was validated by the CMVP to comply with the FIPS 140-2 standard for cryptographic security and was granted certificate # 4047 in October 2021.
• B3000n now uses IGMP version 2 by default instead of version 3.

This release does not have any new features.

This release does not have any new features.

• New Vocera Manufactured Certificates (VMC) Support

  Internal VMC supports both SHA1 and SHA2 certificates.

  Note: To obtain the new VMC, contact Vocera Technical Support.

• SHA384 and SHA512 Certificate Support

  Validation of SHA384 and SHA512 hashed certificates when used in conjunction with Wi-Fi authentication is now supported in the B3000n.

• Multicast Diagnostic Capability

  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.

• Low Battery Prompt

  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.

• First Ping Optimization

  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.

• B3000n Badges support for Fortinet Authentication Server

  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.

• Certificate visibility in B3000n

  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

  Audio prompts in the B3000n badge are now using the same persona as those prompts in the V5000 Smartbadge and the Vocera Genie.

• FIPS 140-2 Validation

  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.

  Note: The FIPS mode in 4.3.2.3 firmware has not been updated to support the 5Ghz channels (120,124,128). This is to maintain the integrity of the FIPS security module. If these channels are enabled, it may cause the B3000n to enter an association loop until these channels can be removed. (B3SF-1466)

• 5GHz Channels Support

  Support for additional channels 120,124, and 128 for operation with the US locale.

• Firmware Upgrade

  Voice Server version signal increments should not force firmware downloads in the foreground.

• Badge Logs

  Periodic date and time stamp in badge logs to assist with reading badge logs are included in this release.

  Note: The correction of the RF noise floor in the B3000n through the resolution of B3SF-135 may impact roaming. If the Badge Property Roaming Policy has been changed from its default, please carefully consider the impact this may have on roaming activity. If you are unsure of the impact, please consult with Vocera Technical Support.

• 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.

  Note: It is strongly recommended that customers consult with their Vocera Technical Representative before enabling this feature.

• 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.

• Badge locked up due to scan loop when proactive scan is disabled. (B3SF-1823)

• During an upgrade of Firmware to version 4.3.3.16, some Badges did not complete the upgrade and got stuck in an update and reboot loop. (B3SF-1786)

  If you have upgraded your Firmware to 4.3.3.16, contact Vocera Support for instructions to upgrade to 4.3.3.18.

• B3000n badge did not work with the new Kingstate headset. This problem is resolved by Firmware 4.3.3.16. (B3SF-1739)

• When WPA mixed mode was used on Avaya, the badges failed to generate temporal keys. (B3SF-1459)
• When FIPS was enabled, and the Reset to default option was used, the badge asserted WLANSetGet256Char error. Workaround: Reboot the badge. (B3SF-1463)
• When FIPS was enabled, and the 4096-bit certificate was used with PEAP authentication, the badge asserted @tls.c:2586:WriteClientKeyExchange error. (B3SF-1465)
• B3000n badge did not associate with Meraki AP on the 802.11w profile. (B3SF-1471)
• B3000n badge did not associate with the 1x profile, under EAP-FAST authentication on Meraki. (B3SF-1472)
• B3000n badge did not associate with the 802.11r profile on Meraki. (B3SF-1473)
• B3000n badge did not associate with a mixed profile (AES+TKIP) on Avaya. (B3SF-1474)
• Genie sounded distorted on B3000n when BlueParrott Bluetooth headset connected. (B3SF-1475)
• B3000n badge was unable to associate with WLAN with FT enabled for Extreme Networks AP. (B3SF-1476)
• B3000n badge did not authenticate Free Radius Authentication and Fortinet Authentication Server. (B3SF- 1563)

There are no new fixes in this release.

• 802.11r keys were not always installed correctly during a four-way handshake when authenticating over the Distribution Switch (OverTheDS) (B3SF-1407)
• 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 DisplayShortCallerName is set to true. (B3SF-1411)
• 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. (DVCS-425)
• 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. (DVCS-409)
• 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 B3N.UseAESCipher set to true. DVCS-426

• When roaming between different vendor's access points with 802.11r was enabled, the B3000n badge was deauthorized. This issue has been addressed. (DE6797).
• The B3000n sometimes failed PEAP authentication with Cisco ACS when an unexpected MSCHAPv2 challenge packet type was 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)