Plantronics Hub Release Notes

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

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

Resolves an issue with delays when joining a large Microsoft Skype for Business meeting of 50 or more attendees.

Resolves an issue on Savi 8200 Series after a firmware update or language change, that could cause an update notification message to continue to appear.

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

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.

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

July 13, 2018: Plantronics Hub for Windows/Mac v3.11.1 Release

Resolved Issues

Resolves an issue where Plantronics Hub does not recognize the firmware update, version 128, for the DA Series of devices. Please see KB article for more details.

Resolves an issue where some members of an Active Directory group, outside of the corporate network, intermittently did not appear in Plantronics Manager Pro.

Resolves an issue with self-signed certificates to allow authentication of Plantronics Hub for Windows with Plantronics Manager Pro.

Resolves issues with audio performance on DA Series after a firmware update.

Known Issues

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.

With BroadSoft Communicator v22.0.0.1166 and v22.0.0.1329, call control may fail intermittently.

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

April 2, 2018: Plantronics Hub for Windows/Mac v3.11 Release

What's New

Adds support for a new Calisto 240 PID to Hub for Windows and Mac. The new Product ID is 0xAE04.

Plantronics Hub will now display a new section called SDK Enabled Softphones if they are found to be running on the system.

Adds support in Plantronics Hub for firmware updates even when multiple Plantronics devices are connected. Users no longer need to remove additional devices.

Adds support for multiple running instances of Plantronics Hub on a single system which allows users to switch between profiles in Windows and have full support for each profile in Plantronics Hub.

Improved support for Other Manufacturers devices:

Enables additional methods of obtaining manufacturer information:

Added vendor ID lookup for manufacturer information when the Endpoint Descriptors have not been properly populated by the manufacturer

Inventory all audio devices: Telephony page filter removed. Now all USB audio devices will be inventoried and added to Plantronics Manager Pro. This includes webcams and keyboards with audio jacks.

Resolved Issues

Resolves issue in Plantronics Hub for Mac that resulted in empty lines added to the menu bar when used with the Voyager Focus or Legend.

In Plantronics Hub, in Settings tab, an option for HD Voice no longer erroneously appears in the Wireless menu.

Fixes issue on Plantronics Hub for Mac in which the Plantronics Hub icon sometimes remained on the desktop after an install was completed and required the user to manually eject it in order to perform a subsequent software update.

Fixed issue with no remote call control with Citrix XenApp 7.13 with HDX RTOP v2.2 and Skype for Business VDI client.

Resolves issue with Restore Defaults feature on Voyager 8200 Series which resulted in not all default settings being restored.

Links in Plantronics Hub updated to point to correct web pages.

Known Issues

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 a local firmware update for BT300 (Product ID = 417) is not available.

On Jabber call, audio unmutes when a user joins a non-audio Skype for Business meeting.

With BroadSoft Communicator v22.0.0.1166 and v22.0.0.1329, call control may fail intermittently.

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

December 14, 2017: Plantronics Hub for Windows/Mac v3.10.2 Release

What's New

Adds device firmware update support in Plantronics Hub for Mac for the following Blackwire and Calisto family devices:

Blackwire 3210 Series

Blackwire 3215 Series

Blackwire 3220 Series

Blackwire 3225 Series

Blackwire 5210 Series

Blackwire 5220 Series

Blackwire C725

Blackwire C310

Blackwire C315

Blackwire C315.1

Blackwire C320

Blackwire C325

Blackwire C325.1

Blackwire C435

Blackwire C510

Blackwire C520

Blackwire C520

Calisto P610

Adds support for a new Calisto 240 PID to Hub for Windows and Mac. New Product ID is 0xAE04.

Adds support for the following new Blackwire devices:

Blackwire 3210 Series (Product ID = 0xC055)

Blackwire 3220 Series (Product ID = 0xC056)

Blackwire 3215 Series (Product ID = 0xC057)

Blackwire 3225 Series (Product ID = 0xC058)

Adds support for High Sierra to Hub for Mac.

Resolves issue with call control in Hub for Mac with Bria 5.0.

Fixes issue with MDA400 QD Series button that prevented a call on hold from being resumed with a call button press on the base.

