Troubleshooting headset call controls in softphones

See also

Sources

1. 1
   The Microsoft Edge policy WebHidAllowDevicesForUrls automatically grants listed sites permission to access HID devices with the given vendor and product IDs.

   Microsoft Edge Browser Policy Documentation WebHidAllowDevicesForUrls · Description section · Checked 2026-10-02
2. 2
   If a URL appears in both WebHidAllowDevicesForUrls and WebHidBlockedForUrls, WebHidAllowDevicesForUrls takes precedence; if the allow policy is unset, DefaultWebHidGuardSetting applies, and otherwise the user's own setting.

   Microsoft Edge Browser Policy Documentation WebHidAllowDevicesForUrls · Description section, final paragraphs · Checked 2026-10-02
3. 3
   In WebHidAllowDevicesForUrls each device entry must have a vendor_id; omitting product_id matches any device from that vendor, and an entry with product_id but no vendor_id is ignored.

   Microsoft Edge Browser Policy Documentation WebHidAllowDevicesForUrls · Description section, devices field rules · Checked 2026-10-02
4. 4
   WebHidAllowDevicesForUrls is supported in Microsoft Edge 109 or later on Windows and macOS, 155 or later on Android, and not on iOS.

   Microsoft Edge Browser Policy Documentation WebHidAllowDevicesForUrls · Supported versions section · Checked 2026-10-02
5. 5
   Genesys Cloud's WebRTC audio troubleshooting advises closing or blocking other applications that are accessing the microphone or speakers.

   Test your WebRTC phone settings · Test your WebRTC phone settings, microphone and speaker troubleshooting · Checked 2026-10-02
6. 6
   Genesys Cloud Embeddable Framework customers may need to grant additional HID permissions within their iframe for headset call controls.

   Configure headsets for embedded clients · Configure headsets for embedded clients, Embeddable Framework note · Checked 2026-10-02
7. 7
   Genesys Cloud call controls on Sennheiser/EPOS headsets require the EPOS Connect software.

   Configure headsets for embedded clients · Configure headsets for embedded clients, supported vendors list · Checked 2026-10-02
8. 8
   Genesys Cloud WebRTC supports built-in Jabra headset call controls when Genesys Cloud runs in a Chromium-based browser (Google Chrome or Microsoft Edge), in the Genesys Cloud desktop app, or in the embedded clients.

   Configure a Jabra headset · Configure a Jabra headset, opening paragraph · Checked 2026-10-02
9. 9
   Genesys Cloud lists the Jabra headset call controls as answer, hang up, hold, remove from hold, mute, unmute and reject, with availability depending on the headset model.

   Configure a Jabra headset · Configure a Jabra headset, supported call controls list · Checked 2026-10-02
10. 10
    In Genesys Cloud, Bluetooth Jabra headsets connected through the computer's internal Bluetooth adapter do not support call controls; a wired USB connection or a Jabra USB Bluetooth adapter is required.

    Configure a Jabra headset · Configure a Jabra headset, connection requirements · Checked 2026-10-02
11. 11
    Genesys Cloud does not support Jabra headset call controls in Firefox or Safari.

    Configure a Jabra headset · Configure a Jabra headset, supported browsers statement · Checked 2026-10-02
12. 12
    In the browser, enabling Jabra call controls in Genesys Cloud requires the user to accept an Additional Permissions Required prompt and then select the headset in the WebHID connection prompt and click Connect.

    Configure a Jabra headset · Configure a Jabra headset, browser setup steps · Checked 2026-10-02
13. 13
    Genesys Cloud's WebRTC microphone troubleshooting steps include allowing the browser to use the microphone and unmuting the microphone in the client call controls.

    Test your WebRTC phone settings · Test your WebRTC phone settings, microphone troubleshooting · Checked 2026-10-02
14. 14
    In Genesys Cloud, a Plantronics/Poly headset connected over Bluetooth cannot use its built-in call controls; a USB connection is required.

    Configure a Plantronics/Poly headset · Configure a Plantronics/Poly headset, connection requirements · Checked 2026-10-02
