1 =========================================================
2 === Information for upgrading from Zaptel to DAHDI ===
3 =========================================================
5 As announced in early 2008, Digium is renaming the Zaptel telephony
6 interface project to DAHDI (Digium Asterisk Hardware Device Interface)
7 to accommodate the desires of the owner of the Zaptel trademark for
10 This version of Asterisk can be built using either Zaptel or DAHDI,
11 and has many changes to make the use of DAHDI as easy as possible for
12 existing users with dialplans, CDR parsers, AMI applications, and
13 others that expect Zaptel to be in use.
15 First, the modules that directly use services from Zaptel/DAHDI have been
16 renamed; the new names are:
18 chan_zap.so -> chan_dahdi.so
19 app_zapbarge.so -> app_dahdibarge.so
20 app_zapras.so -> app_dahdiras.so
21 app_zapscan.so -> app_dahdiscan.so
23 However, in spite of the file name changes, the channels and
24 applications provided by these modules can still be used with 'Zap'
25 style names; see below for more information.
27 Second, there are have been a number of efforts made to ensure that
28 existing systems will not have to have any major configuration changes
29 made solely because Asterisk was built against DAHDI instead of
30 Zaptel. This includes:
34 This module will determine which channel name ('Zap' or 'DAHDI')
35 should be used for incoming and outgoing channels based on the
36 build-time choice of telephony drivers. However, if you wish to
37 continue using the 'Zap' channel name even though you built Asterisk
38 against the DAHDI drivers, you can add the following line to the
39 [options] section of your /etc/asterisk/asterisk.conf file:
43 All CLI commands that begin with 'zap' are now available as 'dahdi'
44 commands as well; the 'zap' variants will report that they are
45 deprecated the first time you use each one in an Asterisk instance,
46 but they will otherwise operate just as they did in previous versions.
48 All Asterisk Manager Interface (AMI) actions that begin with 'Zap'
49 are also available with 'DAHDI' prefixes.
51 The ZapSendKeypadFacility dialplan application is now available as
52 DAHDISendKeypadFacility as well; the Zap variant will report a deprecation
53 warning but will otherwise operate as it did it in previous
56 The configuration for the channel driver will be read from
57 /etc/asterisk/chan_dahdi.conf unless 'dahdichanname' has been set to
58 'no' in asterisk.conf; if that is done, then the configuration will
59 be read from /etc/asterisk/zapata.conf, just as it was in previous
64 The ZapBarge application is now available as DAHDIBarge as well; the
65 ZapBarge variant will report a deprecation warning when used, but
66 will otherwise operate as it did in previous versions. Regardless of
67 which application name is used, the application will restrict itself
68 to channels of the proper type, based on the 'dahdichanname' setting
73 The ZapRAS application is now available as DAHDIRAS as well; the
74 ZapRAS variant will report a deprecation warning when used, but will
75 otherwise operate as it did in previous versions. Regardless of
76 which application name is used, the application will restrict itself
77 to channels of the proper type, based on the 'dahdichanname' setting
82 The ZapScan application is now available as DAHDIScan as well; the
83 ZapScan variant will report a deprecation warning when used, but will
84 otherwise operate as it did in previous versions. Regardless of
85 which application name is used, the application will restrict itself
86 to channels of the proper type, based on the 'dahdichanname' setting
91 This application has not had any name changes, but will report its
92 usage (via 'show application flash') as being for either DAHDI or
93 Zaptel channels based on the 'dahdichanname' setting in
98 This application will transparently create 'DAHDI' or 'Zap' channels
99 as needed, based on the 'dahdichanname' setting in asterisk.conf.
103 This application will transparently create 'DAHDI' or 'Zap' channels
104 as needed, based on the 'dahdichanname' setting in asterisk.conf.