summaryrefslogtreecommitdiff
path: root/doc/tex/hardware.tex
diff options
context:
space:
mode:
authorJeff Peeler <jpeeler@digium.com>2008-06-12 17:27:55 +0000
committerJeff Peeler <jpeeler@digium.com>2008-06-12 17:27:55 +0000
commitef3b21472889eff8e88f7e83afb2251ef54722ce (patch)
tree4732aea57767a39cd0efe083ba0119911ee976a3 /doc/tex/hardware.tex
parent6ac8ccaba45c9c11fefe853d0c83a92e881c2abf (diff)
Goodbye Zaptel, hello DAHDI. Removes Zaptel driver support with DAHDI. Configuration file and dialplan backwards compatability has been put in place where appropiate. Release announcement to follow.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@122234 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'doc/tex/hardware.tex')
-rw-r--r--doc/tex/hardware.tex10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/tex/hardware.tex b/doc/tex/hardware.tex
index 30fa587aa..a678167de 100644
--- a/doc/tex/hardware.tex
+++ b/doc/tex/hardware.tex
@@ -4,12 +4,12 @@ A PBX is only really useful if you can get calls into it. Of course, you
can use Asterisk with VoIP calls (SIP, H.323, IAX, etc.), but you can also
talk to the real PSTN through various cards.
-Supported Hardware is divided into two general groups: Zaptel devices and
-non-zaptel devices. The Zaptel compatible hardware supports pseudo-TDM
-conferencing and all call features through chan\_zap, whereas non-zaptel
+Supported Hardware is divided into two general groups: DAHDI devices and
+non-DAHDI devices. The DAHDI compatible hardware supports pseudo-TDM
+conferencing and all call features through chan\_dahdi, whereas non-DAHDI
compatible hardware may have different features.
-\subsection{Zaptel compatible hardware}
+\subsection{DAHDI compatible hardware}
\begin{itemize}
\item Digium, Inc. (Primary Developer of Asterisk)
@@ -37,7 +37,7 @@ compatible hardware may have different features.
\end{itemize}
\end{itemize}
-\subsection{Non-zaptel compatible hardware}
+\subsection{Non-DAHDI compatible hardware}
\begin{itemize}
\item QuickNet, Inc.