|author||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-08-13 22:34:25 +0000|
|committer||kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>||2008-08-13 22:34:25 +0000|
Merged revisions 137627 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk ................ r137627 | kpfleming | 2008-08-13 17:33:32 -0500 (Wed, 13 Aug 2008) | 9 lines Merged revisions 137530 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r137530 | kpfleming | 2008-08-13 15:46:19 -0500 (Wed, 13 Aug 2008) | 1 line add document describing what users will need to be aware of when upgrading to this version and using DAHDI ........ ................ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@137631 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'Zaptel-to-DAHDI.txt')
1 files changed, 52 insertions, 0 deletions
diff --git a/Zaptel-to-DAHDI.txt b/Zaptel-to-DAHDI.txt
new file mode 100644
@@ -0,0 +1,52 @@
+=== Information for upgrading from Zaptel to DAHDI ===
+As announced in early 2008, Digium is renaming the Zaptel telephony
+interface project to DAHDI (Digium Asterisk Hardware Device Interface)
+to accommodate the desires of the owner of the Zaptel trademark for
+This version of Asterisk can only be built using DAHDI, and as a
+result there are number of changes that will be visible to previous
+users of Asterisk with Zaptel.
+First, the modules that directly use services from DAHDI have been
+renamed; the new names are:
+ chan_zap.so -> chan_dahdi.so
+ app_zapbarge.so -> app_dahdibarge.so
+ app_zapras.so -> app_dahdiras.so
+ app_zapscan.so -> app_dahdiscan.so
+Second, the behavior of many modules has changed due to the switch to
+DAHDI; the changes are listed below.
+ Incoming and outgoing channels managed by this module will be
+ 'DAHDI' channels instead of 'Zap' channels.
+ All CLI commands that began with 'zap' have been renamed to 'dahdi'
+ All Asterisk Manager Interface (AMI) actions that began with 'Zap'
+ have changed to 'DAHDI' prefixes.
+ The ZapSendKeypadFacility dialplan application has been renamed to
+ The configuration for the channel driver will be read from
+ /etc/asterisk/chan_dahdi.conf instead of /etc/asterisk/zapata.conf.
+ The ZapBarge application has been renamed to DAHDIBarge.
+ The ZapRAS application has been renamed to DAHDIRAS.
+ The ZapScan application has been renamed to DAHDIScan.