Plantronics + Polycom. Now together as logo

Shopping Cart

Product Quantity Price Subtotal
Cart Subtotal

Plantronics Hub Release Notes

Article ID :
000019530
Plantronics Hub v3.16.1
Mar 12, 2020
Plantronics Hub v3.16.1 (3.16.52791.9293)

What's New
  • Added support for Calisto 5300 Speakerphone
  • Added support for macOS Catalina (10.15)
  • Added Notarization support for all MAC OS X deliverables, hub can now be installed without pop up warnings asking for user permissions
  • Added DFU support for a DA90 while connected to an MDA400 QD Series
  • Added support for Avaya IX Workplace (Windows)
Resolved Issues
  • Resolves issue that prevents some users from updating the language on a Savi 8200 headset
  • Resolves issue which could cause Hub for Windows to crash when unplugging/replugging a headset while using a third-party developed softphone integration
  • Resolves issue on Savi 8200 UC where a FW update notification was displayed when the device was already updated to the latest version
  • Resolves issue that intermittently delayed Hub from authenticating after Windows woke from hibernation
  • Resolves intermittent issue that could cause Hub for Mac to become unresponsive
Known Issues
  • When using some softphones, ignoring a call while a Calisto 5300 is muted can result in the loss of mute synchronization between the speakerphone and Windows/Hub
  • When using Zoom for macOS the headset call control button may not work reliably for the first call.  If this occurs the Zoom GUI can be used.  Call control using the headset button will work reliably for subsequent calls.
  • For MDA200 and MDA400 QD Series, firmware updates are available using Plantronics Hub for Windows only. Plantronics Hub for Mac does not support firmware updates for these devices.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub for Windows v3.16
Feb 27, 2020
Plantronics Hub v3.16.0 (3.16.52777.8525)

What's New
  • Added support for Calisto 5300 Speakerphone
  • Added DFU support for a DA90 while connected to an MDA400 QD Series
  • Added support for Avaya IX Workplace (Windows)
Resolved Issues
  • Resolves issue that prevents some users from updating the language on a Savi 8200 headset
  • Resolves issue which could cause Hub for Windows to crash when unplugging/replugging a headset while using a third-party developed softphone integration
  • Resolves issue on Savi 8200 UC where a FW update notification was displayed when the device was already updated to the latest version
  • Resolves issue that intermittently delayed Hub from authenticating after Windows woke from hibernation
Known Issues
  • When using some softphones, ignoring a call while a Calisto 5300 is muted can result in the loss of mute synchronization between the speakerphone and Windows/Hub
  • For MDA200 and MDA400 QD Series, firmware updates are available using Plantronics Hub for Windows only. Plantronics Hub for Mac does not support firmware updates for these devices.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.15
Nov 2019
Plantronics Hub v3.15.0 (3.15.52676.3261)

What's New
  • Added support for D200 DECT Dongle
  • Added support for Zoom Meetings in Plantronics Hub for Mac
Resolved Issues
  • Resolves issue that prevents some devices from starting a FW update if the battery life was less than 50%
  • Resolves issue which could cause Plantronics Hub to crash if the Soundscaping feature is disabled 
  • Resolves issue which could cause Plantronics Hub for Mac to crash when unplugging a BT600
  • Resolves issue preventing disabled softphone settings from being retained when restarting Plantronics Hub
  • Resolves an incorrect link to the release notes for Savi 700 Series headsets
Known Issues
  • When using Zoom for macOS the headset call control button may not work reliably for the first call.  If this occurs the Zoom GUI can be used.  Call control using the headset button will work reliably for subsequent calls.
  • Plantronics Hub may become unresponsive when running on macOS Catalina (10.15)
  • For MDA200 and MDA400 Series, firmware updates are available using Plantronics Hub for Windows only. Plantronics Hub for Mac does not support firmware updates for these devices.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset and quit and re-start Plantronics Hub.
  • When using My Habitat Soundscaping, users must manually turn off other audio streams, including music, podcasts and calls if the softphone is not supported by Plantronics Hub.
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.14.1
September 2019
Plantronics Hub v3.14.1 (3.14.52589.47665)

What's New
  • Security Update – please refer to the Polycom Security Center for information about known and resolved security vulnerabilities.
Resolved Issues
  • Resolves issue with Microsoft Skype for Business and/or Microsoft Teams calls being randomly placed on hold.  Further details on simultaneously running both Microsoft Teams and Microsoft Skype for Business can be found here
Known Issues
  • For MDA200 and MDA400 Series, firmware updates are available using Plantronics Hub for Windows only. Plantronics Hub for Mac does not support firmware updates for these devices.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset and quit and re-start Plantronics Hub.
  • When using My Habitat Soundscaping, users must manually turn off other audio streams, including music, podcasts and calls if the softphone is not supported by Plantronics Hub.
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.14.0
Aug 9, 2019
Plantronics Hub for Windows/Mac v3.14.0 Release (Version 3.14.0 | Build 47665)

What's New
  • Added support for Zoom Meeting client. The Zoom API does not support the ability to end meetings directly from the headset, the client UI needs to be used. Further details can be found here
  • Added support for Plantronics Manager Pro to report Microsoft Teams calls separately from Microsoft Skype for Business
  • Added a new "Mute On/Off Alerts" setting for SAVI 8200 Series
  • Removed support for end-of-life softphones, further details can be found here.  Due to customer feedback, support for Cisco IP Communicator (CIPC) will continue.
  • Added security update. Refer to the Polycom Security Center for information about known and resolved security vulnerabilities.
