modem dialout

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Oles Hnatkevych wrote:
> > do you have a problem with dial-*out* or with dial-*in*? Mgetty's
> > configuration is only relevant for dial-*in*.
> 
> For dial-out. I want modem to dial out and establish a connection.
> Currently I'm doing this by init chat string like:
> 
>  ATZ OK ATDPxxxxxxx\r\d\d\d\d\d\d\d....\d\c CONNECT
> 
> This tells modem to begin dialing and to wait. But this method has
> a disadvantage: if the line is busy mgetty has to wait all these
> \d's before accepting BUSY. And there're LOTS of these \d's.

Mgetty is meant for *dial-in*!!! Don't use mgetty for dial-out, it won't
work.

Use "callback" if you want to dial-out and establish a modem connection
with a "login:"-Prompt.

> I feel that mgetty was not considered as a dial-out getty and
> I see my method of dial-out with mgetty as the only possible (except
> patching the source).

With callback, you can do just this. Set up mgetty as usual, start (from
a root shell) a callback process. The name "callback" is misleading here,
it's more like "give that phone number a login: prompt":

Callback will dial-out, establish a connection, and then hand over to
mgetty for login:-prompting and calling /bin/login.

gert
-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-35655025    gert.doering@physik.tu-muenchen.de
.