UpgradingfromZapteltoDAHDI

RevisionHistory Revision 0.1 0.2 0.3 Date December12,2008 December15,2008 January6,2009 By GlennJenkins BillSavage BillSavage Notes FinalDraft Review FinalDraft

UpgradingfromZapteltoDAHDI
Asannouncedinearly2008,DigiumhasrenamedtheZapteltelephonyinterfacetoDAHDIin ordertoaccommodatethedesiresoftheowneroftheZapteltrademarkfortelephony purposes.TheDigiumAsteriskHardwareDeviceInterface(DAHDI)isacollectionofdriversand utilitiesforconnectingyourAsteriskinstallationtothePublicSwitchedTelephoneNetwork (PSTN).dahdilinuxisthepackagethatcontainstheLinuxkernelmodedrivers,whiledahdi toolscontaintheusermodescriptsandutilitiesforworkingwithdahdilinux. DAHDIissupportedbyAsteriskversions1.4.22andgreateraswellasAsteriskversions1.6.0 andgreater.DAHDI2.1.0isthecurrentreleaseoftheDAHDILinuxkernelmodulespackage, whichreplacesthekernelmodulesfromZaptel.Theprimarypurposeofthe2.0.0releasewas torenamethepackagefromZaptel.Theprimarypurposeofthe2.1.0releasewasto incorporatesupportforBRI.Ashortlistofbugfixesaswellasnewfeaturesisprovidedbelow:

Echocancellerscannowbeappliedperchannelandselectedatconfigurationtime. Channelmemoryallocationchangedfromonelargeblockintosmallerblocksinorderto reduceoutofmemoryerrorsonasystemthathasbeenrunningforsometime. Layoutchangestosupportbinarypackaging. NeonMWIsupportaddedtothewctdm24xxpdriver. DroppedsupportforLinuxKernel2.4aswellasthetorisaandwcusbdrivers. Native driver for the B410P four port BRI module

ImportantGeneralUpgradeNotes
Zaptel1.2willcontinuetobereleasedinnewversionsasbugsarefoundandfixed. Asterisk1.2willbeunaffectedbythesechanges. NowthatDAHDI2.0.0hasbeenreleasedtherewillbenomorereleasesofZaptel1.4. Asterisk1.4willcontinuetohavesupportforZaptel,althoughitwillbeenhancedtoalso transparentlysupportDAHDIinstead,andthedocumentation(anddefaultconfiguration files)willencouragenewuserstouseDAHDIinsteadofZaptel. Asterisk1.4releaseslaterthan1.4.21,andallreleasesofAsterisk1.6,willautomaticallyuse DAHDIinpreferencetoZaptel,evenifZaptelisstillinstalledonthesystem. Asterisk1.6.0willuseDAHDIexclusively(itwillnothavesupportforZaptel),althoughthis willbedoneinahighlybackwardscompatiblewaysothatdisruptiontoexistingdialplans andconfigurationswillbeminimized.

DAHDI2.1.0
TheZaptelpackage,whichincludedbothkernelmodulesanduserspacetoolsforconfiguring andmanagingthemodules,hasbeensplitintotwopackages: Thelistofpackagesreleasedincludes: dahdilinux2.1.0:kernelmodules dahditools2.1.0:userspacetools o Thedahdilinuxanddahditoolspackageshave*separate*versionnumbers;they willnotbereleased'insync',anditisperfectlyacceptabletouse(forexample) dahditools2.0.6withdahdilinux2.0.11. dahdilinuxcomplete2.1.0+2.1.0 o Thedahdilinuxcompletepackageversionnumberwillalwaysinclude*both*of theseversionnumberssothatyouwillknowwhatisincludedinit.

BothdahdilinuxanddahditoolsarerequiredtoenableDAHDIsupportinyoursystem.Youwill needtoinstalldahdilinuxfirstandthendahditools,andfinallyyoucanconfigureandmake Asterisk.dahdilinuxcompleteisbothdahdilinuxanddahditoolscombinedintoonedownload asaconvenience.YoustillneedlibpriforPRIsupportwithAsteriskifyouareusingDAHDI. DAHDIissupportedinbothAsterisk1.4.22andAsterisk1.6.0.

NotesabouttheDAHDILINUXPackage
Theprimarykernelmoduleshavechangednames;thenewnamesare: zaptel.ko>dahdi.ko ztdeth.ko>dahdi_dynamic_eth.ko ztdloc.ko>dahdi_dynamic_loc.ko ztdummy.ko>dahdi_dummy.ko ztdynamic.ko>dahdi_dynamic.ko zttranscode.ko>dahdi_transcode.ko

Thekernelmodulesforcarddrivershave*not*changednames,althoughthewcusbandtorisa driversarenolongerincluded. Thispackagenolongerincludesthe'menuselect'utilityforchoosingwhichmodulestobuild;all modulesthatcanbebuiltarebuiltautomatically. Itisnolongerpossibletoselectasoftwareechocancelleratcompiletimetobuildinto dahdi.ko.Allfourincludedechocancellers(MG2,KB1,SECandSEC2)arebuiltasloadable modules,andiftheDigiumHPECbinaryobjectfilehasbeenplacedintotheproperdirectory theHPECmodulewillbebuiltaswell.Anyorallofthesemodulescanbeloadedatthesame time,andtheechocancellertobeusedonthesystem'schannelscanbeconfiguredusingthe dahdi_cfgtoolfromthedahditoolspackage. Note:Itismandatorytoconfigureanechocancellerforthesystem'schannelsusing dahdi_cfgunlesstheinterfacecardsinusehaveechocancellermodulesavailableand enabled.ThereisnodefaultsoftwareechocancellerwithDAHDI.

NotesabouttheDAHDIToolsPackage
Manytoolnameshavechanged:
ztcfg>dahdi_cfg ztmonitor>dahdi_monitor ztscan>dahdi_scan ztspeed>dahdi_speed zttest>dahdi_test zttool>dahdi_tool zapconf>dahdi_genconf(deprecatesgenzaptelconf)

Thesystemconfigurationfilehasmovedfrom/etc/zaptel.confto/etc/dahdi/system.conf. Thedahdi_cfgtoolcannowbeusedtoselectanechocancelleronachannelbychannelbasis inthesystemconfigurationfile.Seethesystem.confsampleforexamplesofhowtodothis.

Asterisk1.4DAHDINotes
ThisversionofAsteriskcanbebuiltusingeitherZaptelorDAHDI,andhasmanychangesto maketheuseofDAHDIaseasyaspossibleforexistinguserswithdialplans,CDRparsers,AMI applications,andothersthatexpectZapteltobeinuse. First,themodulesthatdirectlyuseservicesfromZaptel/DAHDIhavebeenrenamed;thenew namesare: 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 However,inspiteofthefilenamechanges,thechannelsandapplicationsprovidedbythese modulescanstillbeusedwith'Zap'stylenames;seebelowformoreinformation. Second,therehavebeenanumberofeffortsmadetoensurethatexistingsystemswillnot requireanymajorconfigurationchangessolelybecauseAsteriskwasbuiltagainstDAHDI insteadofZaptel.Thisincludes: chan_dahdi.so: Thismodulewilldeterminewhichchannelname('Zap'or'DAHDI')shouldbeusedforincoming andoutgoingchannelsbasedonthebuildtimechoiceoftelephonydrivers.However,ifyou wishtocontinueusingthe'Zap'channelnameeventhoughyoubuiltAsteriskagainstthe DAHDIdrivers,youcanaddthefollowinglinetothe[options]sectionofyour /etc/asterisk/asterisk.conffile.

