diff options
| author | Jeff Peeler <jpeeler@digium.com> | 2008-06-12 17:27:55 +0000 |
|---|---|---|
| committer | Jeff Peeler <jpeeler@digium.com> | 2008-06-12 17:27:55 +0000 |
| commit | ef3b21472889eff8e88f7e83afb2251ef54722ce (patch) | |
| tree | 4732aea57767a39cd0efe083ba0119911ee976a3 /configs/sla.conf.sample | |
| parent | 6ac8ccaba45c9c11fefe853d0c83a92e881c2abf (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 'configs/sla.conf.sample')
| -rw-r--r-- | configs/sla.conf.sample | 10 |
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] |