15. 15
    Genesys Cloud call controls on Plantronics/Poly headsets require the Plantronics Hub software to be installed on the computer.

    Configure a Plantronics/Poly headset · Configure a Plantronics/Poly headset, requirements · Checked 2026-10-02
16. 16
    Genesys Cloud states that it does not support Poly Lens for Plantronics/Poly headset call controls.

    Configure a Plantronics/Poly headset · Configure a Plantronics/Poly headset, requirements · Checked 2026-10-02
17. 17
    For Jabra and Yealink headset buttons in Genesys Cloud for Salesforce, the user must open a separate WebRTC window using the Pop WebRTC Phone window setting.

    Configure headsets for embedded clients · Configure headsets for embedded clients, Salesforce section · Checked 2026-10-02
18. 18
    The Genesys Cloud WebRTC speaker test (the blue speaker icon that plays test tones) is available to Chrome browser users only.

    Test your WebRTC phone settings · Test your WebRTC phone settings, speaker test · Checked 2026-10-02
19. 19
    Genesys provides limited technical support for headset call controls; mechanical headset faults and vendor software or firmware problems are the headset vendor's responsibility.

    Configure a Plantronics/Poly headset · Configure a Plantronics/Poly headset, support note · Checked 2026-10-02
20. 20
    Genesys Cloud headset call controls require the user to have a WebRTC phone assigned.

    Configure a Jabra headset · Configure a Jabra headset, prerequisites · Checked 2026-10-02
21. 21
    Genesys Cloud supports Yealink headset call controls only in the Chrome browser, not in the Genesys Cloud desktop app or the embedded clients.

    Configure a Yealink headset · Configure a Yealink headset, supported clients · Checked 2026-10-02
22. 22
    Genesys Cloud supports Yealink headset call controls over a wired USB connection or a Yealink Bluetooth or DECT dongle, but not over the computer's internal Bluetooth adapter.

    Configure a Yealink headset · Configure a Yealink headset, connection methods · Checked 2026-10-02
23. 23
    Across the Genesys Cloud Jabra, Poly and Yealink articles, the consistent pattern is that call-control buttons work over USB cable or a vendor dongle but not over the PC's built-in Bluetooth radio, so an agent's first check for dead buttons is how the headset is connected.inferred

    Configure headsets for embedded clients · Configure headsets for embedded clients, connection requirements; read together with the vendor articles · Checked 2026-10-02
24. 24
    With Jabra Call Control for Amazon Connect, Jabra Engage 40, 50 and 50 II headsets can toggle agent state (for example available or break) from a customisable headset button.

    Jabra Call Control for Amazon Connect SDK · Supported functions section · Checked 2026-10-02
25. 25
    Jabra Call Control for Amazon Connect requires a Chromium-based browser such as Google Chrome or Microsoft Edge on Windows or macOS.

    Jabra Call Control for Amazon Connect SDK · Requirements section · Checked 2026-10-02
26. 26
    Jabra Call Control for Amazon Connect requires a web application embedding the Amazon Connect CCP through the Amazon Connect Streams API, Jabra end-user components on the agent computer and a USB-connected Jabra headset.

    Jabra Call Control for Amazon Connect SDK · Requirements section · Checked 2026-10-02
27. 27
    The Jabra Call Control for Amazon Connect SDK is not publicly downloadable; developers request access through a Jabra developer support ticket.

    Jabra Call Control for Amazon Connect SDK · Access section · Checked 2026-10-02
28. 28
    An agent who needs Poly headset controls in both Genesys Cloud (which requires Plantronics Hub and does not support Poly Lens) and Cisco Jabber via HP Poly Studio (which requires Plantronics Hub to be uninstalled) faces conflicting vendor-software requirements on one PC.inferred

    HP Poly Studio Desktop - Supported Devices · HP Poly Studio Desktop - Supported Devices, softphone setup note; combined with Genesys Plantronics article requirements · Checked 2026-10-02
29. 29
    On macOS, HP Poly Studio (Poly Lens Desktop for macOS 2.2 or later) only customises settings and updates software for a device connected by Bluetooth Direct, without call control.

    HP Poly Studio Desktop - Supported Devices · HP Poly Studio Desktop - Supported Devices, macOS note · Checked 2026-10-02
