Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!uxc!tank!nucsrl!vcc
From: vcc@eecs.nwu.edu (Guest from Vogelback)
Newsgroups: comp.unix.xenix
Subject: Re: Telebit setup && 386/ix && modem not answering
Message-ID: <3700018@eecs.nwu.edu>
Date: 21 Jan 89 17:34:39 GMT
References: <344@focsys.UUCP>
Organization: Northwestern U, Evanston IL, USA
Lines: 15

I don't have a telebit, but I just recently experienced this problem with
a vanilla 2400 baud modem I was setting up on someone's machine.

His machine had the same problem--everything worked but when uucico was
done for some reason it wasn't calling ungetty to wake login up.

I tried uucico with -x9 and found that when the call was done, uucico
wanted to send some more Hayes codes to the modem.  It was waiting for
the "OK" back from the modem, but since we had disabled result codes it
was timing out.  Unfortunately, it barfed and never called ungetty.

The fix was to configure the modem to send the result codes.  The modem
should not echo the command strings you send it, however.

Rich Skrenta