|
 
|
zaptel 到dahdi 注意事项
大家zaptel 和 dahdi 可能模糊，看看这个解释就明白了。
链接http://www.sfr-fresh.com/unix/mi ... Zaptel-to-DAHDI.txt
1 =========================================================
2 === Information for upgrading from Zaptel to DAHDI ===
3 =========================================================
4
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
8 telephony purposes.
9
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.
14
15 First, the modules that directly use services from Zaptel/DAHDI have been
16 renamed; the new names are:
17
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
22 codec_zap.so -> codec_dahdi.so
23
24 However, in spite of the file name changes, the channels and
25 applications provided by these modules can still be used with 'Zap'
26 style names; see below for more information.
27
28 Second, there are have been a number of efforts made to ensure that
29 existing systems will not have to have any major configuration changes
30 made solely because Asterisk was built against DAHDI instead of
31 Zaptel. This includes:
32
33 chan_dahdi.so:
34
35 This module will determine which channel name ('Zap' or 'DAHDI')
36 should be used for incoming and outgoing channels based on the
37 build-time choice of telephony drivers. However, if you wish to
38 continue using the 'Zap' channel name even though you built Asterisk
39 against the DAHDI drivers, you can add the following line to the
40 [options] section of your /etc/asterisk/asterisk.conf file:
41
42 dahdichanname = no
43
44 All CLI commands that begin with 'zap' are now available as 'dahdi'
45 commands as well; the 'zap' variants will report that they are
46 deprecated the first time you use each one in an Asterisk instance,
47 but they will otherwise operate just as they did in previous versions.
48
49 All Asterisk Manager Interface (AMI) actions that begin with 'Zap'
50 are also available with 'DAHDI' prefixes.
51
52 The ZapSendKeypadFacility dialplan application is now available as
53 DAHDISendKeypadFacility as well; the Zap variant will report a deprecation
54 warning but will otherwise operate as it did it in previous
55 versions.
56
57 The configuration for the channel driver will be read from
58 /etc/asterisk/chan_dahdi.conf unless 'dahdichanname' has been set to
59 'no' in asterisk.conf; if that is done, then the configuration will
60 be read from /etc/asterisk/zapata.conf, just as it was in previous
61 versions.
62
63 app_dahdibarge.so:
64
65 The ZapBarge application is now available as DAHDIBarge as well; the
66 ZapBarge variant will report a deprecation warning when used, but
67 will otherwise operate as it did in previous versions. Regardless of
68 which application name is used, the application will restrict itself
69 to channels of the proper type, based on the 'dahdichanname' setting
70 in asterisk.conf.
71
72 app_dahdiras.so:
73
74 The ZapRAS application is now available as DAHDIRAS as well; the
75 ZapRAS variant will report a deprecation warning when used, but will
76 otherwise operate as it did in previous versions. Regardless of
77 which application name is used, the application will restrict itself
78 to channels of the proper type, based on the 'dahdichanname' setting
79 in asterisk.conf.
80
81 app_dahdiscan.so:
82
83 The ZapScan application is now available as DAHDIScan as well; the
84 ZapScan variant will report a deprecation warning when used, but will
85 otherwise operate as it did in previous versions. Regardless of
86 which application name is used, the application will restrict itself
87 to channels of the proper type, based on the 'dahdichanname' setting
88 in asterisk.conf.
89
90 app_flash.so:
91
92 This application has not had any name changes, but will report its
93 usage (via 'show application flash') as being for either DAHDI or
94 Zaptel channels based on the 'dahdichanname' setting in
95 asterisk.conf.
96
97 app_chanspy.so:
98
99 This application will transparently create 'DAHDI' or 'Zap' channels
100 as needed, based on the 'dahdichanname' setting in asterisk.conf.
101
102 app_meetme.so:
103
104 This application will transparently create 'DAHDI' or 'Zap' channels
105 as needed, based on the 'dahdichanname' setting in asterisk.conf. |
|
asterisk/sangoma, pri, ss7, 呼叫中心 |
|
