1 item
Use your headset buttons in the Microsoft Teams web app to answer, reject and end calls and to mute or unmute. Bring headset call control to the Microsoft Teams web app. The Teams desktop app supports the call buttons on your headset, but the browser version does not, for example on Linux or ChromeOS. This extension closes that gap. Features - Incoming calls ring on your headset; answer or reject them with the headset buttons - Hang up from the headset - Busy light turns on during calls and meetings - Mute state stays in sync between headset and Teams, in both directions The Extension supports several headset vendors via the library "softphone-vendor-headsets" https://github.com/purecloudlabs/softphone-vendor-headsets#readme Headsets connected via USB or a USB dongle are supported. Headsets paired directly with your computer's Bluetooth are not. Tested with - Jabra Evolve 60 / Jabra Link 370 - Jabra Evolve 75 SE / Jabra Link 380 - Jabra Evolve2 65 - Jabra Engage 75 - Poly BT700 dongle Getting started 1. Open Teams in Chrome and allow microphone access, so the extension can recognize your headset by its name. 2. The headset connects automatically. If Chrome needs permission to access it, click the extension icon, then "Connect", and select your headset. 3. The icon turns green when the headset is connected. Open source: https://github.com/neffs/chrome-extension-teams-hid-telephony
Oct 28, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.