Filemaker Pro 18 Advanced

filemaker-pro-18-advanced.png

What's New

New user interface for importing data

More easily map imported source data to FileMaker fields using the new Import Field Mapping dialog box. Use type ahead instead of drag and drop for greater efficiency. And specify custom delimiters when importing certain file types.

Open specific app at launch

Provide better app discoverability for your users. Open a specific custom app when launching FileMaker Pro Advanced.

File version comparison

Use a preview release script step to save a copy of a FileMaker file as XML. Use the XML file to more easily compare changes and updates to your custom app.

File-based script steps

Create scripts that read, write, and manage external data files to write log files or export data in a custom format. Replaces the need for many file-based plug-ins.

Script Error Logging

Now you can more easily debug your workflow automation. Use a preview script step to write information about script errors to a log file.

While calculation function

This calculation function repeats logic while the condition is true, then returns the result, replacing the need for some recursive custom functions.

SetRecursion calculation function

Set the maximum number of iterations for recursion and loops within an expression. The default limit is 50,000 iterations to more easily stop a recursion or loop from running indefinitely. The limit can be lowered or raised using this function.

New managed security access

This new privilege allows developers to offload account access management to other team members without needing to provide full access to any other parts of the file.

Manage Security dialog box

The streamlined Manage Security dialog box allows you to be more efficient in managing access to your custom apps.

Plug-in security enhancements

Ensure your plug-ins come from a trustworthy source before they are automatically loaded by your FileMaker app. Within the Plug-in SDK, developers are able to digitally sign plug-ins. Notifications warn users before loading an unsigned plug-in.

Default file access protection

Prevent other FileMaker files from accessing the data and schema in your custom app. The "Require full access privileges to use references to this file" is now enabled by default in newly created files.

Filemaker Pro 17 Advanced update 17.0.5

FileMaker Pro 17.0.5 Advanced

https://support.filemaker.com/s/article/FileMaker-Pro-17-0-5-Advanced?language=en_US

This software updates FileMaker Pro 17 Advanced to version 17.0.5.

If you are unable to successfully update to FileMaker Pro 17.0.5 Advanced, search the FileMaker Knowledge Base for installation information.

Software details

Japanese era name change

This software update supports the new Japanese era, Reiwa (令和), which begins on May 1, 2019. Japanese Emperor Year (Wareki) dates entered into date fields or used in calculations are changed to a Western Gregorian (Seireki) year and saved internally in the format specified by the file. For example, R1/10/28 is changed to 2019/10/28 (R1 = the first year of Reiwa, or 2019). For more information about Japanese Emperor Year dates, see FileMaker Pro Advanced Help.

Software Update: FileMaker Pro 17.0.4 Advanced

https://support.filemaker.com/s/article/Software-Update-FileMaker-Pro-17-0-4-Advanced?language=en_US

This software updates FileMaker Pro 17 Advanced to version 17.0.4 and fixes a bug.

If you are unable to successfully update to FileMaker Pro 17.0.4 Advanced, search the FileMaker Knowledge Base for installation information.

Software details

Addressed an issue where ODBC connections were not closed properly after certain operations were performed.

Important: To ensure that you don't encounter the issue above, you must update all clients to FileMaker Pro 17.0.4 Advanced and FileMaker Go 17.0.5.

Software Update: FileMaker Pro 17.0.3 Advanced

https://support.filemaker.com/s/answerview?language=en_US&anum=000026224

This software updates FileMaker Pro 17 Advanced to version 17.0.3, addresses known issues in macOS Mojave 10.14, and fixes bugs.

If you are unable to successfully update to FileMaker Pro 17.0.3 Advanced, search the FileMaker Knowledge Base for installation information.

Software details

The following issues were addressed.

Important: To ensure that you don't encounter the issues below, you must update all clients to FileMaker Pro 17.0.3 Advanced.

Application

  • Windows: The application could stop responding when initializing custom menus. 

  • Windows: The application closed unexpectedly when the Script Workspace was maximized and then restored to its previous size after the script steps pane was displayed.  

Layouts

  • Improved performance when drawing layouts that don't contain portals used for master-detail layouts.  

macOS Mojave 10.14

  • There was a graphical problem in some Edit dialog boxes.  

  • The operators list in the Specify Calculation dialog box did not display. 

Software Update: FileMaker Pro 17.0.2 Advanced

https://support.filemaker.com/s/answerview?language=en_US&anum=000026080

Software details

The following issues were addressed.

Important: To ensure that you don't encounter the issues below, you must update all clients to FileMaker Pro 17.0.2 Advanced.

Application

  • Windows: FileMaker Pro Advanced closed unexpectedly when the Hosts dialog box was opened and then immediately closed.

  • macOS: In certain circumstances, the CPU usage increased to 100% after FileMaker Pro Advanced was opened.

  • macOS High Sierra 10.13: During some operations, the progress bar did not display.

Scripts

  • Windows: When the Show Custom Dialog script step was performed, the custom dialog box didn't maintain the default size.

Saving records as PDF

  • Saving records as a PDF was slower than in previous versions.

Layouts

  • macOS: FileMaker Pro Advanced closed unexpectedly when the field display format was changed in the Inspector.

APIs, technologies, or features to be deprecated

As FileMaker Pro Advanced evolves, the list of supported technologies, APIs, and features will change. As part of this evolution, certain operating systems versions, hardware, and features may be deprecated in favor of newer ones. Although deprecation does not mean the immediate deletion of an item, you should migrate your solution away from deprecated technologies, because these technologies may be removed in a future version of the product.

For the latest information about deprecated APIs, technologies, and features, search the FileMaker Knowledge Base. For information about new, changed, and removed features, see the most up-to-date version of FileMaker Pro Advanced Help, available on the FileMaker website.

Plantronics Hub v3.10.2

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 API

  • Crash 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

Kindle VoiceView

Download the VoiceView Audio File for Your Device

If you’ve recently factory reset your Kindle, you will need to re-download the audio file for your device to use VoiceView.

Download the VoiceView Audio file for Kindle Paperwhite (7th Generation), Kindle Oasis (8th Generation), Kindle (8th Generation), Kindle Oasis (9th Generation), and Kindle Paperwhite (10th Geeration). See Which Kindle E-reader Do I Have? if you're not sure which Kindle e-reader model you're using.

To download and install the audio file: 

  1. Check your software version. If your Kindle is not on the latest software version, you will need to update your device to the latest available version. To learn more, go to Fire & Kindle Software Updates.

  2. Download the audio file for your device model:

  3. Turn on your Kindle and plug it into your computer using the USB cable.

  4. Drag and drop the file from your computer into the Kindle drive.

  5. Monitor the transfer to ensure the file transfers successfully.

  6. Eject the Kindle to safely disconnect your Kindle from your computer, and then disconnect the USB cable from your Kindle and your computer.

  7. Hold the power button on your Kindle for 20 seconds.

  8. Wait one minute while your Kindle restarts and installs the voice file.