Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!haven!mimsy!midway!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.questions
Subject: Re: cu & uucp timeout
Message-ID: <1990Dec22.054846.9742@chinet.chi.il.us>
Date: 22 Dec 90 05:48:46 GMT
References: <658@hewey.dms.cdc.com> <2433@motcsd.csd.mot.com>
Organization: Chinet - Public Access UNIX
Lines: 18

In article <2433@motcsd.csd.mot.com> brian@motcsd.csd.mot.com (Brian Smithson) writes:

>>... I've found out that cu & uucico have built time time out values of
>>40 seconds.  That is they assume "no answer" if the other end doesn't
>>answer in 40 seconds.  

>You can work around it by adding some delay in your dialer script before
>you expect the CONNECT message.  For example:
>telebit	=,-,	"" \pATZ\r\c OK\r ATDTW\T\r\c "" \d\d\d\d\d\c CONNECT

Even better, use the -alternate- syntax with a null "send" to add a second
attempt by changing the CONNECT to CONNECT-\c-CONNECT.  This has the
advantage of seeing the CONNECT immediately if it happens instead of always
forcing a fixed delay.  It may also be necessary to tweak an S-register
in the modem to increase the time it will wait as well.

Les Mikesell
  les@chinet.chi.il.us