30. 30
    HP Poly Studio Desktop requires any installed Plantronics Hub to be uninstalled before it is used for Cisco Jabber or Avaya softphone call control.

    HP Poly Studio Desktop - Supported Devices · HP Poly Studio Desktop - Supported Devices, softphone setup note · Checked 2026-10-02
31. 31
    HP Poly Studio Desktop is the new name of the Poly Lens Desktop app.

    HP Poly Studio Desktop - Supported Devices · HP Poly Studio Desktop - Supported Devices, introduction · Checked 2026-10-02
32. 32
    HP Poly Studio Desktop provides call control integration for Microsoft Teams, Zoom, Cisco Webex, Cisco Jabber 12.9 or later, Avaya Workplace 3.36 or later and Avaya one-X Agent 2.5.16 or later.

    HP Poly Studio Desktop - Supported Devices · HP Poly Studio Desktop - Supported Devices, UC softphone call control section · Checked 2026-10-02
33. 33
    With a native Bluetooth audio device on Windows 11, the device may suppress the Teams ring tone and play only its built-in ring tone after the computer sends the HFP RING response; Microsoft lists no workaround.

    Known issues when you use Teams certified peripherals · Issue table, row 'No ringing tone during an incoming or an outgoing call.' · Checked 2026-10-02
34. 34
    In Teams cross-cloud meetings, connected peripheral button controls do not sync with the Teams desktop app because syncing is supported only when all participants are from the same cloud; no workaround is listed.

    Known issues when you use Teams certified peripherals · Issue table, row 'During a cross-cloud meeting, button controls on connected peripherals don't sync with Teams.' · Checked 2026-10-02
35. 35
    In Teams, button controls on connected peripherals can stop syncing when a user with accounts on multiple tenants switches accounts; the workaround is to sign in to the intended account and restart Teams.

    Known issues when you use Teams certified peripherals · Issue table, row 'Button controls on connected peripherals stop syncing with Microsoft Teams during a meeting' · Checked 2026-10-02
36. 36
    With a non-certified device paired through native Bluetooth, muting in the Teams app may not update the device's mute state; Microsoft's workaround is to also press the device's own mute control.

    Known issues when you use Teams certified peripherals · Issue table, row 'The audio status doesn't sync between a connected device and Teams.' · Checked 2026-10-02
37. 37
    A Teams certified peripheral may stop syncing after Teams or the computer restarts; Microsoft's workaround is to unplug and reconnect the peripheral.

    Known issues when you use Teams certified peripherals · Issue table, row 'Device might not sync when you restart Teams' · Checked 2026-10-02
38. 38
    When the new Teams desktop app and Skype for Business run at the same time, the Sync device buttons option in Teams is disabled by design; ending the Skype for Business session re-enables it.

    Known issues when you use Teams certified peripherals · Issue table, row 'The Sync device buttons option is disabled when you run Teams and Skype for Business simultaneously.' · Checked 2026-10-02
39. 39
    After a computer wakes from sleep, Teams and connected peripherals may stop responding to each other's mute and unmute requests; Microsoft's workaround is to restart Teams.

    Known issues when you use Teams certified peripherals · Issue table, row 'Mute and unmute functions on connected peripherals don't work.' · Checked 2026-10-02
40. 40
    The Teams Sync device buttons setting under Settings > Devices lets the user use all the buttons on the device, and the Teams button works regardless of the setting.

    Manage your device settings in Microsoft Teams · Manage your device settings in Microsoft Teams, Sync device buttons · Checked 2026-10-02
41. 41
    Peripheral button controls may not work in Teams meetings when third-party apps are using the peripheral or Teams considers it already in use; Microsoft advises exiting third-party apps before joining.

    Known issues when you use Teams certified peripherals · Issue table, row 'Button controls on connected peripherals don't work during Teams meetings.' · Checked 2026-10-02
42. 42
    Devices with an on-screen dial pad such as the Yealink MP50 may not show Teams HID controls for mute, answer or end call because they are not recognised as certified Teams devices.

    Known issues when you use Teams certified peripherals · Issue table, row 'Devices that have a dial pad in the display screen don't show button controls and call details on the device screen.' · Checked 2026-10-02
