Re: Using mgetty automated callback, and the NO CARRIER message.

On 9 Feb 1998, Carey Evans wrote: > Joost Kooij <[EMAIL PROTECTED]> writes: > > > However, with newer ppp's this no longer seems to be sufficient, as > > apparently chat bails out if the DCD signal is gone. I have had to add > > "AT&C0" to the modem init strings, to disable DCD signalling by the

Re: Using mgetty automated callback, and the NO CARRIER message.

Joost Kooij <[EMAIL PROTECTED]> writes: > However, with newer ppp's this no longer seems to be sufficient, as > apparently chat bails out if the DCD signal is gone. I have had to add > "AT&C0" to the modem init strings, to disable DCD signalling by the modem. % man chat [...] HANGUP The

Re: Using mgetty automated callback, and the NO CARRIER message.

On Fri, 6 Feb 1998, David Wright wrote: > I have a chatscript to do callback, which looks like this. > > ABORTBUSY > ABORT"NO CARRIER" <- > ABORTVOICE > ABORT"NO DIALTONE" > "" ATZ > OK ATL1 > OK ATDT5551212 > ogin:

Re: Using mgetty automated callback, and the NO CARRIER message.

David Wright wrote: > > I have a chatscript to do callback, which looks like this. > > ABORTBUSY > ABORT"NO CARRIER" <- > ABORTVOICE > ABORT"NO DIALTONE" > "" ATZ > OK ATL1 > OK ATDT5551212 > ogin:\qmagic-lo

Using mgetty automated callback, and the NO CARRIER message.

I have a chatscript to do callback, which looks like this. ABORTBUSY ABORT"NO CARRIER" <- ABORTVOICE ABORT"NO DIALTONE" "" ATZ OK ATL1 OK ATDT5551212 ogin:\qmagic-login-id\q RING ata ogin:""