mgetty force-init-chat

[Timothy Luoma]

(I am still trying to solve my "connected but can't get anywhere" 
dialin to FreeBSD problem)

Last time I connected but couldn't get anywhere, I believe this was the 
mgetty log:

01/21 01:52:55 yd0  mgetty: experimental test release 1.1.31-Jul24
01/21 01:52:55 yd0  check for lockfiles
01/21 01:52:55 yd0  locking the line
01/21 01:52:55 yd0  lowering DTR to reset Modem
01/21 01:52:56 yd0  send: \dATQ0V1H0[0d]
01/21 01:52:57 yd0  waiting for ``OK''
01/21 01:52:57 yd0  found action string: ``NO CARRIER''
01/21 01:52:57 yd0  init chat failed, exiting...: Invalid argument
01/21 01:52:57 ##### failed in mg_init_data, dev=ttyd0, pid=77061

So I'm wonder if I should use the "force-init-chat" with mgetty config.

All the examples I see say:

QUOTE:
To get the modem back into a "sane" state, you can use the 
force-init-chat chat sequence. The default setup will send the DLE ETX 
characters, to revive voice modems, then the (pause)+++(pause)ATH0 
sequence to pull the modem from data mode to command mode.
UNQUOTE

OK, that sounds great, but how to I use the default setup?  What is the 
force-init-chat line that I should use for 'default'?  I didn't see 
anything in the mgetty.conf file or in Google, except a lot of places 
quoting the above. It doesn't say how to use the default, or how to 
enter "pause" in the expect/send pairing, or how to send the DLE ETX 
characters

TjL