Posted: Thu May 06, 2004 2:37 pm Post subject: [Asterisk-doc] docs installation.xml,1.3,1.4
Comments:
Update of /cvsroot/asterisk/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7535/docs
Modified Files:
installation.xml
Log Message:
blitzrage
- updated some of the installation requirements. Expanded some documentation
which already existed.
Index: installation.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/installation.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** installation.xml 13 Jan 2004 16:36:23 -0000 1.3
--- installation.xml 6 May 2004 14:37:45 -0000 1.4
***************
*** 33,37 ****
<title>Tested Linux Distributions</title>
<para>
! [RedHat/Fedora/Debian/Mandrake/Gentoo/etc.]
</para>
</sect3>
--- 33,40 ----
<title>Tested Linux Distributions</title>
<para>
! Asterisk works with most Linux distributions. Many distributions such as RedHat, Fedora,
! Debian, Mandrake and Gentoo have all been used successfully by the developers. If you find
! something doesn't work on any particular system, you may want to file a bug report. See the
! section regarding filing a bug report.
</para>
</sect3>
***************
*** 39,43 ****
<title>Minimal Kernel Version</title>
<para>
! [I'm guessing it's 2.4.x, but we should get more clarification]
</para>
</sect3>
--- 42,47 ----
<title>Minimal Kernel Version</title>
<para>
! Asterisk is designed to work on any Linux kernel 2.4. However there is some support for kernel
! 2.6. If you are trying to build a stable system, it is recommended that you use kernel version 2.4.
</para>
</sect3>
***************
*** 45,49 ****
<title>Required Packages</title>
<para>
! [OpenSSL and its development libraries, and libnewt for zttool]
</para>
</sect3>
--- 49,59 ----
<title>Required Packages</title>
<para>
! <!-- [OpenSSL and its development libraries, and libnewt for zttool] -->
! Previously there were some packages which were requirements to install Asterisk such as
! readline and readline-devel. Also there is no special hardware required such as a soundcard.
! The only required package is Asterisk itself. If you are using Digium hardware, you will need
! the zaptel package. For T1 and E1 interfaces the libpri package is required. Bison is required
! to compile Asterisk and the ncurses and ncurses-devel packages are required if you wish to build
! the newt tools (e.g. astman).
</para>
</sect3>
***************
*** 64,72 ****
<sect3>
<title>X100P and X101P</title>
! <para/>
</sect3>
<sect3>
<title>TDM400P</title>
! <para/>
</sect3>
<sect3>
--- 74,97 ----
<sect3>
<title>X100P and X101P</title>
! <para>
! The X100P and X101P are Foreign Exchange Office (FXO) devices which
! allow you to connect the Asterisk PBX to a PSTN line. The only difference
! between an X100P and X101P is a slight difference in chips, but makes no difference
! to it's operation. The X100P uses a single PCI slot and supports FXS
! Loopstart and "Kewlstart" (Loopstart with far end disconnection supervision).
! With the X100P Asterisk supports both incoming and outgoing calls and
! supports ring detection and remote hangup.
! </para>
</sect3>
<sect3>
<title>TDM400P</title>
! <para>
! The TDM400P is a half-length PCI 2.2 compliant card which allows you to connect
! standard analog telephones and analog lines to a computer. The card uses small
! modules to activate the 4 ports on the card allowing any port to act as either an
! FXO or FXS device. There is an alternate naming convention used when referencing
! the TDM400P. TDM##B where the first hash is the number of FXS (0-4) interfaces and the
! second hash is the number of FXO (0-4) interfaces.
! </para>
</sect3>
<sect3>
Posted: Thu May 06, 2004 2:51 pm Post subject: [Asterisk-doc] docs installation.xml,1.3,1.4
On Thu, 2004-05-06 at 09:37, blitzrage wrote:
Quote:
<sect3>
<title>TDM400P</title>
! <para>
! The TDM400P is a half-length PCI 2.2 compliant card which allows you to connect
! standard analog telephones and analog lines to a computer. The card uses small
! modules to activate the 4 ports on the card allowing any port to act as either an
! FXO or FXS device. There is an alternate naming convention used when referencing
! the TDM400P. TDM##B where the first hash is the number of FXS (0-4) interfaces and the
! second hash is the number of FXO (0-4) interfaces.
! </para>
</sect3>
I know this is a bit picking nits, but while the "port" on the back of
the card can be either FXO or FXS, it is the daughter card that controls
the interface. I feel it is important to ensure the new user understands
the daughter board isn't selectable between modes but rather different
boards do different things.
If I knew right off how to word it better I would jump on it, but I'm
finding it clumsy in my head at the moment.
--
Steven Critchfield <critch@basesys.com>
On Thu, 2004-05-06 at 09:37, blitzrage wrote:
> <sect3>
> <title>TDM400P</title>
> ! <para>
> ! The TDM400P is a half-length PCI 2.2
compliant
Quote:
card which allows you to connect
> ! standard analog telephones and analog lines
to a
Quote:
computer. The card uses small
> ! modules to activate the 4 ports on the card
allowing any port to act as either an
> ! FXO or FXS device. There is an alternate
naming
Quote:
convention used when referencing
> ! the TDM400P. TDM##B where the first hash is
the
Quote:
number of FXS (0-4) interfaces and the
> ! second hash is the number of FXO (0-4)
interfaces.
Quote:
> ! </para>
> </sect3>
I know this is a bit picking nits, but while the "port" on the back of
the card can be either FXO or FXS, it is the daughter card that controls
the interface. I feel it is important to ensure the new user understands
the daughter board isn't selectable between modes but rather different
boards do different things.
If I knew right off how to word it better I would jump on it, but I'm
finding it clumsy in my head at the moment.
The card uses small modules to activate the 4 ports on the card. Depending
on which daughter card is plugged onto the board will determine whether the
port acts as an FXO or FXS interface. The boards are not selectable between
modes; the module used determines the type of interface.
Posted: Thu May 06, 2004 6:08 pm Post subject: [Asterisk-doc] docs installation.xml,1.3,1.4
On Thu, 2004-05-06 at 12:55, Leif Madsen wrote:
Quote:
> I know this is a bit picking nits, but while the "port" on the back of
> the card can be either FXO or FXS, it is the daughter card that controls
> the interface. I feel it is important to ensure the new user understands
> the daughter board isn't selectable between modes but rather different
> boards do different things.
>
> If I knew right off how to word it better I would jump on it, but I'm
> finding it clumsy in my head at the moment.
The card uses small modules to activate the 4 ports on the card. Depending
on which daughter card is plugged onto the board will determine whether the
port acts as an FXO or FXS interface. The boards are not selectable between
modes; the module used determines the type of interface.
How's that?
Leif Madsen.
I think it is better.
--
Steven Critchfield <critch@basesys.com>
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum