Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!decwrl!wuarchive!udel!princeton!njin!spcvxa.spc.edu!terry
From: terry@spcvxa.spc.edu (Terry Kennedy, Operations Mgr)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit T2500 problem with internal 2400 modem
Message-ID: <1990Sep7.232331.511@spcvxa.spc.edu>
Date: 7 Sep 90 23:23:31 GMT
References: <9197@uhccux.uhcc.Hawaii.Edu> <9209@uhccux.uhcc.Hawaii.Edu> <1990Sep7.152529.18088@ultra.com>
Distribution: na
Organization: St. Peter's College, US
Lines: 29

In article <1990Sep7.152529.18088@ultra.com>, rmg@ultra.com (Rich Geiger) writes:
> A user at our site also had similar problems coming into our T2500
> with an externel Everex Evercom 24+. He contacted Everex, who sent
> them an updated PROM which fixed the problem. I don't know whether
> this can be taken as evidence that it is Everex (rather than Telebit)
> who was out of spec with regard to the CCIT standard dictating how
> connect speed negotiaion is supposed to be done.

  Yup, the Evercom 24+ modems (both internal and external) used to have a
problem where `unusual' answer tones would confuse them. The 4 pips in the
V.32 answer sequence would do it, and I suppose PEP would as well. The
symptom is that when calling such a modem from an Evercom 24+, you'd hear
the ring, hear the far-end modem pick up, and right after the first V.32
pip you'd get a NO CARRIER on the Evercom 24+.

  This was fixed quite some time ago by a PROM upgrade (27128, I believe).
The FAX card also had the same problem, I don't know if the upgrade for
that one ever made it out (I assume it did, and was just delayed). This
should be a free upgrade from Everex for small numbers of modems. If you
have more than a few (2-3), they may either ask for the old chips back, or
suggest you copy them locally if you have the facility to do so.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, US
	terry@spcvxa.spc.edu	(201) 915-9381

Disclaimer: We're an Everex distributor, but only for internal use. The
policies I stated above were Everex's policies at the time I found the
problem; contact Everex technical support for the latest information.