David fire wrote: > First zaptel is dahdi now.... > second it isnot in /etc/dahdi or /etc/asterisk.... > i know because i remember one time a guy from digium toldme where to put > it.... >
Hopefully you are now using DAHDI so I'll just comment about DAHDI loads the drivers. When you run "make config" in the dahdi-tools projects, a couple of different files are loaded that control the loading of modules. /etc/modprobe.d/dahdi.blacklist is used to instruct udev to *not* automatically load the drivers when the system is booting. All the DAHDI drivers that support hardware devices are listed there in order to eliminate race conditions when the register their spans with the core dahdi driver. Even though the wctc4xxp does not register a span, it is there to remain consistent. /etc/init.d/dahdi is the script that should be configured to run on boot to load your drivers and configure your spans. This script reads /etc/dahdi/modules to determine which drivers it should load (by default, all the drivers are loaded). So you will want to make sure that wctc4xxp is in /etc/dahdi/modules, and then run /etc/init.d/dahdi start to load the driver. Cheers, Shaun _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users