Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!uunet!rayssd!sud509!heiser@tdw201.ed.ray.com
From: heiser@tdw201.ed.ray.com
Newsgroups: comp.dcom.modems
Subject: Re: Telebit T2500 problem with internal 2400 modem
Keywords: T2500, internal 2400 do not work together
Message-ID: <2373@sud509.ed.ray.com>
Date: 10 Sep 90 19:31:08 GMT
References: <9197@uhccux.uhcc.Hawaii.Edu> <9209@uhccux.uhcc.Hawaii.Edu> <6904@tekig5.PEN.TEK.COM>
Sender: heiser@sud509.ed.ray.com (Bill Heiser - Unix Sys Admin @ Raytheon Company, Sudbury MA)
Distribution: na
Organization: Raytheon Company, Sudbury MA
Lines: 25

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.
>

My Franklin Telecom 2400 seems to be completely unable to understand
Telebit carriers.  When I try to call one, I get the "shhhhhhh", which
continues for whatever the timeout period is, then that's it.  

I *think* my Practical Peripherals 2400 used to work, although I can't
tell now, because that modem seems to have died (it doesn't recognize
a dial tone).  


-- 
Work:    heiser@tdw201.ed.ray.com
	 {decuac,necntc,uunet}!rayssd!tdw201!heiser
Home(1): bill%unixland.uucp@world.std.com -or- uunet!world!unixland!bill
	 Public Access Unix Coming Soon!
Home(2): Bill.Heiser@f240.n322.z1.fidonet.org (BBS: 1-508-655-3848)
Other:	 heiser@world.std.com     (Pub. Access Unix)