Resolved Issues

Resolves issues with authentication and download when part of the Plantronics Manager Pro environment.

Fixes issue with missing serial number and build code for MDA400 QD Series in Plantronics Hub for Windows.

Resolves intermittent issue with headsets not displaying in Hub for Windows.

Restore Defaults feature on Voyager 8200 Series may not restore all default settings.

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.

Restore Defaults feature on Voyager 8200 Series may not restore all default settings.

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.

The Savi 700 Series may display advanced settings that are not supported by the headset.

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.

Plantronics Hub v3.10.0

July 20, 2017: Plantronics Hub for Windows/Mac v3.10.0 Release

What's New

Added support in Plantronics Hub for Windows/Mac for Avaya Equinox v3.1.1.2.

Resolved issue in Plantronics Hub for Windows that occurs during a firmware update on Savi 700 or D100 if no headset is attached.

Fixed issue on Voyager 5200 Series during firmware updates that resulted in voice prompt language defaulting to US English. After a firmware update, the device retains user’s language preference.

Fixed firmware update issue on the Savi 700 Series that could result in issues including loss of advanced settings in the settings tab, loss of audio during calls, and missing or incorrect notifications.

Known Issues

With BroadSoft Communicator v22.0.0.1166 and v22.0.0.1329, call control may fail intermittently

Restore Defaults feature on Voyager 8200 Series may not restore all default settings.

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.

Some Voyager Bluetooth headsets intermittently may not display in the Hub user interface. Typically, re-starting Plantronics Hub will resolve the issue.

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.

The Savi 700 Series may display advanced settings that are not supported by the headset.

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.

Fixed audio issue with Savi 700 Series and Savi 400 Series resulting from a logic error in the tuning parameter update that occurred after a device firmware update using Hub v3.9.2. Note: To access the most recent firmware for these products, users must update to Plantronics Hub v3.9.4 or above.

Updated certificate to fix issue with the Plantronics Hub REST Service API on Chrome v58.

Fixed intermittent issue with Plantronics Legend during firmware update or language change. Note: To access the most recent firmware upgrade for Plantronics Legend, users must update to Plantronics Hub v3.9.4 and above.

Fixed issue with Unicode characters when creating LDAP groups. Plantronics Hub for Win/Mac will now recognize group names with Unicode characters.

Known Issues

Call control on Cisco Jabber versions prior to v11.x are not functional.

Settings that appear on both headset and BT300 adapter may not synchronize correctly when changed.

If Plantronics Savi 700 Series or Savi 400 Series 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 for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.

Fixed an issue in the recovery process during a firmware update on both the MDA200 and MDA220 on a Windows 10 system. Note: To access the most recent firmware update for these products, users must update to Plantronics Hub v3.9.2 or above.

Fixed an issue with Savi 700 Series and Savi 400 Series products during the firmware update process on Windows systems. Note: To access the most recent firmware for these products, users must update to Plantronics Hub v3.9.2 or above.

Fixed an issue with remote call control on Swyx Netphone Client 9.40.1635 and higher on Windows systems.

Fixed an issue on Blackwire Series products during a firmware update on Windows systems. Note: To access the most recent firmware update for these products, users must update to Plantronics Hub v3.9.2 or above.

Known Issues

Excessive performance degradation on Plantronics for Hub in Plantronics Manager.

When a call is on hold, a button press will not generate a dial tone with Microsoft Skype for Business.

Call control on Cisco Jabber versions prior to v11.x are not functional.

Initiating calls with Microsoft Skype on a Plantronics device dial pad is not reliable.

Settings that appear on both headset and BT300 adapter may not synchronize correctly when changed.

If Plantronics Savi 700 Series or Savi 400 Series 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 for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.

Important NotePlantronics Hub for Windows v3.9.1 is available to download on Plantronics.com only and will not be made available on the Plantronics Manager and Plantronics Manager tenants. Plantronics Hub for Mac v3.9.1 is now available for download in Plantronics Manager and Plantronics Manager Pro as well at plantronics.com.

Resolved IssuesFixed an issue with a REST API Certificate Error.

Earlier VersionsEarlier versions of the release notes can be found here.