On Tue, Dec 07, 2004 at 12:38:22PM -0500, Gary Thorpe wrote:
>  --- ipt@scraemon.org wrote: 
> > On Tue, Dec 07, 2004 at 09:04:30AM +1100, Smyth, Daniel wrote:
> > > 
> [...]
> > > And chat file
> > > 
> > > 	# /etc/ppp/peers/myisp.chat
> > > 	ABORT BUSY
> > > 	ABORT "NO CARRIER"
> > > 	ABORT "NO DIALTONE"
> > > 	" ATDT<myispnumber> 
> > > 	CONNECT "
> > 
> > Put this whole group of commands in your chat file on one line.  It's
> > been a 
> > while since I've done this, but that is what worked for me.
> > 
> 
> I think the problem may be with the last 2 lines:
> 
> " ATDT<myispnumber> 
> CONNECT "
> 
> Maybe it should be:
> 
> '' ATDT<ispnumber>
> CONNECT
> 
> The original chat script is expecting the string " ATDT<myispnumber> 
> CONNECT " and then send nothing. I don't think it has to be on one
> line, although it can be if you like. See chat(8).

Years ago when I had to use dial up, I read the man page and found that
the instructions did not mesh with the functionality.  This was,
however, on FreeBSD.

For maximum debugging help, I would also add SAY directives to the
script to assist in knowing what steps are being executed.  Also, if you
are going to use multiple lines, escape the carraige returns generated
with back slashes, '\'.  An example,

ABORT BUSY\
ECHO OFF\
ABORT 'NO CARRIER'\
ABORT 'NO DIALTONE'\
SAY "Dialing...\n"\
'' ATDT5551212\
TIMEOUT 120\
SAY "Waiting for connection...\n"\
CONNECT ''\
SAY "Connected.\n"\

Let use know how it turns out.

--
Ian P. Thomas

Destiny is not a matter of chance, it is a matter of choice. It is not a thing 
to be waited for, it is a thing to be achieved.

	- William Jennings Bryan