Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: sonoracomm on January 14, 2007, 07:37:12 PM
-
I get errors such as this at the Asterisk console:
File call-cannot-complete does not exist in any format
I then installed the smeserver-asterisk-sounds-1.2.2-2.noarch.rpm which got rid of many of these error messages, but some remain (such as the one above).
Is there a newer smeserver-asterisk-sounds rpm? Is there a better way to deal with this?
I followed the Quickstart guide from the Selintra docs site to install 2.1.14-378. It doesn't mention smeserver-asterisk-sounds at all.
Thanks in advance,
G
-
I followed the Quickstart guide from the Selintra docs site to install 2.1.14-378. It doesn't mention smeserver-asterisk-sounds at all
Hi
Yes, you should install the sounds rpm. Apologies for the oversight in the docs. Here in England, we run our own UK sounds and throw the American prompts away.
Kind Regards
Selintra
-
Hi and thanks for the quick response...on Sunday, no less.
As I mentioned, I did install the sounds rpm from the Selintra FTP site, and it fixed some of the error messages about file not found. However, there are still some file not found errors, such as the one I mentioned.
Is there a newer sounds rpm? Or should I source a generic sounds rpm from somewhere else?
Thanks in advance,
G
-
Hi there
To be honest we don't pay much attention to the sound files so they may have been updated by Digium (we use our own). The call-cannot-complete.gsm file you refer to is present on our system but in the gb sound files which we get from a third party (installed with the uk sounds rpm). You might want to run a diff on the digium sounds tar files against ours if you have time. You can simply move any missing files over into the /var/lib/asterisk/sounds directory. If there are differences then let us know and we'll make a note to roll a new rpm when we have a few spare cycles. Alternatively, if any kind soul wants to lend a hand, the sounds rpm is dead easy to put together and the src rpm is up on ibiblio. Cooking up an updated version shouldn't take more than a couple of hours on a dark winter's eve. :-)
Kind Regards
Selintra
-
Hi Selintra,
What's a "dark winter's eve" :D Just kidding :wink: What do I need to have a look at the source rpm? I can't promise I'd be able to do anything usefull but I am always willing to try :D
Regards,
Del
-
Hi Del,
Modifying a simple rpm like asterisk-sounds isn't difficult, just time consuming. In your SME box under /usr/src/redhat you will find the rpm build libraries. They are called /BUILD /RPMS /SOURCES /SPECS & /SRPMS.
Do the following as /root... (not essential but is saves buggering about)
Copy the sounds .src.rpm into /SRPMS and then install it with
rpm -Uvh rpm-name
An rpm consists of two things - a tarball containing the files to be installed and a .spec file which allows a measure of control over how the install is done. After you've installed the /src rpm you will find the gripped tarball in /SOURCES. Use 'tar xzvf' to unzip it. What you end up with is a sparse linux file tree (beginning with /root) and containing the files to be installed (in their correct libraries). You will now have the job of comparing the actual files against the latest asterisk sounds and then updating your tree accordingly (download the tarball from digium and unpack it in /usr/src).
All asterisk sound files are in /var/lib/asterisk/sounds.
Once you're happy with your new source tree you can re-zip it with 'tar czvf' N.B. KEEP THE SAME NAME AS THE ORIGINAL .tar.gz.
To build your new rpm go to the /SPECS directory where you will find the .spec file for your sounds rpm (it was installed as part of the src rpm install).
Open it, find the release number (4th or 5th line) and increase it by 1.
save it back and then roll your new rpm with
rpmbuild -ba rpm-name.spec
As long as you get a zero return code (i.e. it worked ok), your new rpm will be saved into /RPMS/noarch and your new .src rpm will fetch up in /SRPMS.
Easy peasy.
:-)
Kind Regards
Selintra
-
Hey Selintra,
Proceeding to build the new rpm, I ran into an immediate snag. It appears that Digium has reorganized the folder structure of their sounds (from asterisk-core-sounds-en-gsm-1.4.5.tar.gz) and it is significantly different than the folder structure of the rpm.
How should I reconcile that? Just pick the missing sounds out and drop them in the root (/var/lib/asterisk/sounds) then zip it back up?
How should I pick out which sound files to pull from the Digium tarball?
So much for building my first rpm...
G
-
1.4 is somewhat different to 1.2. You might want to fetch the 1.2 tar.gz from digium or fetch the 1.2 sounds srpm from atrpms here
http://www.atrpms.net/dist/common/asterisk-sounds/
Kind Regards
Selintra
-
Well, I did what you suggested...
I found little difference between the smeserver-asterisk-sounds-1.2.2-2 and the asterisk 1.2 tarball. So I dug a bit deeper.
The one sound that I cannot find on my system, nor (readily) on the net, is call-cannot-complete.gsm (or any other format).
Jan 20 14:45:57 WARNING[2946] file.c: File call-cannot-complete does not exist in any format
I think the other errors went away after I installed smeserver-asterisk-sounds-1.2.2-2.
Thanks again,
G
-
Hi
I've done a bit more investigation on this. I think the sound-clip you refer to may be one that development had specially made by the recording studio but I won't be able to check 'till tomorow when I speak to them.
I'm pretty sure that they cleaned up call disconnection around about -330 and they may have commissioned this clip as a part of that exercise.
Kind Regards
Selintra
-
Yeah, I was right. Apologies to everyone. This clip is ours. I've asked dev to put a patch in to check if SAIL is running our UK language pack and, if not, to choose a phrase from the stock (US) * sound pack. They're moaning like hell because they say that if there had been something close enough they'd have used it in the first place.
Sheesh - developers. :roll:
Kind Regards
Selintra