Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!tut.cis.ohio-state.edu!osu-cis!att!alberta!ubc-cs!van-bc!sl
From: sl@van-bc.UUCP (pri=-10 Stuart Lynne)
Newsgroups: comp.dcom.modems
Subject: Re: using TB+ modem to call slow and PEP sites
Keywords: telebit modem
Message-ID: <2239@van-bc.UUCP>
Date: 17 Feb 89 18:10:44 GMT
References: <822@vicorp.UUCP> <2833@stpstn.UUCP>
Reply-To: sl@van-bc.UUCP (pri=-10 Stuart Lynne)
Organization: Wimsey Associates, Vancouver, BC.
Lines: 39

One problem I havn't yet resolved (although I havn't tried to hard) is that
if I use the TB+ to dial out at 2400, and the *next* incoming call is in PEP
mode; the modem sets the speed to 2400 bps. 

I have:

	S50=0		auto speed determine
	S51=255		auto speed select
	S52=2		DTR resets
	S53=2		DSR on when DCD on
	S58=2		CTS/RTS
	S66=0		Interface speed not locked
	S68=255		Use S58

The sequence of events I see:

    cu -ltty1a -s2400 dir	Dialout at 2400 bps
    AAA				autobaud
    ATDTxxxx			autodial
    login
    ~.  			Close port, DTR dropped for 1 second to reset

    Getty opens port, DTR raised
    Incoming call by another TB+, their S50=255
    Connection made in PEP mode
    Speed of connection set at 2400 bps by TB+, not 9600 as S51 would
    indicate


This was very reproducible here. It basically prevents me from using the TB+
for outdial to 2400 bps sites because I have no reliable way to get that
next call answered properly. It's very annoying to be connected in PEP mode
and have uucp transfer data at 2400bps not 9600bps.

I have a 2400bps line so it hasn't been a big problem. Of course if it was
fixed I would probably junk it in favour of a third TB+.

-- 
Stuart.Lynne@wimsey.bc.ca {ubc-cs,uunet}!van-bc!sl     Vancouver,BC,604-937-7532