43. 43
    For EPOS headsets with Webex on Red Hat Linux, Cisco instructs users to download the latest webex.rpm, uninstall the previous version and reinstall with administrator (sudo) privileges.

    Webex App | Headset support · Webex App | Details about headset support, EPOS Linux note · Checked 2026-10-02
44. 44
    For handset models, the one-button make-call-out feature is not supported in Webex.

    Webex App | Headset support · Webex App | Details about headset support, handset note · Checked 2026-10-02
45. 45
    Jabra headset models do not currently work on Webex VDI for Dell ThinOS; Cisco states support will come in a future release.

    Webex App | Headset support · Webex App | Details about headset support, Jabra section note · Checked 2026-10-02
46. 46
    For problems with Poly headsets on the Webex App, Cisco advises installing Poly Lens for Windows version 1.5.0 or above or contacting Poly.

    Webex App | Headset support · Webex App | Details about headset support, Poly section · Checked 2026-10-02
47. 47
    Cisco strongly recommends using a third-party headset with Webex only with the dongle provided by the headset manufacturer.

    Webex App | Headset support · Webex App | Details about headset support, third-party headsets note · Checked 2026-10-02
48. 48
    Chrome blocks WebHID access to security-sensitive devices such as FIDO tokens and to protected usages such as generic keyboards and mice.

    Connecting to uncommon HID devices · Security and privacy section, blocklist · Checked 2026-10-02
49. 49
    The WebHID API is available in Chrome 89 and Edge 89 and later.

    Connecting to uncommon HID devices · Browser support section · Checked 2026-10-02
50. 50
    Chrome's chrome://device-log page shows HID and USB device events and can be used to debug WebHID device access.

    Connecting to uncommon HID devices · Dev tips section · Checked 2026-10-02
51. 51
    A site can revoke its own access to a WebHID device by calling device.forget(), available from Chrome 100.

    Connecting to uncommon HID devices · Revoke access section · Checked 2026-10-02
52. 52
    Firefox and Safari do not support the WebHID API, according to the Chrome developer documentation.

    Connecting to uncommon HID devices · Browser support section · Checked 2026-10-02
53. 53
    WebHID is available only in secure contexts (HTTPS).

    Connecting to uncommon HID devices · Security and privacy / requirements section · Checked 2026-10-02
54. 54
    Under WebHID, a site gains access to a HID device only after the user actively selects that device in a browser chooser opened by navigator.hid.requestDevice(); previously granted devices are returned by navigator.hid.getDevices().

    Connecting to uncommon HID devices · Open a HID connection section · Checked 2026-10-02
55. 55
    Webex Contact Center Desktop WebRTC supports Google Chrome, Microsoft Edge and Mozilla Firefox, but VDI does not support WebRTC.

    System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop, WebRTC browser note · Checked 2026-10-02
56. 56
    Only certain Poly, Jabra and EPOS headsets can end a meeting or hang up a Zoom Phone call, and only when used with their USB dongles and associated vendor applications.

    Supported USB HID devices for the Zoom Workplace desktop app and Zoom Web App · Supported USB HID devices, note on hang up · Checked 2026-10-02
57. 57
    Zoom lists the functions supported by USB HID headsets as accept or decline a meeting invite, accept or decline an inbound Zoom Phone call, and mute the microphone.

    Supported USB HID devices for the Zoom Workplace desktop app and Zoom Web App · Supported USB HID devices, supported functions · Checked 2026-10-02
58. 58
    Zoom instructs users to enable the Sync buttons on headset audio setting if their device is on the supported USB HID list, and to disable it otherwise.

    Supported USB HID devices for the Zoom Workplace desktop app and Zoom Web App · Supported USB HID devices, introduction · Checked 2026-10-02

Documents

Cite this page

WarmTransfer. (2026, October 2). Troubleshooting headset call controls in softphones. WarmTransfer. https://warmtransfer.net/knowledge/headset-control-troubleshooting

@misc{warmtransfer-headset-control-troubleshooting,
  title  = {Troubleshooting headset call controls in softphones},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/headset-control-troubleshooting},
  note   = {Verified 2026-10-02}
}