Path: utzoo!utgpu!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!pyramid!vsi1!lmb
From: lmb@vsi1.UUCP (Larry Blair)
Newsgroups: comp.dcom.modems
Subject: Re: Low speed and Telebit modems
Keywords: Telebit 2400bps 1200bps
Message-ID: <1205@vsi1.UUCP>
Date: 10 Nov 88 22:07:34 GMT
References: <7307@daver.UUCP>
Reply-To: lmb@vsi1.UUCP (Larry Blair)
Distribution: na
Organization: VICOM Systems Inc., San Jose, CA
Lines: 29

In article <7307@daver.UUCP> dlr@daver.UUCP (Dave Rand) writes:
>Has anyone (else) had problems with connections to Telebits,
>when calling at low speed? I have heard reports of problems
>at 1200 bps, when calling into a Telebit. Recently, I have
>had a great deal of problems with another site calling into
>my Telebits at 2400 bps - no files longer than a few K would
>transfer.

I wonder...  I was going to post on a similar problem.  Maybe they're
related.

I talk to a site that has severe input speed problems.  They are unable
to receive and process uucp packets faster than about 150 cps during the
day.  The TB buffers about 10K of packets, so the time between when my
system sends the last packet of a news batch and when the "CY" aknowledging
complete reception is consistently over 70 seconds; greater than the
timeout in my uucp.  The problem didn't occur with the X. files or with
short mail messages, since the buffer never filled.

The solution I implemented was to increase the timeout value to about
120 seconds.  A better solution would be the ability to select the
buffer size in the TB; something I requested back when RLS posted his
"what would you like to see" article.

Btw, the way to tell if this is happening to you is if you see a lot
of failures of the "expected C, got FAIL" type.

-- 
Larry Blair   ames!vsi1!lmb   lmb%vsi1.uucp@ames.arc.nasa.gov