Getting a wireless headset working on a Cisco phone is really two questions: which headset, and which remote-answer adapter for your exact Cisco model. The second one is where people get stuck, because the same headset needs a different adapter depending on whether your phone is a 79xx, an 8945, a DX80, or an SPA. Here's the mapping, by headset brand.
Quick answer
Last updated July 2026
First: handset port, not headset port
This trips up almost everyone. Poly, Jabra, and EPOS wireless headset bases are designed to install into the handset jack on your Cisco phone — the port the curly handset cord plugs into — not the dedicated headset jack, even when the phone has one. The headset jack is built for corded headsets and won't drive a wireless base correctly.
Myth
My Cisco phone has a dedicated headset port, so that's obviously where the wireless headset base goes.Reality
It isn't. The headset port is designed for corded headsets. A wireless base needs the handset port to work properly — you unplug the handset cord from the phone, plug it into the base, and run the included telephone interface cable from the base back to the phone's handset port. Plugging a wireless base into the headset jack is one of the most common reasons a setup doesn't work as expected.One exception worth knowing: there's an alternate configuration for Poly headsets where you don't want remote answering at all. In that setup, the base goes into the headset port, you leave the handset cord alone, set the compatibility dial to position 4 and the Tx switch to "A," set IntelliStand to the down ("=") position, and answer calls by pressing the headset button on the phone itself. You get wireless audio and mobility, but you have to be at the phone to answer.
Poly (Plantronics) wireless headsets on Cisco
The Poly CS540 is the standard pairing and remains current. For tri-connectivity across a desk phone, computer, and mobile, the Poly Voyager Focus 2 adds Class 1 Bluetooth and Digital Hybrid ANC, and can leave the office with you.
Which adapter you need depends on the phone:
| Cisco model | Poly adapter |
|---|---|
| 6945, 7821, 7841, 7861, 7942G, 7945G, 7962G, 7965G, 7975G, 8811, 8841, 8845, 8851, 8861, 8865 | Standard Cisco EHS cable (built-in EHS) |
| SPA 512G, SPA 514G, SPA 525G, SPA 525G2 | APC-45 (connects to the phone's 2.5mm headset jack) |
| 8961, 9951, 9971 | APU-72 (uses the phone's built-in USB port) |
| 8941, 8945, 8945G | APC-82 (headset port on the back of the phone) |
| SPA 303, SPA 501G, 502G, 504G, 508G, 509G, SPA 921, 922, 941, 942, 962 | HL10 mechanical lifter (no built-in EHS) |
Expansion modules (sidecars): if the phone has a 7914 expansion module, plug the module into the phone's AUX connector, connect the APC-43 control connection into the expansion module, then use a 40287-05 adapter to extend the audio input to reach the phone's headset jack.
Enable EHS before connecting. On phones with built-in EHS, the capability must be turned on before you attach the adapter, so the phone resets and is ready for it.
Jabra wireless headsets on Cisco
The Jabra Engage 65 SE is the current Jabra wireless headset for Cisco environments, offering up to 490 feet of range and high-encryption DECT that supports more headsets in one location without interference. It replaces the discontinued Jabra Pro 920, Pro 925, and the original Engage 65 and 75 that older Cisco bundle lists reference.
| Cisco model | Jabra adapter |
|---|---|
| 69xx, 79xx, 88xx series with built-in EHS | Cisco-certified Jabra EHS cable (see our EHS guide for the Link version by headset generation) |
| 8941, 8945, 8945G | Jabra Link 41 (headset port on the back of the phone) |
| DX650, DX70, DX80 | Jabra Link 30 (uses the USB port on the side of the phone) |
| SPA 303, 501G, 502G, 504G, 508G, 509G, 512G, 514G, 525G, 525G2, SPA 921, 922, 941, 942, 962 | GN1000 mechanical lifter |
For the exact Jabra Link cable version on EHS-capable Cisco phones — which varies by headset generation — see our complete EHS cable compatibility guide.
EPOS wireless headsets on Cisco
EPOS (formerly Sennheiser) uses its own CEHS-CI adapter line for Cisco, and the numbering maps to phone capability rather than series:
| Cisco model | EPOS adapter |
|---|---|
| 6821, 6841, 6851, 6921, 6941, 6945, 6961, 7821, 7841, 7861, 7931G, 7940(G), 7941(G), 7942G, 7945(G), 7960(G), 7961(G), 7962G, 7965G, 7970(G), 8811, 8841, 8845, 8851, 8861, 8865 | CEHS-CI 01 (connects to the headset port and AUX port) |
| 8800 series, 9900 series, 8961 (USB-equipped) | CEHS-CI 02 (uses the side USB port) |
| 8941, 8945, 8945G | CEHS-CI 04 (headset port) |
| SPA 303, 501G, 502G, 504G, 508G, 509G, 512G, 514G, 525G, 525G2, SPA 921, 922, 941, 942, 962 | HSL10 II mechanical lifter (no built-in EHS) |
| DX650, DX70, DX80 | HSL10 II lifter, or connect the base directly to the phone's USB port |
On the headset side, the EPOS IMPACT D10 II is the current single-connectivity wireless model, with up to 500 feet of range and a magnetic charging base. For dual or triple connectivity across a desk phone, computer, and Bluetooth device, EPOS now sells that range under the IMPACT 5000 series naming — the successor to the older SDW 5065 and SDW 5016 models that older Cisco lists reference.
Enabling hookswitch control on the phone
Even with the correct adapter, remote answering won't work until the phone is configured for it. On the phone, press the Settings button (checkbox icon), select Device Configuration, then Media Configuration, and confirm that Wireless Headset Hookswitch Control is set to Enabled. If it shows as Disabled, that's typically controlled centrally — contact your phone system administrator.
Fixing echo on a Cisco phone
If you're getting echo or side tone with a wireless headset on a Cisco phone, the fix usually isn't on the headset at all. In Cisco Call Manager, set the Handset/Headset monitor variable for that phone to Disabled. This routes the call to the headset only when the headset is in use, which resolves the echo.
Does a wireless headset plug into the Cisco headset port or handset port?
The handset port, in almost all cases — even if your Cisco phone has a dedicated headset jack. The headset jack is designed for corded headsets and won't drive a wireless base properly. The exception is a specific no-remote-answer configuration where the base uses the headset port and you answer at the phone.
What adapter do I need for a Cisco 8941, 8945, or 8945G?
These models need a brand-specific adapter that differs from the standard Cisco EHS cable: the APC-82 for Poly headsets, the Jabra Link 41 for Jabra, and the CEHS-CI 04 for EPOS. All three connect to the headset port on the back of the phone.
What adapter works with Cisco DX650, DX70, or DX80 phones?
These phones have a USB port on the side. Jabra headsets use the Link 30 adapter. EPOS headsets can either use the HSL10 II lifter, or connect the base directly to the phone's USB port depending on the model.
Why do I have echo on my Cisco phone with a wireless headset?
The fix is usually in Cisco Call Manager rather than on the headset. Set the Handset/Headset monitor variable for that phone to "Disabled," which routes the call to the headset only when the headset is actually in use.
Do Cisco SPA-series phones support EHS?
Mostly not. The SPA 303, 501G, 502G, 504G, 508G, 509G, 921, 922, 941, 942, and 962 need a mechanical lifter (HL10 for Poly, GN1000 for Jabra, HSL10 II for EPOS). The exceptions are the SPA 512G, 514G, and 525G2, which work with the Poly APC-45 adapter.
What replaced the Savi 8220, 8240, and Jabra Pro 920 for Cisco setups?
All are discontinued. The current Poly options are the CS540 for desk-phone use and the Voyager Focus 2 for tri-connectivity with Bluetooth. On the Jabra side, the Engage 65 SE replaces the Pro 920, Pro 925, and the original Engage 65 and 75.
The headset choice is the easy part — the adapter is where Cisco setups go wrong, and the same phone series can need different hardware depending on the exact model number. Call our team at 877-999-3838 with your Cisco model number and headset brand, and we'll confirm the right adapter before you order.
Comments (0)