In the other hand, when I start * with asterisk -vvvc it show me this lines
could be this the problem?
[res_musiconhold.so] => (Music On Hold Resource)
== Parsing ‘/etc/asterisk/musiconhold.conf’: Found
Sep 14 10:34:57 WARNING[10540]: res_musiconhold.c:565 moh_register
;37;40m: Unable to open pseudo channel for timing… Sound may be choppy.
Patience my friend someone will help soon, there is not a lot of people in the forum at this time. Trust me I’m having a similar problem and I have not been able to fix yet at least yours is not stopping, mine is and pulling the little hair I have. Now don’t worry someone will come to your recue soon.
I think we’re going to need a little bit more information to solve this problem. See if you can answer the following questions to help us out.
1.) Do you have mpg123 installed? Making sure that it is the exact version that is need. Also making sure that it is not really mpg321 in disguise.
2.) Do you have any Zaptel drivers installed? I think you need a timing source for it to work properly. This means you need to either have a hardware card and associated driver, or the ztdummy driver running.
or
In case you are interested, I’ll post a link to the method that I use for on hold music. I do not prefer to use the standard method with mpg123. It’s old, insecure, and wastes processor power on decocding mp3s.
I use the step that is under B. Use Rawplayer. Basically this method converts your MP3 on hold music files ahead of time and stores them as raw audio files. This is better cause you only decode them once. Then when asterisk needs the audio, you just dump the raw audio strait to asterisk. I’ve not had any problems with this method, and currently have it working on two machines.
Yes I have mpg123 installed a it is running ok by console … and de version in mpg123-0.59r.
I’m thinking that in this point is the problem, look at my modprobe below:
root@Intragrt:~#modprobe ztdummy
/lib/modules/2.4.29/kernel/drivers/usb/host/usb-uhci.o.gz: init_module: No such device
/lib/modules/2.4.29/kernel/drivers/usb/host/usb-uhci.o.gz: Hint: insmod errors can be caused by inc.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.29/kernel/drivers/usb/host/usb-uhci.o.gz: insmod /lib/modules/2.4.29/kernel/driverd
/lib/modules/2.4.29/kernel/drivers/usb/host/usb-uhci.o.gz: insmod ztdummy failed
Ok … I run my menuconfig to see my kernel configuration and I’m seeing that “Support for USB” is a MODULE, (it seem to me that it has to be “BUILT-IN”) and “UHCI (Intel PIIX4, VIA, …) support” is a module too (I think that this part is ok) …
To sum up … I think that ztdummy driver is not running, could be because “Support for USB” is compiled as a MODULE and not BUILT-IN???