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: http://svn.digium.com/svn/asterisk/trunk@122234 f38db490-d61c-443f-a65b-d21fe96a405b

1 files changed, 5 insertions, 5 deletions

diff --git a/configs/sla.conf.sample b/configs/sla.conf.sample
index 75acc2bc4..3ae9dffac 100644
--- a/configs/sla.conf.sample
+++ b/configs/sla.conf.sample
@@ -21,15 +21,15 @@
 
 ;type=trunk                 ; This line is what marks this entry as a trunk.
 
-;device=Zap/3               ; Map this trunk declaration to a specific device.
+;device=DAHDI/3               ; Map this trunk declaration to a specific device.
                             ; NOTE: You can not just put any type of channel here.
-                            ;       Zap channels can be directly used.  IP trunks
+                            ;       DAHDI channels can be directly used.  IP trunks
                             ;       require some indirect configuration which is
                             ;       described in doc/asterisk.pdf.
 
 ;autocontext=line1          ; This supports automatic generation of the dialplan entries 
                             ; if the autocontext option is used.  Each trunk should have 
-                            ; a unique context name.  Then, in zapata.conf, this device 
+                            ; a unique context name.  Then, in dahdi.conf, this device 
                             ; should be configured to have incoming calls go to this context.
 
 ;ringtimeout=30             ; Set how long to allow this trunk to ring on an inbound call before hanging 
@@ -49,12 +49,12 @@
 
 ;[line2]
 ;type=trunk
-;device=Zap/4
+;device=DAHDI/4
 ;autocontext=line2
 
 ;[line3]
 ;type=trunk
-;device=Zap/3
+;device=DAHDI/3
 ;autocontext=line3
 
 ;[line4]