Xref: utzoo comp.unix.questions:5083 comp.dcom.modems:1220
Path: utzoo!mnetor!spectrix!clewis
From: clewis@spectrix.UUCP (Chris R. Lewis)
Newsgroups: comp.unix.questions,comp.dcom.modems
Subject: Re: uucp dialer problem
Message-ID: <400@spectrix.UUCP>
Date: 20 Jan 88 16:54:51 GMT
References: <177@oravax.UUCP>
Reply-To: clewis@spectrix.UUCP (Chris R. Lewis)
Distribution: na
Organization: Spectrix Microsystems Inc., Toronto, Ontario, Canada
Lines: 38

In article <177@oravax.UUCP> alex@oravax.UUCP writes:
>
>I am having a problem with the Hayes 2400 dialer in uucp.  I have a
>Vax running 4.3BSD connected to several modems.  All of them work fine
>when accessed via tip or kermit, but when the Hayes 2400 is used by
>uucp, I get the following debugging output:

>OK
>AT&F&D3&C1E0X1ATDT9,14153291916
>OK
>lost line kr - -1
>, root orawest (1/7-09:15-22491) LOST LINE (LOGIN)
>root orawest (1/7-09:15-22491) FAILED (HSM no carrier)

I suspect that your problem is arising from the &F - which does a hangup.

The reason for this is that 4.3 UUCP appears to open the modem with
modem control enabled and SIGHUP and when the &F comes along, 4.3 UUCP thinks
the carrier dropped - even though it shouldn't really be expecting one yet.  
I was just looking at this code a little while ago - tho my message
was different from yours (we're running 4.3 UUCP on Xenix 3) and we
were getting the open never working because carrier wasn't on.

We run our Smartteam 2400 with:

	- modem respects host's DTR
	- modem continuously provides DCD
	- modem continuously provides DSR

Why not try a "Z" instead (which is I think a little less drastic.

Our cu is a little smarter: on a ACU line it opens it O_NDELAY
(don't wait for carrier) and then fcntl's the carrier monitoring later
on when the modem has established a connection.
-- 
Chris Lewis, Spectrix Microsystems Inc,
UUCP: {uunet!mnetor, utcsri!utzoo, lsuc}!spectrix!clewis
Phone: (416)-474-1955