skip to Main Content

Review: Sennheiser DW Pro2 Cordless Headset

In truth, the only time that I ran the battery completely down is when I used the DW Pro2 USB connected to my desktop. The management software that Sennheiser provides, a program called “HeadSetup,” includes a function called “Continuous Audio.” When enabled this holds the DECT radio active so that all audio events on the computer are played through the headset. This is most appropriate when participating in a Webex or GotoMeeting session where the audio is not being conveyed by a typical soft phone.


Such applications don’t provide hook state information making it necessary to manually force the radio link to be sustained. If I accidentally left the “Always Audio” function engaged the battery would be completely drained by the end of my office day.[pullquote]Supported Soft Phones & UC Clients

  • AOL Instant Messenger
  • Avaya IP Soft Phone v4, v5, v6
  • Avaya One-X Communicator
  • Cisco IP Communicator v2.0+
  • IBM Lotus Sametime Connect
  • Skype[/pullquote]

The HeadSetup application is aware of various soft phones and corporate UC clients. When used with these applications it’s able to manage the hook state of the headset in a manner similar to using an EHS cable with a traditional desk phone.

In my installation this meant clear, simple integration with Skype. When a Skype call arrived merely touching the button on the side of the headset caused the call to be answered. Touch the button again to hang it up.

The HeadSetup application also allows the USB connection to be used to update the firmware in the headset & DECT base.

Sennheiser also provided an “Electronic Hook Switch” (aka EHS) cable suitable for use with the Polycom Soundpoint range of desk phones. I am a little embarrassed to admit that this was my first time using an EHS connection. The EHS cable allows control of phone hook state with a simple touch of the button on one earpiece, making it easy to answer an incoming call even when away from my desk.

I tried the DW Pro2 along side various Polycom models from my VVX-1500 all the way down to the SoundPoint IP335, and even the new VVX-500. In all cases the same EHS cable worked perfectly as long as I also set the phone to expect DHSG type signaling for hook state control. The DW Pro2 manual was also very clear on this matter.

Sennheiser-HSL10-250A slightly different EHS cable supports the use of the DW Series headsets with the entry-level SoundPoint IP 321 and IP 330 models.  However, it’s hard to fathom such a fine headset connected to a sub-$100 SIP phone. Of course, Sennheiser also offers EHS cables appropriate for various other enterprise phones.

Desk phones that don’t support EHS connection can still be used with the DW series through the use of the optional HSL 10 handset lifter. I’ve long felt that such mechanical solutions seem like Flintstone engineering, but some will doubtless appreciate the option.

The manual and literature on the DW Series makes many references to the term “Comfort Calling.” When I dug into this a little I found that the term is used to describe a set of features intended to make it easier to use the headset for extended periods.

For example, the DW Pro2 will monitor the audio to the earpiece for transients. When an unusually transient occurs it will quickly act to drop the audio level in the earpiece. This it does so that you don’t get a painful blast in your ear simply because the party at the far-end drops a coffee cup very near the conference phone.

There are other facets to Comfort Calling, including on-the-fly switching between narrowband and wideband modes. If the headset senses that the call audio doesn’t contain appreciable energy above 3.5 KHz the headset will drop into narrowband mode. This action will ensure an optimal noise floor for the call as well as extend the battery life.

This mode switching came as something of a surprise to me. Puzzled by this behavior I inquired with Sennheiser support who told me that this was deliberate, and in fact a feature. They did suggest that it may be occasionally misbehaved in the current firmware.

They further advised that a minor adjustment to the microphone gain would minimize the occurrence of this transition. I made the adjustment suggested and found the behavior largely eliminated.

The manual for the DW Pro2 includes instructions for pairing multiple headsets with the DECT base. It then describes the ability to conference multiple headsets into one call.

Going even further it describes how to pair the headset alone with another manufacturers GAP compliant DECT base. Just for fun I may some day try to pair it with a Gigaset DECT base. Both of these capabilities underscore the flexibility of the DW Pro2, although they are clearly beyond a typical SOHO use case.

A large part of the measure of any headset comes down to two simple factors; Is it comfortable to wear and how does it sound? The Sennheiser DW Pro2 is very comfortable, even when used for extended periods. In addition, it sounds great. It’s easily the best cordless headset that I’ve ever used.

That said, it’s also one of the more expensive cordless office headsets that you can buy. They are available online but not from very many US vendors. The DW Pro2 can be found online in the $380 range, while the single-ear DW Pro1 I found offered for around $360. An earlier model known as the Office Runner appears to be derived from the DW Office but is available for $299.

Does it make sense to spend that much on a cordless headset? That’s a question you must answer for yourself. However, if you’ve invested in a high-quality desk phone should you compromise on a cordless headset? That’s a bit like putting cheap tires on a fine automobile. You may save a bit of money at the outset, but it ultimately limits the quality of your experience driving.

The DW Pro Series is great hardware. I’m certain that if you should try one you won’t want to give it up.

This Post Has 6 Comments
  1. Another kinda cool unknown feature, is for multiple headsets in a single location. If user a is on a call with the headset, user b can dock his headset on user a’s dock and get added/conferenced into the call.

    1. That’s interesting. I’m kinda regretting getting the Pro2, a Pro1 would have been more appropriate. However, I’ve been using it a lot!

      The value of the auto volume level control provided should not be understated. There are lots of times when the other party is doing things that result in impact noises that can be seriously painful to someone wearing a headset. I was on a US Telecom conf call earlier this week when that very thing happened!

  2. “None of my existing headsets worked with my Polycom Soundpoint IP650 or VVX-1500,…”

    Actually you can use your Voyager Pro UC with these phones by getting the Plantronics MDA200. What they call a UC enabler. I have not personally used it but I set one up for someone with a Soundpoint IP650 who has been using it for the past few weeks. He says he’s been extremely happy with it.

    1. That is interesting. I have a coworker who uses the Voyager Pro. Perhaps I’ll get him one to try.

      It does go to show that I’m not THAT well connected with Plantronics, as I had no idea that such an device was available. A little digging reveals that it was only released in October 2011, so it’s relatively new.

  3. Afraid not. I received my DW Pro2 when the product was still fairly new. It’s been in service a few years now. I replaced the battery once. Very occasionally it fails to charge when connected to the base. When this happens it reports a depleted battery at a potentially inopportune moment, very early in my day.

    I’ve been pondering an effort to clean the contacts on the base and headset to hopefully overcome this problem. If that doesn’t work then I may be looking to replace it.

  4. The DW series all connect to phones, in my case a Polycom VVX, using the RJ-9 headset jack. An adapter cable is required to have this and EHS control. The headset base also has a micro-usb jack for connection to my computer.

    It’s awesome!

Comments are closed.

Back To Top
%d bloggers like this: