![]() ![]() The replacement is Savi 8200 Series / Voyager 5200 Office). *(NOTE: Legend UC is an end-of-life product. Plantronics Hub also works in conjunction with Plantronics Manager Pro to give your IT staff an easy-to-use tool to configure and manage devices across the enterprise. So there could be a resilience issue with the integration. Use Plantronics Hub to provide RCC, as required, and enhance user experience with mute and battery status, easily visible on the taskbar. I quitted and restarted 3CX and then it re-appeared, and headset call control started to work again. If you use a Plantronics headset with the BT600 you will want to update both the BT600 and the headset. Download the correct installer file for your environment (e.g., MSI version) from 2. To do so youll need the headset plugged into the computer via USB. You can deploy Plantronics Hub in a large organization by following the steps below: 1. Youll want to see whatever device you want to be updated on the this screen. There was one occasion where a test initially failed: I then checked Hub > Settings > Softphones, scrolled to bottom and the Softphone called "COM Session" had disappeared. Open the application, and click the 'Notifications' tab on the top of the window. Given these test results it would suggest that any Plantronics Hub supported headset will provide call control with 3CX. I had success with the all the products I tried: Legend UC + BT300*, Calisto 3200, Savi W740*, Savi 8220 UC, Focus UC + BT600, Voyager 4245 Office. The test included inbound call: headset rings, answers, ends, outbound call: headset activates, ends. I tested button call control (RCC - remote call control) with a wider set of Poly headsets with the 3CX Windows Client, Version 16.3.0.179 and Plantronics Hub version 3.20. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |