it can… Asterisk in some cases needs a timing source. Zaptel provides it.
Try installing zaptel, then recompile/reinstall *… see if that helps…
I have not been successful in using MOH without zaptel installed. I don’t know that it is required, but it fails to work without it for me.
Likewise, I didn’t realise that Zaptel was required even if you don’t have any line cards installed. That book does mention this but not until way down in the section on installing Zaptel. I only read the first sentence and assumed I could skip the rest as I wouldn’t be needing it.
I have a problem, however, trying to make the damn thing.
I have unpacked the tar ball into /usr/src/zaptel-1.2.7 and am trying to “make all” on it. I keep getting the message “You do not appear to have the sources for the 2.6.9-34.EL kernel installed” even though I think I have (or rather, my linux guru who’s been helping me thinks it is).
Any clues?
Also…
I’ve been trying to follow the “How to compile ztdummy” over at:
voip-info.org/wiki-Asterisk+timer+ztdummy
On stage 4 it says “Edit the Makefile and remove the ‘#’ in front of ztdummy in the top”. Well, there’s no “ztdummy” at the top and if I remove the ‘#’ before “ztdummy” way down the makefile then it throws an error.
Edit:
Okay, I’m getting somewhere. I found this useful page that explains about a bug in spinlock.h
voip-info.org/wiki/view/Aste … CentOS+4.x
I’ve corrected that and have “made” Zaptel but I’m still having problems loading it at the moment (FATAL: Module Zaptel not found).
on a redhat style OS, I have found this usually works well
yum update (gets you latest stuff)
yum install kernel-devel (gets you kernel sources)
(edit spinlock file)
zaptel folder:
make clean
make
make install
make config (adds init scripts so zaptel starts on boot. thsi works from * source too)
service zaptel start (loads zaptel)
then do asterisk, from asterisk source folder:
make clean
make
make install
make config
(insure that zaptel is running)
service asterisk start
asterisk -r (you should have a console)
hope that helps!
Sorry for going quiet on you guys - I’ve been up to my eyes in CAT5e and we went live last weekend. Bit of a nervous moment on Monday morning when the calls started rolling in but it all held together - most of the time.
Consequently, my attention to Music-on-Hold was, well, put on hold!
I’ve come back to it now because I need to create a public address connection via the sound card and I’ve an inclination that I’ll need Zaptel to implement this. I intend to follow the details over here:
voip-info.org/wiki/view/Sett … sound+card
Many thanks, IH, for those simple clear instructions but I haven’t followed them yet. This is because I’ve noticed that I have a directory /usr/src/asterisk that has the same contents as /usr/src/asterisk-1.2.10. There is another called /usr/src/zaptel-1.2.7 but there isn’t one called /usr/src/zaptel. Do I need it?
not really.
if you’ve played around with * for a bit, /usr/src/asterisk might have been created if you checked out the TRUNK code from SVN (or HEAD from CVS way back in the day), as no version is attached to those. If you are using a release version, you would get a asterisk-version.tar.gz file, which unpacks into a /usr/src/asterisk-ver type directory.
You can probably delete whichever ones you are not using. If you are not sure, move them all somewhere (ie make a /usr/src/oldstuff), download fresh asterisk/zaptel source tarballs, untar, and compile/install as per above.
Also, after updating the kernel, I’ve had to reboot to get on the latest kernel version. I’ve found that zaptel is trying to work with the latest version, but I’m still running the older version. Usually a reboot between updating the kernel and compiling zaptel gets things in sync.
Since the system is now live, I’m only fiddling with it at weekends when the office is closed. Eventually, I’ll have a backup server that I can play with but that will require yet more time than I have available at the moment.
I followed IronHelix’s instructions. The ‘yum update’ took some time since I booted off the CentOS ServerCD which is only version 4.3. Anyway, that appeared to complete okay and the ‘yum install kernel-devel’ was not required as I already had the kernel sources.
The spinlock.h file no longer needs editing as the bug has been corrected.
In the Zaptel folder I edited the Makefile to take out the ‘#’ before ‘ztdummy’ in the ‘MODULES:=’ directive. Although, from the warnings about duplicate definitions thrown up by the following 'make’s I think this is not required as I’m running Linux version 2.6.
Then I did ‘make clean’, ‘make’, ‘make install’, ‘make config’ and ‘service zaptel start’. This throws out a fatal error:
“Loading zaptel framework: FATAL: Module zaptel not found.
waiting for zap to come online… Error: missing /dev/zap!”
And indeed, there is nothing in my /dev folder called zap. I’ve even rebooted but I still get the same error during the boot process.
EDIT:
I went back and put in the ‘#’ in the Makefile and now it seems to work okay!
EDIT AGAIN:
Zaptel seems to be up now. It even detects that there is no zaptel hardware and loads ztdummy. However, I still don’t hear any music on hold. The log reports the following if I dial the MoH extension:
[quote] – Executing MusicOnHold(“SIP/10-095fac30”, “default”) in new stack
– Started music on hold, class ‘default’, on channel ‘SIP/10-095fac30’
– Stopped music on hold on SIP/10-095fac30
== Spawn extension (office, 88, 1) exited non-zero on ‘SIP/10-095fac30’
[/quote]
The ‘Stopped music’ message comes up almost straight after the ‘Started music’ message. It’s much the same if I put a real call on hold. I’ve tried ‘musiconhold=default’ in zapata.conf but this has no effect.
try installing (if you dont already have it) the asterisk-addons package, and then set the type to ‘files’…
Sorry for not replying sooner… been busy.
Just to let you know that MoH now works. There seems to be little info anywhere on how to install the addons so I just tried make clean; make; make install. There were plenty of complaints about not having mySQL but after a reboot it seems to be okay.
Now there’s one more Asterisk system up and running.
Thanks to all and especially IronHelix.