From: bob@consult.UUCP (Bob Willey CDP)
Newsgroups: biz.sco.general
Subject: Re: uugetty problems
Date: 11 Sep 92 04:06:20 GMT
Reply-To: bob@consult.UUCP (Bob Willey CDP )
Organization: CCS Enterprises, Inc. - Easton, MD

>Bill Irwin writes:
>> jmiller@wendy.bowlgreen.oh.us (Jim Miller) writes:
>Here's a message that Don Draper posted in this place a few months ago:
>From: Don Draper <dond@sco.COM>
>Subject: non-answering modem solution
>Here's an easy and little-known solution to a common modem problem.
>It took me a long time to solve this one.  Hope it comes in handy
>and saves you some of the frustration that this cost me...
>After I call out on my modem, it no longer answers the phone.
>
>PROBLEM:  My modem isn't being reinitialized for dial-in.  Disabling
>	  and re-enabling the port doesn't help.   The modem must be
>	  turned off and on before it will answer the phone again.
>
#CAUSE:    Whenever getty (or uugetty) is run, it checks the file
#	  /usr/lib/uucp/Devices to see if the tty port it is running
#	  on is a modem port.  If it finds the tty device in the Devices
#         file, then getty checks to see if a binary dialer or Dialers 
#	  file entry is being used.  If one of these is found, then getty
#	  attempts to hang up the modem line and initialize the modem for
#	  the next caller.  If a binary dialer is specified on the Devices 
#	  file line, then getty calls that dialer with the "-h" flag.  If 
#	  a Dialers file entry is specified instead, then getty calls uuchat,
#	  passing it the "&" line from the Dialers file entry.
#	  getty uses the first entry which it finds in the Devices file.
#	  The tty device name is "regularized" (i.e. tty1a and tty1A are
#	  considered equivalent).  This means that if an entry such as:
#	  Direct tty1a - 2400 direct
#	  appears before the ACU entry for the same tty port, such as:
#	  ACU tty1A - 2400 hayes2400 \D
#	  then getty will decide that no binary dialer or Dialers file
#	  entry is being used - and the modem won't be initialized for
#	  dial-in.
>

This was very helpful, but did not solve our problem.  We get the uuchat
procedure hung up on the port occassionally and must kill the uuchat
process and then everything will fire up just fine.  We do have multiple
entries in the /usr/lib/uucp/Devices file:

ACU tty2A - 2400 tb2400
ACU tty2A - 9600 tb9600
ACU tty2A - 19200 tbfast
   (Note:  everything else is commented out)

And in the Dialers file, it contains the following:

#	@(#) Dialers 1.1 88/11/16 
#  Telebit dialers
#  tb1200, tb2400, tbfast for 1200, 2400 and 19200 baud.
#tb1200	=W-,	""	A\pA\pA\pT OK ATS50=2DT\T CONNECT\s1200
tb2400	=W-,	""	A\pA\pA\pT OK ATS50=3DT\T CONNECT\s2400
tb9600	=W-,	""	A\pA\pA\pT OK ATS51=4S111=30S50=255DT\T CONNECT\sFAST
tbfast	=W-,	""	A\pA\pA\pT OK ATS51=5S111=30S50=255DT\T CONNECT\sFAST

#&tb1200	=,-,	""	A\pA\pA\pT OK ATHQ6S50=0S0=1 OK
&tb2400	=,-,	""	A\pA\pA\pT OK ATHQ6S50=0S0=1 OK
&tb9600	=,-,	""	A\pA\pA\pT OK ATHQ6S50=0S0=1 OK
&tbfast	=,-,	""	A\pA\pA\pT OK ATHQ6S50=0S0=1 OK

#  This entry will reset the Telebit modem to desired modes
tbreset	=,-,	""	A\pA\pA\pT OK ATHQ6S45=255S50=0S51=255S52=2S53=3S54=3 OK ATS

Normally everything works just fine, but every once in a while (especially
when I leave the office for a few days), it just hangs up and when I do a
ps -ef  there sits uuchat on the port at 2400 and has been for many hours  
(or days)...  It is really just a nusiance factor, not a major problem.
The modem we have is a Telebit T18PC internal modem
With the above settings we can no longer connect to anomaly except at 2400.
We used to be able to, but I suspect they have changed to newer modems and
are no longer compatible.  (seperate issue).

Thanks for any input.

-- 
>.. Bob Willey, CDP          ..  |  ..  uunet!consult!bob  bob@ccs.com   ..<
>.. CCS Enterprises, Inc.    ..  |  ..   Office: (410) 820-4670          ..<
>.. P.O. Drawer 1690         ..  |  ..      FAX: (410) 476-5261          ..<
>.. Easton, Maryland 21601 ......|......... BBS: (410) 476-5098 ...........<