dahdichanname=no AllCLIcommandsthatbeginwith'zap'arenowavailableas'dahdi'commands.The'zap' variantswillreportthattheyaredeprecatedthefirsttimeyouuseeachoneinan Asteriskinstance.Theywillotherwiseoperatejustastheydidinpreviousversions. AllAsteriskManagerInterface(AMI)actionsthatbeginwith'Zap'arealsoavailablewith 'DAHDI'prefixes.

TheZapSendKeypadFacilitydialplanapplicationisnowavailableas DAHDISendKeypadFacility.TheZapvariantwillreportadeprecationwarningbutwill otherwiseoperateasitdiditinpreviousversions. Theconfigurationforthechanneldriverwillbereadfrom/etc/asterisk/chan_dahdi.conf unless'dahdichanname'hasbeensetto'no'inasterisk.conf.Ifthatisdone,thenthe configurationwillbereadfrom/etc/asterisk/zapata.conf,justasitwasinprevious versions.

app_dahdibarge.so TheZapBargeapplicationisnowavailableasDAHDIBarge.TheZapBargevariantwillreporta deprecationwarningwhenused,butwillotherwiseoperateasitdidinpreviousversions. Regardlessofwhichapplicationnameisused,theapplicationwillrestrictitselftochannelsof thepropertype,basedonthe'dahdichanname'settinginasterisk.conf. app_dahdiras.so The ZapRAS application is now available as DAHDIRAS. The ZapRAS variant will report a deprecation warning when used, but will otherwise operate as it did in previous versions. Regardless of which application name is used, the application will restrict itself to channels of the proper type, based on the 'dahdichanname' setting in asterisk.conf. app_dahdiscan.so TheZapScanapplicationisnowavailableasDAHDIScan.TheZapScanvariantwillreporta deprecationwarningwhenused,butwillotherwiseoperateasitdidinpreviousversions. Regardlessofwhichapplicationnameisused,theapplicationwillrestrictitselftochannelsof thepropertype,basedonthe'dahdichanname'settinginasterisk.conf. app_flash.so Thisapplicationhasnothadanynamechanges,butwillreportitsusage(via'showapplication flash')asbeingforeitherDAHDIorZaptelchannelsbasedonthe'dahdichanname'settingin asterisk.conf. app_chanspy.so Thisapplicationwilltransparentlycreate'DAHDI'or'Zap'channelsasneeded,basedonthe 'dahdichanname'settinginasterisk.conf.

app_meetme.so Thisapplicationwilltransparentlycreate'DAHDI'or'Zap'channelsasneeded,basedonthe 'dahdichanname'settinginasterisk.conf.

Asterisk1.6toDAHDINotes
ThisversionofAsteriskcanonlybebuiltusingDAHDI,andasaresulttherearenumberof changesthatwillbevisibletoprevioususersofAsteriskwithZaptel. First,themodulesthatdirectlyuseservicesfromDAHDIhavebeenrenamed;thenewnames 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,thebehaviorofmanymoduleshaschangedduetotheswitchtoDAHDI.Thechanges arelistedbelow. chan_dahdi.so: Incomingandoutgoingchannelsmanagedbythismodulewillbe'DAHDI'channels insteadof'Zap'channels. AllCLIcommandsthatbeganwith'zap'havebeenrenamedtodahdicommands. AllAsteriskManagerInterface(AMI)actionsthatbeganwith'Zap'havechangedto 'DAHDI'prefixes. TheZapSendKeypadFacilitydialplanapplicationhasbeenrenamedto DAHDISendKeypadFacility. Theconfigurationforthechanneldriverwillbereadfrom/etc/asterisk/chan_dahdi.conf insteadof/etc/asterisk/zapata.conf.

app_dahdibarge.so: TheZapBargeapplicationhasbeenrenamedtoDAHDIBarge. app_dahdiras.so: TheZapRASapplicationhasbeenrenamedtoDAHDIRAS. app_dahdiscan.so: TheZapScanapplicationhasbeenrenamedtoDAHDIScan.