|author||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-07-11 22:12:26 +0000|
|committer||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-07-11 22:12:26 +0000|
a whole pile of Zaptel/DAHDI compatibility work, with lots more to come... this tree is not yet ready for users to be easily upgrading or switching, but it needs to be :-)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@130298 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/hardware.txt b/doc/hardware.txt
index 01f8f7f06..9e4e96e91 100644
@@ -2,12 +2,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), 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.
-Zaptel compatible hardware
+DAHDI compatible hardware
-- Digium (Primary author of Asterisk)
@@ -31,7 +31,7 @@ Zaptel compatible hardware
* Wildcard TE410P - Quad T1/E1 switchable interface. Supports PRI and
RBS signalling, as well as PPP, FR, and HDLC data modes.
-Non-zaptel compatible hardware
+Non-DAHDI compatible hardware
-- QuickNet, Inc.