Resolved an issue preventing Chrome version 107 and higher from accepting a self-signed certificate.Security enhancements, please consult Poly Security Center for details.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.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.After wearing sensor is turned off for Blackwire 710/720, Plantronics Hub still shows sensor-dependent settings as ON yet they do not work.Unplugging the following devices during the firmware update process may result in the recovery process not working correctly: Blackwire C315, C325.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.On Cisco Jabber call, audio unmutes when user joins a non-audio Skype for Business meeting.Support for local firmware update for BT300 (Product ID = 417) is not available.During a firmware update, if an MDA220 becomes bricked, Plantronics Hub can no longer detect the device.Users must shut down Plantronics Hub and re-start it to regain audio connection. Lost audio connections may occur if the BT600 is unplugged and then plugged back in.It is also not accurately reported to Plantronics Manager Pro. On the MDA220 (Product ID 0xAD04), the serial number is not reported correctly in Plantronics Hub for Windows and Mac.Plantronics Hub for Mac does not support firmware updates for these devices. For MDA200 and MDA400 QD Series, firmware updates are available using Plantronics Hub for Windows only.Call control using the headset button will work reliably for subsequent calls. When using Zoom for MacOS the headset call control button may not work reliably for the first call.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 updating from v3.22.0 and v3.22.1 to a later version of Hub on a non-English language Windows system it is necessary to first uninstall these versions before reinstalling v3.22.2 or later.Resolved an issue causing the Mute feature to work unreliably on some Zoom calls.Resolved an issue resulting in a high number of open connections per client at a central HTTPS proxy.Resolved an issue causing an update to Hub 3.25 via a policy to fail at 50%.Resolved an issue causing loss of audio on an ongoing call when a second incoming call is ringing if the Zoom feature “Sync buttons on headset” is enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |