From 47ea5a01b46f7cf62dd472a767668d738fb39894 Mon Sep 17 00:00:00 2001 From: "Kevin P. Fleming" Date: Wed, 13 Aug 2008 22:33:32 +0000 Subject: 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: https://origsvn.digium.com/svn/asterisk/trunk@137627 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- Zaptel-to-DAHDI.txt | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 Zaptel-to-DAHDI.txt (limited to 'Zaptel-to-DAHDI.txt') diff --git a/Zaptel-to-DAHDI.txt b/Zaptel-to-DAHDI.txt new file mode 100644 index 000000000..f0cf2f676 --- /dev/null +++ b/Zaptel-to-DAHDI.txt @@ -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 +telephony purposes. + +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. + +chan_dahdi.so: + + 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' + commands. + + All Asterisk Manager Interface (AMI) actions that began with 'Zap' + have changed to 'DAHDI' prefixes. + + The ZapSendKeypadFacility dialplan application has been renamed to + DAHDISendKeypadFacility. + + The configuration for the channel driver will be read from + /etc/asterisk/chan_dahdi.conf instead of /etc/asterisk/zapata.conf. + +app_dahdibarge.so: + + The ZapBarge application has been renamed to DAHDIBarge. + +app_dahdiras.so: + + The ZapRAS application has been renamed to DAHDIRAS. + +app_dahdiscan.so: + + The ZapScan application has been renamed to DAHDIScan. -- cgit v1.2.3