Article ID: 000032379

Last Modified Date: 09/07/2023

Access Level: Public

Plantronics Hub Release Notes

September 6, 2023:
Plantronics Hub v3.25.1 (3.25.54065.37203)

Plantronics Hub v3.25.1

What's New

Resolved Issues

Resolved an issue causing loss of audio on an ongoing call when a second incoming call is ringing if the Zoom feature “Sync buttons on headset” is enabled
Resolved an issue causing an update to Hub 3.25 via a policy to fail at 50%
Resolved an issue resulting in a high number of open connections per client at a central HTTPS proxy
Resolved an issue causing the Mute feature to work unreliably on some Zoom calls

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
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.
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.

December 15, 2022:
Plantronics Hub v3.25.0 (3.25.53799.37131)

Plantronics Hub v3.25.0
What's New

Support for macOS Monterey
Security enhancements, please consult Poly Security Center for details

Resolved Issues

Resolved an issue preventing Chrome version 107 and higher from accepting a self-signed certificate
Resolved an issue preventing a FW update from completing on Savi 7300 base unit
Resolved Zoom call control issues with Hub for Mac OS
Resolved an issue preventing hosted pages in Chrome version 104 and higher from connecting to the REST API in HUB
Resolved an issue where the REST API on Ports 32017, 32018 were not available leading to loss of call control with some partner softphones

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
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.
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 the user joins a non-audio Skype for a 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 the 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.

March 10, 2022:
Plantronics Hub v3.24.2 (3.24.53523.36336)

Plantronics Hub v3.24.2
What's New

Resolved Issues

Resolves an issue causing calls to unexpectedly terminate when simultaneously using Cisco Jabber and Cisco Webex
Resolves an issue preventing the “Call on Hold” option being displayed in Plantronics Manager Pro
Resolves an issue that required administrator credentials to modify System Keychain during installation on Big Sur Mac OS
Resolves an issue to enable Zoom as an option in the list of supported Softphone

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
Microsoft Teams mute not always obeying user mute requests via Microsoft Teams GUI (and sometimes via headset) when Hub is running
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.
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.

January 13, 2022:
Plantronics Hub v3.24.1 (3.24.53462.35855)

Plantronics Hub v3.24.1
What's New

Resolved Issues

Resolves an issue causing SAVI 82XX series devices to automatically unmute after selecting Mute on the Teams or Hub GUI

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
Teams mute not always obeying user mute request via Teams GUI (and sometimes via headset) when Hub is running
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.
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.

December 16, 2021:
Plantronics Hub v3.24 (3.24.53436.35631)

Plantronics Hub v3.24
What's New

Includes support to enable/disable a tone when a call is placed on hold for BW 82XX, BW 52XX and BW3XXX series headsets
Includes a setting to enable Pairing mode on BT600
Support for simultaneous USB and Bluetooth connections for Voyager 42XX, Voyager 43XX and Voyager Focus 2 series headsets

Resolved Issues

Resolves an issue that could cause a fatal excetion when starting Hub 3.23 on Windows 7
Resolves an issue preventing the talk time remaining bar from being displayed for Sync 20 on Catalina Mac OS
Improved the accuracy of the talk time remaining bar for Voyager 43XX series headsets
Removed unsupported languages from the list of languages in the drop down
Resolves an issue preventing a call being taken off Hold when using the SwyxIt! Softphone GUI
Resolves an issue preventing a second incoming call from being answered on a Voyager 4300 when using Cisco Jabber on Mojave Mac OS

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
Teams mute not always obeying user mute request via Teams GUI (and sometimes via headset) when Hub is running
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.
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.23

September 2, 2021:
Plantronics Hub v3.23 (3.23.53335.34198)

What's New

Includes support for Poly Voyager 4300 series headsets
Added a prompt to unplug the USB cable and power cycle a Poly Sync Series device when changing the HD voice setting
Implemented call control support for Cisco WebEx

Resolved Issues

Resolves an issue that could cause a crash when polling Hub for Independent Volume Control setting
Resolves an issue with removing a call from Hold when using the Swyxit softphone UI
Resolves an issue with some laptops with refreshing the Mute icon in the system tray
Removes incorrect language options for Poly Sync 20

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
Teams mute not always obeying user mute request via Teams GUI (and sometimes via headset) when Hub is running
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.
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.22.2 – Windows Only
August 5 2021:

Plantronics Hub v3.22.2
What's New
Resolved Issues

Resolves an issue preventing non-English language Windows users from updating v3.22.0 and v3.22.1 of Hub to a later version

Known Issues

When updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later
Teams mute not always obeying user mute requests via Teams GUI (and sometimes via headset) when Hub is running
Call control fails to work correctly for all Poly headsets when using Cisco Webex

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.
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 a 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.22.1

July 15, 2021:
Plantronics Hub v3.22.1

What's New

Implemented support for Encore Pro 515/525/545, DA75 and DA85

Resolved Issues

Resolved an issue that prevented Call Control from working with Zoom

Known Issues

Teams mute not always obeying user mute requests via Teams GUI (and sometimes via headset) when Hub is running
Call control fails to work correctly for all Poly headsets when using Cisco Webex
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.
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 the 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.22.0

June 7 2021:
Plantronics Hub v3.22.0 (3.22.53244.32743)

What's New

Implemented support for Savi 7300, Voyager Focus 2 and BT700
Implemented support for Cisco Webex Softphone
Security enhancements, please consult Poly Security Centre for details

Resolved Issues

Resolved a connectivity issue when using IPv6 proxy
Resolved an issue that caused an incorrect battery level to be displayed when connected to BT600
Resolved an issue that prevented BW5200 from completing a FW update
Resolved an issue that could cause a SAVI 7300 and SAVI 82XX series bases to become non-compliant after a FW update
Resolved an issue that caused an interruption of a FW update on Sync 20

Known Issues

Call control fails to work correctly for BW5220, BW3200 and BW520 headsets when using Cisco Webex
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.
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.21.0

February 4 2021:
Plantronics Hub v3.21.0 (3.21.53118.27704)

What's New

Implemented support for Poly Sync 40

Resolved Issues

- Resolves an issue with Avaya IX Workspace where a call is unexpectedly put on hold when a second call is made to a BLA device

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

November 3, 2020:
Plantronics Hub v3.20.0 (3.20.53032.23105)

What's New

Implemented support for Poly Sync 20

Resolved Issues

Resolves an issue on Mac OS which prevented independent volume control of media and telephony on mono versions of BW32XX, BW72XX, BW82XX headsets

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

August 20, 2020:
Plantronics Hub v3.19.0 (3.19.52957.19169)

What's New

Implemented Acoustic Event reporting support for Savi 8210 and Savi 8220 products (firmware update required)

Resolved Issues

- Resolves an issue causing an incorrect headset serial number to be displayed when connected to a D200 dongle
- Resolves an issue preventing Thai and Indonesian from appearing in the Language drop down for BW8225 headsets
- Resolves an issue causing excessively large DeviceManager log files when using Hub 3.18 and Cisco Jabber 12.5.1

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

June 30, 2020:
Plantronics Hub v3.18.0 (3.18.52885.14653)

What's New

Implemented support for Poly EagleEye Mini Camera – device will now appear in Plantronics Manager Pro inventory reports (there are no settings or firmware updates for EagleEye Mini hence these are not supported)
Implemented support for independent volume control of media and telephony on Blackwire 3300 Series, Blackwire 7225, BW8225 and MDA500 QD series devices

Resolved Issues

Resolves an issue where a call is unmuted when receiving a second unanswered call

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