|author||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-07-11 16:08:03 +0000|
|committer||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-07-11 16:08:03 +0000|
new installations should be using DAHDI instead of Zaptel, so the sample config file is now chan_dahdi.conf instead of zapata.conf
also, convert remaining references to zapata.conf in various places git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@130042 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
3 files changed, 7 insertions, 7 deletions
diff --git a/doc/ael.txt b/doc/ael.txt
index f72f2805b..7c7829ae9 100644
@@ -48,7 +48,7 @@ as well as the Expression syntax, and the Variable syntax.
Asterisk acts as a server. Devices involved in telephony, like Zapata
cards, or Voip phones, all indicate some context that should be
activated in their behalf. See the config file formats for IAX, SIP,
-zapata.conf, etc. They all help describe a device, and they all
+chan_dahdi.conf, etc. They all help describe a device, and they all
specify a context to activate when somebody picks up a phone, or a
call comes in from the phone company, or a voip phone, etc.
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 43173b1b4..39e906101 100644
@@ -18,7 +18,7 @@ Asterisk configuration files are defined as follows:
label = value
label2 = value
-In some files, (e.g. mgcp.conf, zapata.conf and agents.conf), the syntax
+In some files, (e.g. mgcp.conf, chan_dahdi.conf and agents.conf), the syntax
is a bit different. In these files the syntax is as follows:
diff --git a/doc/sla.tex b/doc/sla.tex
index c1159ce43..5aefdd61e 100644
@@ -23,7 +23,7 @@ IP channels.
An SLA system is built up of virtual trunks and stations mapped to real
Asterisk devices. The configuration for all of this is done in three
different files: extensions.conf, sla.conf, and the channel specific
-configuration file such as sip.conf or zapata.conf.
+configuration file such as sip.conf or chan_dahdi.conf.
@@ -55,7 +55,7 @@ Please refer to the examples section for full dialplan samples for SLA.
An SLA trunk is a mapping between a virtual trunk and a real Asterisk device.
This device may be an analog FXO line, or something like a SIP trunk. A trunk
must be configured in two places. First, configure the device itself in the
-channel specific configuration file such as zapata.conf or sip.conf. Once the
+channel specific configuration file such as chan_dahdi.conf or sip.conf. Once the
trunk is configured, then map it to an SLA trunk in sla.conf.
@@ -66,7 +66,7 @@ device=Zap/1
Be sure to configure the trunk's context to be the same one that is set for the
"autocontext" option in sla.conf if automatic dialplan configuration is used.
-This would be done in the regular device entry in zapata.conf, sip.conf, etc.
+This would be done in the regular device entry in chan_dahdi.conf, sip.conf, etc.
Note that the automatic dialplan generation creates the SLATrunk() extension
at extension 's'. This is perfect for Zap channels that are FXO trunks, for
example. However, it may not be good enough for an IP trunk, since the call
@@ -195,7 +195,7 @@ device=SIP/station3
With this configuration, the dialplan is generated automatically. The first
zap channel should have its context set to "line1" and the second should be
-set to "line2" in zapata.conf. In sip.conf, station1, station2, and station3
+set to "line2" in chan_dahdi.conf. In sip.conf, station1, station2, and station3
should all have their context set to "sla\_stations".
For reference, here is the automatically generated dialplan for this situation:
@@ -238,7 +238,7 @@ For this example, assume that there are 2 trunks and 3 stations. The trunks
are Zap/1 and Zap/2. The stations are SIP/station1, SIP/station2, and
-In zapata.conf, channel 1 has context=line1 and channel 2 has context=line2.
+In chan_dahdi.conf, channel 1 has context=line1 and channel 2 has context=line2.
In sip.conf, all three stations are configured with context=sla\_stations.