|
|
6d6cf1 |
<sect1 id="server-usage-overview">
|
|
|
6d6cf1 |
|
|
|
6d6cf1 |
<title>Overview</title>
|
|
|
6d6cf1 |
|
|
|
6d6cf1 |
<para>
|
|
|
6d6cf1 |
The infrastructure described in this chapter uses the
|
|
|
6d6cf1 |
client/server model to provide a public mail service through
|
|
|
6d6cf1 |
the telephone line. In this configuration, we (the poeple
|
|
|
6d6cf1 |
building the infrastructure) provide the information you (the
|
|
|
6d6cf1 |
person using the infrastructure) need to know in order to
|
|
|
db8245 |
establish a dial-up connection from the client computer to the
|
|
|
db8245 |
server computer through the telephone line.
|
|
|
6d6cf1 |
</para>
|
|
|
6d6cf1 |
|
|
|
6d6cf1 |
<para>
|
|
|
6d6cf1 |
The infrastructure described in this chapter is made available
|
|
|
6d6cf1 |
to you free of charge, however, you should know that
|
|
|
6d6cf1 |
maintaining it costs both money and time. For example, for
|
|
|
6d6cf1 |
each hour the server computer is on production there is an
|
|
|
6d6cf1 |
electrical consume that need to be paid every month.
|
|
|
6d6cf1 |
Likewise, each call that you establish from the client
|
|
|
6d6cf1 |
computer to the server computer will cost you money, based on
|
|
|
6d6cf1 |
the location you made the call from and the time you spend
|
|
|
6d6cf1 |
connected.
|
|
|
6d6cf1 |
</para>
|
|
|
6d6cf1 |
|
|
|
6d6cf1 |
<para>
|
|
|
db8245 |
In this manual, by dial-up connection we mean the action of
|
|
|
db8245 |
dialing-up a server computer from a client computer through a
|
|
|
db8245 |
Modem attached to the telephone line. In this infrastructure,
|
|
|
db8245 |
dial-up connections are always established from the client
|
|
|
db8245 |
computer to the server computer and never the other way
|
|
|
db8245 |
around. The main purpose of a client computer to establish a
|
|
|
db8245 |
dial-up connection with the server computer will be using one
|
|
|
db8245 |
or more Internet services provided in the server computer.
|
|
|
db8245 |
</para>
|
|
|
db8245 |
|
|
|
db8245 |
<para>
|
|
|
db8245 |
In order for the server computer to answer telephone calls, it
|
|
|
db8245 |
is required to install a Modem device in it (see
|
|
|
b46cda |
linkend="server-install-modem" />). Once the Modem device has
|
|
|
b46cda |
been installed, you need to install and configure both
|
|
|
db8245 |
<application>mgetty</application> and
|
|
|
db8245 |
<application>pppd</application> programs. The
|
|
|
db8245 |
<application>mgetty</application> program must be run by
|
|
|
db8245 |
<systemitem class="daemon">init</systemitem> daemon in order
|
|
|
db8245 |
to take control over the Modem device. By default, inside
|
|
|
db8245 |
&TC;; (release 5.5), mgetty isn't configured to start with
|
|
|
db8245 |
<systemitem class="daemon">init</systemitem> daemon so you
|
|
|
db8245 |
need to do it yourself (see ...). Later, for attending
|
|
|
db8245 |
connection requests, you need to configure mgetty to use the
|
|
|
db8245 |
<application>pppd</application> program, so the Point-to-Point
|
|
|
db8245 |
Protocol (PPP) can be talked and IP packages can be
|
|
|
db8245 |
interchanged between the client computer and the server
|
|
|
db8245 |
computer. Later, you need to configure
|
|
|
db8245 |
<application>pppd</application> to adjust it to your needs
|
|
|
db8245 |
(see ...).
|
|
|
db8245 |
</para>
|
|
|
db8245 |
|
|
|
db8245 |
<para>
|
|
|
db8245 |
Once you've configured both <application>mgetty</application>
|
|
|
db8245 |
and <application>pppd</application> programs, the server
|
|
|
db8245 |
computer should be ready to attend incoming calls. The
|
|
|
db8245 |
remaining of this chapter describes the way incoming calls are
|
|
|
db8245 |
attended by the server computer once they have arrived to its
|
|
|
db8245 |
Modem device.
|
|
|
6d6cf1 |
</para>
|
|
|
6d6cf1 |
|
|
|
6d6cf1 |
</sect1>
|