
For the past week I’ve had a Plantronics MDA200
The MDA200 is a cute little box. It measures a little less than 4” on a side and just under 1” tall.
It has a total of five connections:
- USB connection to a host computer
- 3.5mm EHS connection to a desk phone
- RJ-45 audio connection to a desk phone
- Coax power connection
- Front USB port for the headset, BT or DECT dongle
The MDA200 comes with one removable cable that’s terminated in an RJ45 at one end and RJ9 at the other. This cable provides call audio to/from the MDA200. There’s a tap midway along that cable that allows it to be inserted between a phone and its handset. In this manner the MDA200 accommodates phones that don’t have a headset jack.
The MDA200 also sports a USB cable that’s permanently attached. This is used to connect to a nearby computer and provides power to the device. An optional power supply allows the MDA200 to be used without a USB connection.
Since all of the Polycom phones that I use have an RJ9 headset jack I only needed to connect the ends of the headset cable. The phone’s handset remained independent of the wiring to the MDA200.
To have control of hook switch status via the headset & MDA200 I had to order the Plantronics APP-5 Polycom Hookswitch cable.
This cable has an RJ9 and 5 pin connector at one end, another RJ9 and a 3.5mm plug at the other end. It’s a truly curious beast. You probably won’t find this cable at any local retailer. It’s not cheap either, costing around $50 from Amazon.
The 5 pin plug fits the EHS jack on the various Polycom desk phones that I tried. In my case that was a VVX-1500, VVX-500, IP650 and IP335. The RJ9 connectors on each end of the the EHS cable remained unused.
With the two cables connected appropriately, the BT300 dongle plugged into the front of the MDA200 and the attached USB cable plugged into my PC the entire rig was almost ready to roll. All that remained to was to navigate the menus on the IP335 and ensure that it was set to expect Plantronics type EHS signaling.
With this setting confirmed I began by trying the Voyager Pro UC v2 with the SoundPoint IP335.
The MDA200 has two buttons on its top; one denoting a computer, the other the desk phone. Tapping the button for the desk phone took the IP335 off-hook, presenting dial tone in the Voyager Pro UC. Tapping the button again hung up the phone, abandoning the call.
The main button on the Voyager Pro was also engaged in control of hook state. When a Skype call arrived at my PC simply tapping the button on the headset caused the call to be answered. The calling party was presented on the Voyager Pro UC.
In all cases where HDVoice was possible the MDA200, Voyager Pro UC, IP335 combination presented wideband audio. Calls arriving via the PSTN suffered related indignities, arriving as G.711 encoded narrowband streams…no fault of the gear I had locally installed.
In the case of the Voyager Pro UC the multi-point pairing feature came in very handy. The headset was able to handle calls on my cell phone interspersed with calls via my PC or the IP335. It was a reasonably painless process taking calls from any source.
Of course, the Voyager Pro UC and BT300 supported only limited cordless range. Hoping for something more flexible I tried the Plantronics Savi Go with the BUA200 USB attached Bluetooth dongle. Happily, that combination of phone, interface & headset worked just as well. However, the Class 1 Bluetooth radio provided the additional cordless range that I expected.
With the Voyager Pro UC I was able to start or end a call from the headset. With the Savi W430 the button on the headset controlled the DECT radio link but not the hook status of the current call. To alter the hook status of the current call I had to use the buttons on the MDAA200 or the IP335. This was a bit less convenient that the other two headsets.
I double-checked the Plantronics software that I had on my PC to ensure that the D100 DECT dongle for the Savi W430 was running the most current firmware, which seemed to be the case.
It’s worth considering the mechanical reality of how the various pieces involved come together to provide a solution.
The audio cable and the EHS cable are not exactly perfect companions to the MDA200. As you can see, the EHS cable has a right-angle style 3.5mm plug. Given the recessed connector apron of the MDA200, the EHS cable doesn’t fit nicely unless your MDA200 is sitting at the very back edge of your desk, which seems very unlikely. Alternatively, you can rotate the right-angle connector as shown. However, that makes it interfere with the RJ45 end of the audio cable. Certainly less than elegant, the three parts present an imperfect, but workable combination.
The economics of this arrangement also bears some examination. Street price on the Voyager Pro UC is around $120. The MDA200 runs around $80, and the EHS cable another $50. That’s $250 to address all three use cases; mobile, desk phone and computer.
Plantronics MDA200 allows their USB connected headsets, whether wired or wireless, to be transparently used with two or possibly three devices at a time. It works as promised and there’s little doubt that it’s very convenient.
If you already have something like one of the Voyager Pro series you can definitely use the MDA200 to extend the utility of the device you already own. Using the same headset in the office, whether with a desk phone or computer, makes perfect sense, especially when it’s a good quality, HDVoice capable headset.
If you don’t expect to see any benefit from sharing the same Bluetooth headset between your PC, desk phone and cell phone then the MDA200 may not be such a compelling solution. For example, the combined cost of the MDA200, EHS cable and Savi W430 is well into the range where there are much more compelling cordless headset solutions from various companies.
Finally, from the perspective of a wired USB headset the MDA200 is clearly a hit. It lets you take a relatively low-cost headset from the Blackwire Series and use it with a proper desk phone as well as a range of soft phones. What’s not to like about that?