Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Switching modem to answer

0 views
Skip to first unread message

Aaron Baugher

unread,
Sep 14, 1999, 3:00:00 AM9/14/99
to
I've been asked to do some administration on a remote
system. It has a modem that's been used for dialing out,
but it's not set to answer. I'm looking for a
quick-and-easy way to switch it to auto-answer; something I
can lead someone through over the phone. Once I get into
the system I can make it permanent. Any way to do this in a
command line or two?


Thanks,
Aaron
--
Aaron Baugher - abau...@rnet.com - Quincy, IL, USA
Extreme Systems Consulting - http://haruchai.rnet.com/esc/
CGI, Perl, Java, and Linux/Unix Administration

Richard Howlett

unread,
Sep 14, 1999, 3:00:00 AM9/14/99
to
Aaron Baugher wrote:
>
> I've been asked to do some administration on a remote
> system. It has a modem that's been used for dialing out,
> but it's not set to answer. I'm looking for a
> quick-and-easy way to switch it to auto-answer; something I
> can lead someone through over the phone. Once I get into
> the system I can make it permanent. Any way to do this in a
> command line or two?

Try this:

(stty $stty_attributes_including_especally_the_bit_rate
printf 'ATS0=1\r' >/dev/tty1A
exec sed '/^OK$/q') </dev/tty1A

I saved this from a posting on another newsgroup and thought you may find it
useful. I have to say I haven't tried it myself but the poster was well
known for his scripting expertise.

HTH
--
Richard Howlett

mailto:ric...@rhowlett.demon.co.uk


Tom Parsons

unread,
Sep 14, 1999, 3:00:00 AM9/14/99
to
Aaron Baugher enscribed:

| I've been asked to do some administration on a remote
| system. It has a modem that's been used for dialing out,
| but it's not set to answer. I'm looking for a
| quick-and-easy way to switch it to auto-answer; something I
| can lead someone through over the phone. Once I get into
| the system I can make it permanent. Any way to do this in a
| command line or two?

Can we assume you have an OpenServer or 3.2v4.2 based system?

If it is a MultiTech modem, you can change the configuration remotely
or, talk someone through adding S0=1 to the initialization string
in the atdialer script.
--
==========================================================================
Tom Parsons t...@tegan.com Sysop, SCOForum-CompuServe
==========================================================================

Aaron Baugher

unread,
Sep 14, 1999, 3:00:00 AM9/14/99
to
Tom Parsons <c...@tegan.com> writes:

> Can we assume you have an OpenServer or 3.2v4.2 based
> system?

It's OpenServer 5.0.5.

> If it is a MultiTech modem, you can change the
> configuration remotely or, talk someone through adding
> S0=1 to the initialization string in the atdialer script.

Does the atdialer script get run on bootup, or would they
need to dial out once before the new setting would take
effect?

Tom Parsons

unread,
Sep 15, 1999, 3:00:00 AM9/15/99
to
Aaron Baugher enscribed:

| Tom Parsons <c...@tegan.com> writes:
|
| > Can we assume you have an OpenServer or 3.2v4.2 based
| > system?
|
| It's OpenServer 5.0.5.
|
| > If it is a MultiTech modem, you can change the
| > configuration remotely or, talk someone through adding
| > S0=1 to the initialization string in the atdialer script.
|
| Does the atdialer script get run on bootup, or would they
| need to dial out once before the new setting would take
| effect?

If the modem is properly configured, ie., the first entry in
/usr/lib/uucp/Devices for that port references the correct atdialer,
the atdialer will be run >every< time the port is enabled or reset.
When the system boots, the first getty will run the script, when users
call in and disconnect, the new getty will run it again.

--tom

0 new messages