Xref: utzoo comp.sys.att:4109 comp.unix.microport:1429 comp.sys.ibm.pc:18491
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!pyramid!ctnews!starfish!cdold
From: cdold@starfish.Convergent.COM (Clarence Dold)
Newsgroups: comp.sys.att,comp.unix.microport,comp.sys.ibm.pc
Subject: Re: AT&T 386 UNIX Vr3.1
Message-ID: <666@starfish.Convergent.COM>
Date: 29 Aug 88 16:16:33 GMT
References: <171@banzai.UUCP>
Organization: Convergent Technologies, San Jose, CA
Lines: 23

From article <171@banzai.UUCP>, by john@banzai.UUCP (John Canning):
> In article <145@carpet.WLK.COM> bill@carpet.WLK.COM (Bill Kennedy) writes:
>>AT&T's uugetty doesn't get into debates with an intelligent modem who wants
>>to talk about answering the phone.
> 
>     However, uugetty is not smart enough to program the modem when you
>     first turn the system on.  You must first call a bogus number before
>     the modem will be set to answer.
You could always run a little script from *rc:

cu -t -l tty001<<Q
~!sleep 1
AT
~!sleep 1
ATAA
~!sleep 1
~.
Q

But even that is unnecessary if you have DTR driven by the system, and leave
the modem set for auto-answer.  The modem I've used won't answer if DTR is low.
DTR shouldn't go high until uugetty is started.  That way, the modem doesn't
answer if the system isn't up, but always answers if the system is up.