Changes

{{Note box|Please note that FreePBX is a GUI and Asterisk is the telephony engine. The asterisk engine can load modules that perform specific tasks. One of these (set of) modules is DAHDI. DAHDI is required if you want to connect your Asterisk PBX to e.g. POTS or ISDN for local physical breakout. But DAHDI is absolutely '''NOT''' required if you only use SIP/IAX2 trunks via a trunk provider for breakout to the telephony network (SS7). So all DADHI issues may not be valid for a lot of users who do not need DAHDI, and FreePBX and Asterisk work perfectly without DAHDI, if you only need SIP/IAX2 trunks. Even if you do need to break out locally, ATA's or routers with POTS lines come in handy and you don't need DAHDI either, thus keeping your SME Serevr stable and without any hassle. Therefore I would like to see the FreePBX contrib evolve to a more basic contrib, where DAHDI can be 'activated' after initial install and as a seperate procedure. -HF}}  

{{Note box|Please note that FreePBX is a GUI and Asterisk is the telephony engine. The asterisk engine can load modules that perform specific tasks. One of these (set of) modules is DAHDI. DAHDI is required if you want to connect your Asterisk PBX to e.g. POTS or ISDN for local physical breakout. But DAHDI is absolutely '''NOT''' required if you only use SIP/IAX2 trunks via a trunk provider for breakout to the telephony network (SS7). So all DADHI issues may not be valid for a lot of users who do not need DAHDI, and FreePBX and Asterisk work perfectly without DAHDI, if you only need SIP/IAX2 trunks. Even if you do need to break out locally, ATA's or routers with POTS lines come in handy and you don't need DAHDI either, thus keeping your SME Server stable and without any hassle. Therefore I would like to see the FreePBX contrib evolve to a more basic contrib, where DAHDI can be 'activated' after initial install and as a seperate procedure. -HF}}