Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!uhccux!todd
From: todd@uhccux.uhcc.Hawaii.Edu (Todd Ogasawara)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit T2500 problem with internal 2400 modem
Keywords: T2500, internal 2400 do not work together
Message-ID: <9283@uhccux.uhcc.Hawaii.Edu>
Date: 8 Sep 90 19:05:17 GMT
References: <9197@uhccux.uhcc.Hawaii.Edu> <9209@uhccux.uhcc.Hawaii.Edu> <6904@tekig5.PEN.TEK.COM>
Reply-To: todd@uhccux.UUCP (Todd Ogasawara)
Distribution: na
Organization: University of Hawaii
Lines: 28

In article <6904@tekig5.PEN.TEK.COM> kevinc@tekig5.PEN.TEK.COM (Kevin E Cosgrove) writes:
>I've been following the story on this because I use an Everex Evercom-24
>to call UUCP neighbors of mine; they run Telebit modems.  Everything
>will run fine for a week or so at a time for a given neighbor.  But
>every so often the Everex won't recognize the Telebit's carrier signal.
>Also every so often the Telebit won't autobaud down (around?) to 2400.
>
>These two experiences sound like they could be related.  Any guesses?

I think there was some discussion related to this problem not too long ago
that was very helpful to me in dealing with problems I had when using
recent model external Everex modems to dial into T2500 modems. It looks
like the more recent Everex modems (old ones do not have this problem) are
"too smart for their own good" and get "confused" by the initial non-PEP
T2500 tones. The collective suggestion of the net was to place an
electronic ear muff on the Everex for a few seconds after connect to
prevent this 'confusion'. The technique is to simply use the "," after
dialing. E.g.,

	ATDT 123-4567,,,,

I've found that using a 6 (3 commas) to 10 (5 commas) second delay does the
trick...todd
-- 
Todd Ogasawara, U. of Hawaii
UUCP:		{uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!todd
ARPA:		uhccux!todd@nosc.MIL		BITNET: todd@uhccux
INTERNET:	todd@uhccux.UHCC.HAWAII.EDU