Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!orion.cf.uci.edu!uci-ics!venera.isi.edu!aero!sm.unisys.com!csun!srhqla!magnus!mml
From: mml@magnus.UUCP (Mike Levin)
Newsgroups: comp.mail.uucp
Subject: Re: Increase the time-out in HDB uucico?
Keywords: timeout hdb uucico
Message-ID: <499@magnus.UUCP>
Date: 12 Mar 89 00:32:12 GMT
References: <530@maxim.ERBE.SE>
Reply-To: mml@magnus.UUCP (Mike Levin)
Organization: Silent Radio, Los Angeles
Lines: 54

In article <530@maxim.ERBE.SE> prc@maxim.ERBE.SE (Robert Claeson) writes:
>I'm trying to call a distant site via using uucp via a good V.21bis/
>MNP Class 5 modem. I can log in to the remote system by connecting
>the modem directly to a terminal and using hayes AT commands directly.
>It takes about 50 seconds between I hit return after the dial command
>until I get the login prompt from the other system.
>
>However, when I try to do the same thing using uucp (we're using HDB
>uucp in SVR3.1), uucico seems to time out before the other modem
>answers the call. The Dialers file is set up to send *exactly* the
>same commands to the modem as when I'm using the modem manually.
>Is there a way to increase the timeout in uucico (and cu -- it
>doesn't work either)?

	I had similiar problems when first setting up my Telebits, and
	I didn't like the use of delays, because certain connections,
	under certain conditions, were faster.  So, after a greate deal
	of hacking about, came up with the idea of doing something
	tricky with the CONNECT messages.  Take a look at the following
	entries (these are for telebit) from the Dialers file:


TB300R	=W-,	"" \r\pAT\r\pAT&ES7=50Q0S92=0S95=0S50=1 OK ATDT\T CONNECT\s300-\c-CONNECT\s300
TB1200R	=W-,	"" \r\pAT\r\pAT&ES7=50Q0S92=0S95=0S50=2 OK ATDT\T CONNECT\s1200-\c-CONNECT\s1200
TB2400R	=W-,	"" \r\pAT\r\pAT&ES7=50Q0S92=0S95=0S50=3 OK ATDT\T CONNECT\s2400-\c-CONNECT\s2400

	Note that when expecting the 'CONNECT\s300' (or 1200, or 2400) messages,
	the script is actually saying:

	CONNECT\s300-\c-CONNECT\s300

	Which means:

		Expect the message 'CONNECT 300', and if you time out,  having
		not yet received it, send: (nothing), and then wait for the
		message 'CONNECT 300' until you time out. 

	This seems to do the trick, as I have set the timeout in the modems
	(register S7) for 50 seconds, the modem will ALWAYS time out before
	the script aborts.



						Good luck,


						Mike Levin


-- 
 _            _           
| | ___  ___ |_| ___   Michael Levin     SilentRadio Headquarters- Los Angeles
| |/ ._\| | || ||   \  20732 Lassen Street,    Chatsworth  CA  91311    U.S.A.
|_|\___/ \_/ |_||_|_|  {pacbell|pyramid|csun}!srhqla!levin - levin@magnus.UUCP