NTEX14AA, NTEX14AB, NTEX14AC USB Audio Adaptors

I was in error. The NTEX14AA (No buttons on unit);
also has a built-in message waiting indicator light.

I have searched many more documents, and I see why I got two different ideas about whether the NTEX14AA had a message waiting light or not. I have a really nice hi-res jpeg I downloaded from Nortel a year or so ago, and that picture shows no light, yet the lower resolution picture all the online vendors are copying from each other's web sites does indeed show a light on the unit. So I can only guess that the vintage of the unit determines whether or not the unit has a message waiting light. Also, I found information online that indicates that the NTAB14AB (and NTEX14AC of course) has a longer USB cable than the cable supplied with the NTEX14AA. The NTEX14A series are meant for use with the i2050 Software Phone Client Software.

For those of you confused by the vendors selling various units described as NTEX14 USB adapters, here is a list of the USB adapters meant for use with 2050 Mobile Voice Client:

NTEX14MA - Adapter Only
NTEX14MB - With GN Netcom Dura Plus Monaural Headset
NTEX14MC - With GN Netcom Dura Plus Monaural Headset & MVC Software

A very nice picture of the MVC (NTEX14M Series) can be seen here:


Both software products contain the number 2050,
and both USB adapter series start with NTEX14, thus explaining the confusion resulting.

Hi there,

The NTEX14AA without message waiting light is manufactured for Nortel by Algo Communications. Algo also solds an almost identical device under its own brand, they name it "ALGO 4900 USB ATA", USB Analog Terminal Adapter (ATA) for Nortel IP Softphone 2050.

They provide a full brochure, tech specs, user guide and even a firmware upgrade. Maybe at least the documentation could be of use for the NTEX14AA.

The links:
- Product Overview
- Brochure (PDF)
- User Guide (PDF)

The only difference I've noticed between the Nortel NTEX14AA that I own and the Algo 4900 (apart from the brand logo) is that the Algo features a full RJ-11 connector that allows you to plug an analog telephone or so, while the Nortel NTEX14AA only features a 4P4C connector for plug in a handset or a headset. Well, either this is a real difference or maybe I have a really old version of the NTEX14AA.

By the way, I've tested it on a Windows XP Pro SP2 PC and it's recognized as a “USB Audio Device”. It's funny to listen to my mp3's on a phone handset ;-)

That's all so far. I hope this information will be of use for someone.

Regards from Spain,

-- Wayfarer

P.D. "Algo" is a funny brand name for a spaniard... as "algo" in spanish mean "something".

Wayfarer,
Thank you for your input on this subject. It can be difficult to track down information on these devices.

I think it important that the differences between the Algo USB ATA and the NTEX14AA be made clear. The only thing they have in common is appearance and manufacturer (Algo). A handset should never be plugged into the ATA due to the fact that the ringing voltage could damage the handset, and the load the handset would put on the ATA during ringing cycles could possibly damage the ATA as well.

Algo has manufactured several specialty devices for Nortel over the years and it is interesting how some items get the Nortel labelling (thus requiring the item to be purchased through Nortel's distribution network) and others get the Algo labelling, allowing them to be purchased under much less restrictive circumstances.

I can't say that I would want to rely on the USB documentation to use the NTEX14AA.

You can configure windows to play your sounds
(other than the telephone conversation)
by visiting the control panel/sounds & audio devices
and selecting the audio tab

(this assumes you are using Windows XP)

and setting your playback and recording devices to be your sound card or built-in audio hardware.

This, of course, must be done after you have installed the USB audio adapter and configured the i2050 SoftPhone.

Why Nortel chose not to tell us this is beyond me, as it is the single most annoying factor involved with the installation of these devices. It seems windows likes to abandon your regular audio devices and prefer the USB device once it is detected.

But now you have the fix!