Mergeti la continut

Plantronics Hub Release Notes

ID articol:

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