Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!convex!linac!uwm.edu!lll-winken!gauss.llnl.gov!casey From: casey@gauss.llnl.gov (Casey Leedom) Newsgroups: comp.dcom.modems Subject: Re: Telebit and V.32bis? Message-ID: <90562@lll-winken.LLNL.GOV> Date: 31 Jan 91 20:28:52 GMT References: <1991Jan31.063258.15906@bilver.uucp> Sender: usenet@lll-winken.LLNL.GOV Reply-To: casey@gauss.llnl.gov (Casey Leedom) Distribution: comp Organization: Lawrence Livermore National Laboratory Lines: 25 Nntp-Posting-Host: gauss.llnl.gov | From: bill@bilver.uucp (Bill Vermillion) | | One thing the PEP in a TBit modems does is connect where others | wont, or when they do connect won't stay connected. | | I have a site that was using V.32 (not HSTs) on a leased line that | would typically drop 4 to 6 times per day. Nothing the two phone | companies involved could do would improve it for more than a few | days at a time. That's true and I had the same problem with V.32 connections with my T2500. But, I think that this may be a function of the buggy Rockwell chip set. The T1600 I'm evaluating has yet to drop a connection. I've had it up for five days at a time without any connection losses *or* performance degradation that I could see, while the best my T2500 was ever able to do was hold a connection for five hours. I've tested the T1600 connecting to both T2500s and another T1600 (though the longest I tested the T1600 to T2500 connection was 24 hours.) It works great. I think a lot of the V.32 connection horror stories we have all heard and possibly dealt with ourselves are a function of the single common denominator in most V.32 modems: the Rockwell chip set. Casey