Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sgi!vjs@rhyolite.SGI.COM
From: vjs@rhyolite.SGI.COM (Vernon Schryver)
Newsgroups: comp.dcom.modems
Subject: Re: Using Telebits on International Calls
Summary: MCI does not work with TB's
Keywords: telebit, international
Message-ID: <29049@sgi.SGI.COM>
Date: 20 Mar 89 22:52:11 GMT
References: <404@nytim.UUCP> <3474@ficc.uu.net>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 32

In article <3474@ficc.uu.net>, kunkee@ficc.uu.net (randy kunkee XNX MGR) writes:
> 
> ...Last year (Sept. 88) we purchased some TB+ modems along with our
> other half in England hoping to get great e-mail service.  It worked
> great for about 2 or so months and then suddenly we started to really
> eat it on performance....
> 
> Randy Kunkee
> Ferranti International Controls Corporation
> 12808 W. Airport Blvd.  Sugar Land, TX 77478
> UUCP: uunet!ficc!kunkee       ph: (713) 274-5132

I had similar problems with TB's between the Bay Area (in CA) and KY (near
eye sight of Cincinnati) using either MCI or SPRINT.  There didn't seem to
be enough [?bandwidth?] to allow the TB's to work.  They'd retrain every
few seconds, and give up and drop the connection after 10-30 seconds, if
they got carrier at all first.  Turning on the speaker during data was
illiminating, as was checking the numbers while the link was trying to be
up.  A nice fellow at Telebit gave me some magic &J and S112 numbers to
try, but they did not help significantly.

Switching to AT&T solved the problem.  This despite the fact that the MCI
circuits sounded better to my ear.  This bugged me since I hold grudges
against Mother Bell, being able to remember Carterphone and $15/mon DAA's
and accustic couplers and racks of obsolete 103's that they wouldn't allow
us to replace and ...

So my dialer scripts have lots of '10xxx1' prefixes.

Vernon Schryver
Silicon Graphics
vjs@sgi.com