Resolved Issues
  • Resolved issue so that Hub is forced to re-authenticate if the anonymization configuration has changed
  • Resolved issue which caused Spokes3G SDK to crash on MacOS when exiting Avaya Equinox
  • Resolved issue to prevent users being removed from LDAP groups when the LDAP server is not reachable
  • Resolved issue that caused Hub to crash during a FW update of Voyager 5200 UC and Voyager Focus UC when more than one instance of Cisco Jabber is running
  • Resolved issue preventing a language update from English to Norwegian if the Firmware Policy Deployment Type = Automatic on Hub
  • Resolved issue to ensure that the audio quality options in Hub are updated to reflect those of a newly subscribed DECT headset
  • Resolved issue with Hub for Mac OS to ensure all LDAP group members are correctly identified
  • Resolved issue that caused a crash when updating from V3.12.0 to V3.13.2 on Mac OS
Known Issues
  • For MDA200 and MDA400 Series, firmware updates are only available for Windows using Plantronics Hub for Windows.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping, audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset, quit and re-start Plantronics Hub
  • When using My Habitat Soundscaping, if the softphone is not supported by Plantronics Hub, users must manually turn off other audio streams, including music, podcasts and calls
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change
  • On the MDA220 (Product ID 0xAD04), the serial number is  reported incorrectly in Plantronics Hub for Windows and Mac. It is also  inaccurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware updates for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not work reliably during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON, yet they do not work.
  • When using the call button on the Avaya Communicator 2.1 to flash between an active call and a call on hold, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.13.2 (3.13.52516.41952)
June 2019
Plantronics Hub for Windows/Mac v3.13.2 Release

Resolved Issues
  • Improves authentication logic for more reliable authentication with Plantronics Manager Pro tenants.
  • A dialogue box is now shown, that instructs users to close Skype for Business when performing a firmware update with Savi 400 and 700 series devices when multiple devices are connected to the computer.
Known Issues
  • For MDA200 and MDA400 Series, firmware updates are available using Plantronics Hub for Windows only. Plantronics Hub for Mac does not support firmware updates for these devices.
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature.
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset and quit and re-start Plantronics Hub.
  • When using My Habitat Soundscaping, users must manually turn off other audio streams, including music, podcasts and calls if the softphone is not supported by Plantronics Hub.
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.13.1
April 18, 2019
Plantronics Hub for Windows/Mac v3.13.1 Release

Resolved Issues
  • Resolves issue in Plantronics Hub for Windows v3.13.0 with some softphones, including Cisco Jabber and Swyx SwyxIt!, that resulted in the loss of remote call control.
Known Issues
  • Plantronics Manager cannot update Plantronics Hub v3.12 clients using the Plantronics Manager software update policy feature. Plantronics Hub v3.12 must first be uninstalled, and the new version (Plantronics Hub v3.13 or higher) must be deployed to host systems on the tenant. Plantronics Hub v3.11 and lower are not affected and can be updated using the software update policy feature. 
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset and quit and re-start Plantronics Hub.
  • When using My Habitat Soundscaping, users must manually turn off other audio streams, including music, podcasts and calls if the softphone is not supported by Plantronics Hub.
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.
Plantronics Hub v3.13.0
March 18, 2019
Plantronics Hub for Windows/Mac v3.13.0

What's New
  • Adds support in Plantronics Manager Pro for Genesys PureCloud for macOS.
  • Added support for AppLocker. Plantronics Hub will no longer install files to C:\ProgramData folders.
  • Pseudonymization Feature Added to Prevent Collection of Username and Hostname
  • Starting with 3.13, the Username and Hostname (two required pieces of personal data) will be encrypted by default.
  • Pseudonymization happens at the client; real username and hostname does not leave company network 
Resolved Issues
  • Resolved issue with Savi 8200 (pid ac2b) that prevented the device from authorizing with a Plantronics Manager Pro tenant.
  • Resolves issue on Plantronics Hub for Mac v3.12 that could result in variable usage of memory.
  • Resolves issue on Windows 10 systems for users with Genesys WDE 8.5.127.06 client that resulted in a lost audio and crash of Plantronics Hub.
  • Resolves issue with Plantronics Hub v3.12 on Windows 10 (64-bit) that caused softphones that had been unchecked from the Softphones page to become checked again on Plantronics Hub re-open. 
  • Resolves issue on Plantronics Hub for Mac that caused troubleshooting mode to remain on.
  • Resolved issue with My Habitat Soundscaping that caused the My Habitat Soundscaping system tray options to become out of synchronization after user placed or removed a sensor-based headset.
Known Issues
  • On Plantronics Hub for Mac, when starting My Habitat Soundscaping audio is automatically routed to the default audio device. Users must manually change their default audio device to the headset and quit and re-start Plantronics Hub.
  • When using My Habitat Soundscaping, users must manually turn off other audio streams, including music, podcasts and calls if the softphone is not supported by Plantronics Hub.
  • At the end of a call, My Habitat Soundscaping may demonstrate a brief volume level change.
  • On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac. It is also not accurately reported to Plantronics Manager Pro.
  • Lost audio connections may occur if the BT600 is unplugged and then plugged back in. Users must shut down Plantronics Hub and re-start it to regain audio connection.
  • During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.
  • Support for local firmware update for BT300 (Product ID = 417) is not available.
  • On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.
  • On Plantronics Hub for Mac, the call end button on the headset may not reliably work during a softphone call on Voyager 8200 with a BT600 and on Blackwire C320, C720.
  • Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.
  • After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.
  • When using the call button to flash between an active call and a call on hold using Avaya Communicator 2.1, both calls may be put in a hold state and may require using the softphone user interface to resume the call.
  • To ensure accurate data in Plantronics Manager Pro reports, customers using Avaya Equinox should open the softphone client prior to opening Plantronics Hub for Windows.

< Previous 10 | Next 10 >()

Filter by