PLANTRONICS HUB RELEASE NOTES
ARTICLE ID:
000019530
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.
Plantronics Hub v3.17.0
May 28, 2020:
Plantronics Hub v3.17.0 (3.17. 52868.13817)
What's New
Resolved Issues
Resolves issue causing microphone to unmute when rejecting a Cisco Jabber call while user is muted in Cisco WebEx Meeting Centre
Resolves issue where Calisto 5300 battery level was incorrectly report as a percentage instead of in Hours and Minutes
Resolves an issue where the wrong image was displayed for BT600 when connected to a Calisto 5300
Resolves an issue preventing a policy locking the settings for a Calisto 5300
Removed a checkbox to dismiss a persistent firmware update reminder
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 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 for Windows/Mac
https://www.plantronics.com/us/en/support/downloads-apps/hub-desktop
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 Release
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.
Plantronics HUB v3.12 Release
December 2, 2018: Plantronics Hub for Windows/Mac
What's New
Adds support in Plantronics Manager Pro for Genesys Workspace Web Edition v8.5.202.23. Call control support was included in Hub 3.11.0.
Adds support for My Habitat Soundscaping feature to Plantronics Hub for Windows/Mac for Habitat Soundscaping customers.
Adds a Network Assessment tool in the Support section. Conducts an on-demand system test to ensure full functionality with Plantronics Manager Pro. For more detail on the latest updates to Plantronics Manager Pro, go to Plantronics-Manager-Pro-Release-Notes
Adds functional modular logging to the Software Log files in Troubleshooting Assistance.
Adds a Clear Software Logs option in the Troubleshooting Assistance section.
Resolved Issues
Improves support for silent updates scheduled using Plantronics Manager Pro.
Improves the options for saving log files in the Troubleshooting section.
Improves stability of Plantronics Hub when closing application.
Improves installation process in Plantronics Hub for Mac to unmount volume when installation is complete.
Improves reliability with Netphone client.
Resolves an issue when a user is on a muted Jabber call. Joining a Microsoft Skype for Business meeting (screen share only) caused the call to unmute.
On the Savi 8200 Series, both the base and the headset serial numbers now display.
Improves LDAP logging details to assist in troubleshooting.
On Plantronics Hub for Mac, improves third-party device unplug event logging in Plantronics Manager Pro.
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.
Plantronics Hub v3.11.3
October 30, 2018: Plantronics Hub for Windows/Mac v3.11.3 Release
What's New
Bug fixes.
Resolved Issues
SWD-2665 - HUB 3.11.2 GUI Pops Up and Exit Continuously when deploying PMP silent mode policy for FW Update
Resolves an issue with Plantronics Hub continuously closing and re-opening while trying to apply an already completed firmware update. This issue occurred only when the firmware update policy was set to Silent in Plantronics Manager Pro.
SWD-2643 - Skype for Business client becomes unresponsive when you join a meeting with lots of participants
Resolves an issue with delays when joining a large Microsoft Skype for Business meeting of 50 or more attendees.
SWD-2703 - DFU | after Language update, Yen HS continues in FW update loop that resulted in dropped calls and possible Plantronics Hub crashes on Voyager 6200.
Resolves an issue on Savi 8200 Series when the headset is directly plugged into the USB port of a PC. The update notification message continued to appear after the specified update was completed.
Known Issues
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 re-plugged. Users must shut down Hub and re-start it to regain audio connection.
During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer see the device.
Support for local firmware update for BT300 (Product ID = 417) is not available.
On 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.11.2
August 13, 2018: Plantronics Hub for Windows/Mac v3.11.2 Release
What's New
Added support for the APU 76 (Product Identification Number 0xAF0B).
Updated Plantronics support for Broadsoft UC One softphone clients.
On the Calisto 7200, adds support for Polycom® NoiseBlock™ technology. NoiseBlock™ technology automatically mutes the microphone when a user stops speaking, silencing noises that can interrupt the conversation. You’ll stay focused on your meeting, not the mute button.
Resolved Issues
Resolves intermittent failure that caused the connection to the enterprise tenant to fail.
Resolves issue on Plantronics Hub for Mac that showed an earlier version of Hub on the About screen for users registered to an enterprise tenant.
Fixes issue with a language change on a Voyager Legend and Blackwire 500 Series products.
Updates Plantronics Hub softphone support for Cisco Jabber.
Updated Plantronics support for retrieving LDAP Group Membership names for Plantronics Manager Pro customers.
Resolves issue Skype for Business calls that resulted in dropped calls and possible Plantronics Hub crashes on Voyager 6200.
Known Issues
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 re-plugged. Users must shut down Hub and re-start it to regain audio connection.
During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer see the device.
Support for local firmware update for BT300 (Product ID = 417) is not available.
On 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 RELEASE NOTES VERSIONS 3.8.4 AND EARLIER
Article ID :
000023351
Version 3.8.4
November 16, 2016: Plantronics Hub Desktop for Windows/Mac v3.8.4 Maintenance Release
What's New
Added support for Plantronics BackBeat PRO 2
Added capabilities that allows BT600 to be used with Plantronics Calisto 620
Added enhanced mute features to Plantronics Blackwire 725:
Mute Reminder
“Mute ON/OFF” Voice Alerts
Volume Level Tones
Resolved Issues
Plantronics Hub Desktop
Added support for new product IDs for Plantronics Blackwire 310/320.
Added support for new product IDs for Plantronics Blackwire 725 and support for redial feature (callback) for Skype for Business.
Fixed a crash in Plantronics Hub for Windows that occurred during a silent firmware update to a Plantronics Calisto 240 (P240-M).
Fixed an issue in Hub for Windows with the Broadsoft custom plugin in which, during installation, call control was dependent on the order of installation.
Resolved issue in Plantronics Hub for Windows that prevented users from uninstalling the application.
Changed Mac installer file name to consistently meet the Plantronics Manager installer script naming requirements.
SDK
Updated the Plantronics SDK EULA.
Version 3.8.3
September 12, 2016: Plantronics Hub Desktop for Windows/Mac 3.8.3 Maintenance Release
What's New
New command line argument to prevent the creation of desktop icon during the installation of Plantronics Hub (Windows only)
Added support for Blackwire 725 SKU’s with the following product identification numbers (PID): 139, 13a, 13b, 13c.
New setting option for DA Series products providing ability to disable audio tones during volume up/down steps. Audio tone only generated at maximum and minimum thresholds.
Resolved Issues Resolved call control issue with BroadSoft UC One v21.3.0.1354 and Plantronics Hub™ 3.8.2 (3.8.51410.36664).
Upgraded libexpat to version 2.2.0 for Cisco Jabber merge module.
Resolved the following issues in Plantronics Hub for Mac for the Cisco Jabber UC client softphone:
Resolved crashes in MacLogger thread
Blackwire C420 call drops (not initiated by user)
Call control not resumed when headset installed after call initiated
Minor memory leak issues
Known Issues
If Savi 700 or Savi 400 headset firmware or tuning is not correctly read from device (for example, battery is empty), device can't register to the server
Restoring Defaults in Plantronics Hub for BWC710/C720 does not restore two settings (Mobile Phone ringtone and the Anti-Startle) to their default
Plantronics Hub for Mac hangs at the end of firmware update If you put Mac to sleep and then wake it up during the update
Plantronics Hub for Mac doesn't apply LDAP settings from spokes.config. It instead uses system's (user) LDAP settings
Failed software update on Plantronics Hub for Mac on Mavericks OSX 10.9 reports as successful on PM Pro
Plantronics Hub users are not notified of a new software update unless a device is currently plugged into the system
Version 3.8.2
July 21, 2016: Plantronics Hub Desktop for Windows/Mac 3.8.2 Maintenance Release
What's New
Not applicable
Resolved Issues
Hub not properly specifying ROOT for LDAP request
Authentication fails when Hub is running behind proxy
Firmware/Software update fails if Hub is running in a proxy environment
Mac: End users can't change "Software Log Level" on Plantronics Hub, after end user manually replaces the spokes.config file
Using the Plantronics icon in the bottom right to right click and Quit Plantronics Hub does not always work. Process would remain running.
Plantronics Hub reporting wrong battery and firmware information after a couple days of running in background while PC hibernated
When auth token expires, Plantronics Hub desktop sends multiple auth requests, resulting in http error 500 from the server
Device settings aren't sent to server initially after device registration
Plantronics Hub waking Windows 10 from Sleep every minute
Intermittent connection between ShoreTel and Plantronics Hub / Failure of ShoreTel Tapi Service (TapiSrv)
Legend users are told that updates are managed by their IT Admin
Voyager Legend FW:107 Cisco Jabber 11: If a muted call is ended at far end and a new incoming call is answered it starts unmuted; user can unmute the call with the HS but then he/she cannot end the call or answer subsequent calls
Voyager PRO UC and Calisto P240: Call control stops working in standalone mode after Plantronics Hub launched and then closed.
Cisco Jabber Standalone support is needed for Cisco Jabber for MAC OS X
Hub for Mac & Jabber plugin: No update archive is created during the build process
PLT Cisco Jabber plugin on Windows crashes on Cisco Jabber 11.7 EAP
Jabber: Call Control Stops Working after Multi-Mute scenario
Known Issues
If Savi 700 or Savi 400 headset firmware or tuning is not correctly read from device (for example, battery is empty), device can't register to the server
After Wearing Sensor is turned off via MyHeadsetUpdater for Blackwire C710/C720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work
Restoring Defaults in Plantronics Hub for BWC710/C720 does not restore two settings (Mobile Phone ringtone and the Anti-Startle) to their default
Plantronics Hub for Mac hangs at the end of firmware update If you put Mac to sleep and then wake it up during the update
Plantronics Hub for Mac doesn't apply LDAP settings from spokes.config. It instead uses system's (user) LDAP settings
Failed software update on Plantronics Hub for Mac on Mavericks OSX 10.9 reports as successful on PM Pro
Jabber and Lync 2013 calls aren't rerouted to Voyager Focus UC if the USB adaptor is unplugged during an active call and plugged right back in
Plantronics Hub users are not notified of a new software update unless a device is currently plugged into the system
Version 3.8.1
May 26, 2016: Plantronics Hub Desktop for Windows/Mac 3.8.1 (released to address issues in “Resolved Issues” below).
What's New
Not applicable
Resolved Issues
Windows 10 audio issues on device unplug/replug with Plantronics Hub running
Plantronics Hub 3.8 freezes on startup if host system has certain Region and Language Format settings not explicitly supported by Hub
Known Issues
Firmware/Software update fails if Plantronics Hub is running in a proxy environment
Authentication fails when Plantronics Hub is running behind a proxy
If Savi 700 or Savi 400 headset firmware or tuning is not correctly read from device (for example, battery is empty), device can't register to the server
After Wearing Sensor is turned off via MyHeadsetUpdater for Blackwire C710/C720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work
Restoring Defaults in Plantronics Hub for BWC710/C720 does not restore two settings (Mobile Phone ringtone and the Anti-Startle) to their default
Plantronics Hub for Mac hangs at the end of firmware update If you put Mac to sleep and then wake it up during the update
Plantronics Hub for Mac doesn't apply LDAP settings from spokes.config. It instead uses system's (user) LDAP settings
Failed software update on Plantronics Hub for Mac on Mavericks OSX 10.9 reports as successful on PM Pro
Jabber and Lync 2013 calls aren't rerouted to Voyager Focus UC if the USB adaptor is unplugged during an active call and plugged right back in
Plantronics Hub users are not notified of a new software update unless a device is currently plugged into the system
Version 3.8
May 9, 2016: Plantronics Hub Desktop for Windows/Mac 3.8
What's New
New device support: Voyager 5200 UC
New device support: EncorePro 5xx USB and EncorePro 7xx USB
New softphone support: Jabber for Mac
Option to disable all softphones
Mute Reminder improvement
Simpler Plantronics Hub deployment
Resolved Issues
Voyager Edge: When USB-connected, battery status info is sometimes incorrect and inconsistent
Voyager Edge: Sample ringtones play only twice when selected without selecting Apply first
Platronics Hub for Mac: Non-existing software plugins are sent from client to cloud
Plantronics Hub for Mac can't start with Avaya 1X is on and disabled in Client Hub
Voyager Edge UC/BT300: Setting PC ringtone volume to Off, prevents sample playback of both PC and Mobile Phone ringtones
Voyager Edge UC/BT300: When Streaming Music setting turned off, music continues playing through headset
Software Presence settings are not working with Lync/S4B
Incoming call with Plantronics Hub and SwyxIt! sometimes cannot answer call
When Streaming Audio (A2DP) setting changed while USB-connected, setting change does not take after powering cycling the HS
Spokes.config file is overwritten during local update on Mac OS
Plantronics Hub for Mac crashes on launch when DA90 or BT600 is connected on Mac
Smart Lock's popup message only appearing the 1st time headset separated from USB adapter
Voyager 5200 UC: OTA DFU being allowed even when battery below 50%
Jabber Plugin: Not establishing pipe to softphone and no green checkmark
When Wearing Sensor turned off, dependent settings should be disabled
Plantronics Hub for Mac not responding when user try to save log files with any connected Device
iTunes resumes playing after call ends when music was manually paused by the user prior to the call
Scroll bar displayed for a few seconds when clicking on update's "view details"
When starting update, "update" button in the background is blue
User is getting Update notification for Updated device
Voyager Focus UC: Wrong primary value shown as Mute Reminder default
Updated setting values not being sent to server when a Restore Defaults is executed
Jabber & Client Hub: Jabber transfers active call from non-primary device to primary device
Firmware/Software update fails if Plantronics Hub is running in a proxy environment
34551 Plantronics Hub is taking 20 seconds to displaying headset info
DA70: About Device screen does not show Headset connection
No call control after disconnection of device on call and transfer of call on Cisco Jabber
On Avaya Communicator both calls are put on hold when attempting to hold one and resume the other
User is getting error message when click on Disable FW Update recovery Filed
Cisco Jabber multiple calls handling issue
Some Plantronics SDK events not available when using Voyager Focus UC
Jabber & Client Hub: Jabber transfers active call from non-primary device to primary device
Server integration for new Mute Reminder setting not implemented
Pressing "Check For Updates" hangs Plantronics Hub resulting in crash
Invalid PID data is displayed in WMI tables for devices with FW Updates before WMI Provider installation
Voyager 5200 firmware update: after reaching 36% the update process drastically slows down resulting in overheating of MacBook
Sometimes, OK button stays disabled after Successful update.
Intermittent: Mac Client Hub crashes during silent Client Hub update
About Screen copyright date should now be 2016
"When I Start Speaking" value for Audible Reminder for Mute Reminder setting not implemented
WMI Provider incorrect formats of PID, FW update, event time
Cisco Jabber multiple calls handling issue
Voyager 5200 battery bar levels are inconsistently displayed when device is connected via BT600 and US
After successfully applied SW settings and Client Hub restart, locked SP are unlocked
10 MB increase in size of 3.8 SDK from 3.7
Uninstalling Hub Desktop leaves stray folder behind
"User Guide" link for Savi 7xx is not leading to any page
Duplicated Updates are displayed on Hub Client Updates page
An endless mute on/off loop occurs if a Jabber call is muted at the very beginning of the call
Plantronics Hub gets stuck while checking for updates
Inconsistent UI when "Check for Updates" button is pressed during the silent Update process
Plantronics Hub for Mac software settings update, with Avaya 1-X as Target Softphone, is not implemented correctly
User Configuration Settings are not preserved over a DFU cycle with Blackwire C500 or C725
After Jabber plugin update and Client Hub is uninstalled, Spokes 3G folder contains "Plugins" folder
Incoming ringtone is heard only twice while an outgoing call is ringing in CUPC
Plantronics Hub for Mac Software Settings are not applied correctly when using Avaya 1-X
Mac OS10.10: Client Hub does not send metrics information for non Plantronics device
Plantronics Hub SwyxIt - no call control despite green tick there. (Also sometimes green tick disappears)
Windows Media Player resumes even when not playing at the start of a call
Silent update of spokes 3.6 to 3.7 requires restart in order to authenticate to server
Install metrics are not being recorded for Plantronics Hub installed on WIN8-64
Known Issues
Windows 10 audio issues with Plantronics Hub when headset is unplugged and plugged right back in. Rebooting the system or removing the USB headset from device manager resolves the issue.
Firmware/Software update fails if Plantronics Hub is running in a proxy environment
Authentication fails when Plantronics Hub is running behind proxy
If Savi 700 or Savi 400 headset firmware or tuning is not correctly read from device (for example, battery is empty), device can't register to the server
After Wearing Sensor is turned off via MyHeadsetUpdater for Blackwire C710/C720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work
Restoring Defaults in Plantronics Hub for BWC710/C720 does not restore two settings (Mobile Phone ringtone and the Anti-Startle) to their default
Plantronics Hub for Mac hangs at the end of firmware update If you put Mac to sleep and then wake it up during the update
Plantronics Hub for Mac doesn't apply LDAP settings from spokes.config. It instead uses system's (user) LDAP settings
Failed software update on Plantronics Hub for Mac on Mavericks OSX 10.9 reports as successful on PM Pro
Jabber and Lync 2013 calls aren't rerouted to Voyager Focus UC if the USB adaptor is unplugged during an active call and plugged right back in
Plantronics Hub users are not notified of a new software update unless a device is currently plugged into the system
Version 3.7.1
January 18, 2016: Plantronics Hub Version 3.7.1
Resolved Issues
Call transfer to Cisco CUCE queue fails when Savi 7xx is in use with Cisco Jabber 10.5.2
Call control not working with Swyxit!
Call control not working with IBM Sametime
Battery level indicator for Blackwire 710/720 is missing in Plantronics Hub Window
Miscellaneous bug fixes and improvements
Version 3.7
December 3, 2015: Plantronics Hub Version 3.7
What's New
Support for Plantronics APU-75
Support for BroadSoft UC-One softphone
Ability to update device settings for the BackBeat Pro, BackBeat Sense and Voyager Edge
Many enhancement on the Mac platform, including:
Support for Plantronics Manager Pro and Plantronics Manager
Software updates
Firmware updates for Savi products
Resolved Issues
Missing headset serial number for Savi 700 series
Usernames with Unicode characters are displayed incorrectly
Admin notes for end user updates not displaying in Chinese
Plantronics Hub update fails if same type of installer (.exe or .msi) not run as for previous installation
Cannot update Plantronics Hub for Mac while Plantronics Hub is running
Spokes.config file is overwritten during local update on Mac
Advertised update fails on Mac
Lync presence resets to 'Available' after a mobile call
Plantronics Hub for Mac unable to reach network share - updates cannot be received
Dial Tone is not working in Lync 2013/Skype for Business
Plantronics Hub can crash when BT600 removed from USB port with Voyager Focus UC connected to USB
Dialing a call from a display device with Avaya one-X intermittently fails to dial correct digits and initiate a call
Second incoming SwyxIt! 2015 call can not be answered by flash
Plantronics Hub intermittently crashes when Skype for Business is restarted
Softphones that have been "locked" by EIT are still showing in Plantronics Hub
"Restore Defaults" setting missing for Blackwire 700 series
Local DFU fails if user selects file from shared location
Calisto P240 and Clarity P340 Serial number is displayed as unavailable
Improve interaction between sensor-based presence and Smart Presence
If Jabber is running during Plantronics Hub upgrade computer must be restarted
Mute alert stops working after changing settings
Voyager Legend on Mac: Audio channel closes after call is finished
EIT push of .exe installer does not pass parameters if older version of Plantronics Hub already present
Default Mobile Audio Bandwidth setting value for BT300C and BT300C-M isn't marked
Plantronics Hub not able to display headset serial number for Savi 7xx/4xx after device info is loaded
Deskphone test ringtone button produces no audio for Savi 700 series
Test ringtone buttons become disabled for Savi 700 series after radio link activated
Latest Avaya for Lync client (ACA plugin) uses new process names
Pressing VM button in CIPC GUI results in Plantronics Hub disconnection
Unable to dial from the device dialpad on Lync/Skype for Business
Users not notified of Voyager Focus UC headset update
Miscellaneous bug fixes and improvements
Known Issues
Version 3.6
July 30, 2015: Plantronics Hub Version 3.6
What's New
Support for the following devices:
Voyager Focus UC, including firmware updates
DA70
Blackwire 315/325
Savi 400 TIP FW upgrade
Support for the new UC client Avaya Communicator for Microsoft Lync
Enabled support for Cisco Jabber for VXME (to be included in the next release of Jabber for VXME in August)
Polycom support – DFU
Skype for Business support – Call Control, presence
Support for Avaya Communicator for Microsoft Lync
Various UX updates
Resolved Issues
Unable to uninstall 3.5 installations performed in another language
Blackwire 720 PIDs missing from Plantronics Manager Pro added in 3.6: PID 0x0129 and 0x012A
Pushing Plantronics Hub MSI silently doesn’t work if:
2.x installed and Flexnet Agent attempts to check for update at time of 3.5 upgrade
Jabber is installed
SwyxIt!, Windows Media Player, WinAmp is installed (silent install fails, normal manual install works)
Unable to uninstall 3.5 installations performed in another language
MSIEXEC parameters are ignored in the upgrade path (IT pushes MSI for Plantronics Hub 3.5 when prior version of Plantronics Hub is installed and the upgrade runs but the command line parameters are ignored so Hub continues to point at the consumer tenant)
Plantronics Hub installation is finished but error dialog is displayed
Caller ID for Clarity 340 is shown as "Unknown"
Calisto 620/BT300: Conflicts, inconsistencies, and other problems with displayed battery UX info
Refresh icon isn't available on main page
Savi W720: Name not appearing in System Tray menu and not shown as primary device
Plantronics Hub hangs when user selects "Mute" in Mac top toolbar.
Device not removed from Plantronics Hub when detached after system sleep
Voyager Legend, Voyager Pro UC and Blackwire 710/720: "Mute off Alert" setting is not present on Plantronics Hub
Once screen maximized after launch, it can not be minimized to any smaller size
Software update from Plantronics Manager/Manager Pro is not received by Plantronics Hub
Clarity 340 ‐ Plantronics Hub sends wrong call state reports for Cisco Jabber call states
Uninstall of Plantronics Hub completes with an "Installation Complete!" message
For Jabber (and other softphones) presence is sent as Available and not Unknown, when softphone presence
isn't attainable via APICrash in PLTHub.exe after performing DFU
Plantronics Hub is displaying battery level during silent DFU
Unable to end calls from the device when dialing external numbers in Skype
Settings packages aren't applied according to group priority after Plantronics Hub restart
Auto‐Answer feature not working with 3.5 patch release
Plantonics Hub 3.5 prevents user from defaulting Savi base to deskphone
Parameters passed to Hub MSI not applied if Jabber installed and running
Quitting Plantronics Hub doesn't end PLTHub.exe so it can't be re‐launched
Firmware update progress bar should not reset to zero throughout Savi update process
Miscellaneous bug fixes and improvements
Known Issues
