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

doc/tex/sla.tex

@@ -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 dahdi.conf.
 
 \subsection{Dialplan}
 
@@ -55,21 +55,21 @@ 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 dahdi.conf or sip.conf.  Once the
 trunk is configured, then map it to an SLA trunk in sla.conf.
 \begin{astlisting}
 \begin{verbatim}
 [line1]
 type=trunk
-device=Zap/1
+device=DAHDI/1
 \end{verbatim}
 \end{astlisting}
 
 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 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
+at extension 's'.  This is perfect for DAHDI channels that are FXO trunks, for
 example.  However, it may not be good enough for an IP trunk, since the call
 coming in over the trunk may specify an actual number.
 
@@ -173,12 +173,12 @@ sla.conf:
 \begin{verbatim}
 [line1]
 type=trunk
-device=Zap/1
+device=DAHDI/1
 autocontext=line1
 
 [line2]
 type=trunk
-device=Zap/2
+device=DAHDI/2
 autocontext=line2
 
 [station](!)
@@ -199,8 +199,8 @@ device=SIP/station3
 \end{astlisting}
 
 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
+DAHDI channel should have its context set to "line1" and the second should be
+set to "line2" in 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:
@@ -241,10 +241,10 @@ phone system.  The voicemail box number used in this example is 1234, which
 would be configured in voicemail.conf.
 
 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
+are DAHDI/1 and DAHDI/2.  The stations are SIP/station1, SIP/station2, and
 SIP/station3.
 
-In zapata.conf, channel 1 has context=line1 and channel 2 has context=line2.
+In 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.
 
@@ -297,12 +297,12 @@ exten => s,2,Macro(slaline,line2)
 
 [line1_outbound]
 exten => disa,1,Disa(no-password,line1_outbound)
-exten => _1NXXNXXXXXX,1,Dial(Zap/1/${EXTEN})
+exten => _1NXXNXXXXXX,1,Dial(DAHDI/1/${EXTEN})
 exten => 8500,1,VoicemailMain(1234)
 
 [line2_outbound]
 exten => disa,1,Disa(no-password|line2_outbound)
-exten => _1NXXNXXXXXX,1,Dial(Zap/2/${EXTEN})
+exten => _1NXXNXXXXXX,1,Dial(DAHDI/2/${EXTEN})
 exten => 8500,1,VoicemailMain(1234)
 
 [sla_stations]