mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-10-31 02:37:10 +00:00 
			
		
		
		
	https://origsvn.digium.com/svn/asterisk/trunk ................ r137680 | kpfleming | 2008-08-13 21:03:47 -0500 (Wed, 13 Aug 2008) | 9 lines Merged revisions 137679 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r137679 | kpfleming | 2008-08-13 21:03:04 -0500 (Wed, 13 Aug 2008) | 1 line forgot one module name that changed ........ ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.0@137681 65c4cc65-6c06-0410-ace0-fbb531ad65f3
		
			
				
	
	
		
			54 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			54 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| =========================================================
 | |
| === 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
 | |
|   codec_zap.so -> codec_dahdi.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.
 |