Page 81 - Asterisk™: The Future of Telephony

Zaptel
You may also run into errors when compiling Zaptel. Here are some of the most com-
monly occurring problems, and what to do about them. If your error is not listed below,
see the previous section as your error may be covered there.

make: cc: Command not found
You will receive the following error if you attempt to build Zaptel without the gcc
compiler installed:

make: cc: Command not found
make: *** [gendigits.o] Error 127
Be sure to install gcc and its dependencies. For more information, see “configure: error:
no acceptable C compiler found in $PATH in the previous section.

FATAL: Module wctdm/fxs/fxo not found
The TDM400P cards require the PCI bus to be version 2.2. If you attempt to load the
Zapata telephony drivers with an older version, you may get the following errors:
• When attempting to load the wctdm driver, you may see this error:

FATAL: Module wctdm not found
• When attempting to load the wctdm or wcfxo driver, you may see an error such as
this:
ZT_CHANCONFIG failed on channel 1: No such device or address (6)
FATAL: Module wctdm not found
The only way to resolve these errors is to use a newer motherboard that supports PCI
version 2.2:

You may also encounter these errors if the power has not been attached
to the Molex connector found on the TDM400P card.

Unresolved symbol link when loading ztdummy
The ztdummy driver requires that a UHCI USB controller be available on Linux 2.4
kernels (the USB controller is not a requirement on Linux 2.6 kernels, because they are
capable of generating the 1 kHz timing reference). There exists a secondary kind of
controller, known as OHCI, which is not compatible with the ztdummy driver. If the
UHCI USB controller is not accessible on Linux 2.4 kernels, the following error will
occur:
/lib/modules/2.4.22/misc/ztdummy.o: /lib/modules/2.4.22/misc/ztdummy.o: unresolved
symbol unlink_td
/lib/modules/2.4.22/misc/ztdummy.o: /lib/modules/2.4.22/misc/ztdummy.o: unresolved

Common Compiling Issues | 53