Summary:ASTERISK-16833: res_musiconhold does not compile
Reporter:Bruce McAlister (asgaroth)Labels:
Date Opened:2010-10-19 07:18:45Date Closed:2011-06-07 14:00:23
Versions:Frequency of
Description:the music on hold module does not build. It looks like it is skipped during build time.

****** STEPS TO REPRODUCE ******

[1] ./configure --prefix=/opt/asterisk
[2] make menuselect
[3] make
[4] make install
[5] make samples


When starting asterisk, asterisk complains with the following messages

[Oct 19 11:47:07] WARNING[15455]: loader.c:387 load_dynamic_module: Error loading module 'res_musiconhold.so': ld.so.1: asterisk: fatal: /opt/asterisk/lib/asterisk/modules/res_musiconhold.so: open failed: No such file or directory

Looking in the directory, it appears that res_musiconhold.so is not installed.

Looking at the source directory, there does not appear to be a res_musiconhold.so file accompanying the res_musiconhold.c file.

It therefore appears to me that res_musiconhold.so is not being built.

I dont see any errors during the build process, so I can only assume that it has been accidentally missed during build time.
Comments:By: Stefan Schmidt (schmidts) 2010-10-19 09:35:34

i have tried this an i see musiconhold compiled:
[CC] res_musiconhold.c -> res_musiconhold.o
  [LD] res_musiconhold.o -> res_musiconhold.so
could you please take a look at your menuselect (make menuselect) under the Resource Modules if res_musiconhold has a XXX.


By: Bruce McAlister (asgaroth) 2010-10-19 09:46:26

Ahh yes. you are correct. When looking in menuselect it appears that res_musiconhold depends on dahdi.

Is that correct?

As I'm running on Solaris, as far as I am aware, I will be unable to build dahdi as a timing source.

Is there any other way to enable res_musiconhold without the need for dahdi?

By: Bruce McAlister (asgaroth) 2010-10-19 17:31:47

is this in any way related to bug id 17726?

By: Paul Belanger (pabelanger) 2010-10-19 18:27:56

Yes, this is correct DAHDI is required for res_musiconhold.

Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support