Carlos Chavez wrote:> I am getting the following warnings on the CLI when loading Asterisk
> 1.6.1-rc1:
>
> [Feb 12 12:32:34] NOTICE[22261]: timing.c:59
> ast_install_timing_functions: Multiple timing modules are loaded. You
> should only load one.
>
> [Feb 12 12:32:34] ERROR[22261]: codec_dahdi.c:398 find_transcoders:
> Failed to open /dev/dahdi/transcode: No such file or directory
>
> [Feb 12 12:32:33] WARNING[22261]: chan_iax2.c:10939 build_user: Unable
> to support trunking on user 'telecomab' without DAHDI timing
> [Feb 12 12:32:33] WARNING[22261]: chan_iax2.c:10679 build_peer: Unable
> to support trunking on peer 'telecomab' without a timing interface
>
> I am using DAHDI 2.1.0.4, Asterisk 1.6.1-rc1 on a CentOS 5.2 machine
> with a TDM04 card. These are the modules:
>
> Module Size Used by
> dahdi_echocan_mg2 9608 0
> wctdm 39884 4
> dahdi 190728 2 dahdi_echocan_mg2,wctdm
>
> Where do I have to specify the timing module?
>
Timing may be provided from one of two sources in Asterisk 1.6.1:
res_timing_dahdi.so (get timing from DAHDI), and res_timing_pthread.so (use
pthread library for timing). There are a couple of ways to fix your problem,
assuming that the timing module you want to use is res_timing_dahdi.so.
1) Remove res_timing_pthread.so from /usr/lib/asterisk/modules and restart
Asterisk
2) In modules.conf, add noload => res_timing_pthread.so
3) While not a requirement, you can also make menuselect and disable
res_timing_pthread.so from being built at all. The module can be found under the
Resource Modules menu.
It looks as though the timing modules for 1.6.1 are not well-documented, and
Menuselect should be altered to not allow for both modules to be built.
We'll
get to work getting this documented better.
Mark Michelson