Kevin Bockman wrote:
If you are using 1.2, I would use native (codec, not MP3). There
should be an example in the sample config file in
/usr/src/asterisk/configs/musiconhold.conf.sample - I don't see it on
the Wiki. It should be there, somewhere. Must be buried. For this
option, you
Robert La Ferla wrote:
Chris Albertson wrote:
Second even if there were one the mpg123 process is not long lived. A
new one is started for each
MOH session.
I hate to say it but there is a problem where the mpg123 process never
terminates. This occurs with the latest
we had the same problem, so we switched it to madplay (do a search in
the wiki)
and that issue stopped.
Best Regards
Greg Cirino
[EMAIL PROTECTED] Virus Spam Free
and you can't do better than that!
http://www.cirellemail.com
Cirelle Enterprises Inc.
25 Indian Rock Rd #421
Windham NH,
Kevin Bockman wrote:
If you are using 1.2, I would use native (codec, not MP3). There
should be an example in the sample config file in
/usr/src/asterisk/configs/musiconhold.conf.sample - I don't see it on
the Wiki. It should be there, somewhere. Must be buried. For this
option, you will
Robert La Ferla wrote:
How can you convert mp3 to gsm? mencoder? Do you have an example?
Once again, documented on the wiki :-)
sox is your friend; it can convert between pretty much all available
codecs, except G.729 and G.723.1.
___
On Tue, Jan 10, 2006 at 01:16:51PM +0100, Matt Riddell (IT) wrote:
I tried to get my wife to killall mpg123 processes from the console, but
the machine was probably in the Asterisk console rather than the command
line.
!killall mpg123
should work from the asterisk CLI
--
Tzafrir Cohen
When I configured this server, I did not do the make mpg123 option.
Months later, I read about it and did it, as the client was asking about
MOH. About a week later the server crashed, which it never has before. I
believe mpg123 have a memory leak.
What's the best way to remove it, and is
Chris Mason (Lists) wrote:
When I configured this server, I did not do the make mpg123 option.
Months later, I read about it and did it, as the client was asking about
MOH. About a week later the server crashed, which it never has before. I
believe mpg123 have a memory leak.
What's the best
Almost certainly a memory leak in mpg123 is not the cause of a system
crash. First off, there is no such leak. Second even if there were
one
the mpg123 process is not long lived. A new one is started for each
MOH session.
If mpg123 is causing the crash then it may be due simply because of
all
Chris Albertson wrote:
Second even if there were one the mpg123 process is not long lived. A new one
is started for each
MOH session.
I hate to say it but there is a problem where the mpg123 process never
terminates. This occurs with the latest SVN-branch-1.2-r7917 version
and has been
That's been happenning since 1.2 - if the parent * process dies the
mp123 process doesn't go with it like it should and will just eat your
processor right up, if you're using 1.2, I'd definitely suggest using
native moh.
Robert La Ferla wrote:
Chris Albertson wrote:
Second even if there
Almost certainly a memory leak in mpg123 is not the cause of a system
crash. First off, there is no such leak. Second even if there were
one the mpg123 process is not long lived. A new one is started for
each MOH session.
If mpg123 is causing the crash then it may be due simply because
12 matches
Mail list logo
