[asterisk-dev] bounty for ASTERISK-17474 streaming MusicOnHold bug
luke at solvent-llc.com
Wed Dec 28 07:43:08 CST 2011
It's been a couple of months now and as some will note, Michael L. Young
(elguero) has generously contributed his time & effort to roll a patch for
this long-standing issue. The patches have been uploaded for 1.8 and 10.0
(see ASTERISK-17474) and I've personally tested the 1.8 patch on a couple of
systems and they are working well. I did offer $250 of my own cheddar for
this but I requested some additional support from the community and now that
the patch has been shipped and will be rolled into 126.96.36.199 it's a good time
to revisit since I did not receive any responses last time.
Would anyone else be kind enough to donate any additional amount towards
this patch? I am sure that the patch is of benefit to a number of you, and
any amount is appreciated! I've created a PayPal donation box to accept
donations for this cause and will pass 100% of funds over to Michael Young.
The link is:
On Mon, Nov 7, 2011 at 9:30 AM, Luke Hamburg <luke at solvent-llc.com> wrote:
> Hi all-
> So I posted this some months back to asterisk-users but I was told
> that bounties need to be sent to the -dev list. I believe this to be
> a fairly common issue and I am now bumping my original offer up to
> $250. I'm trying to get the overall bounty up to the $500 mark with
> help (hopefully) from a handful of others who I know have been affected
> by this issue.
> Since my original post I've updated my test system to Asterisk
> 1.8.8-rc2 + DAHDI 188.8.131.52 and fwiw, no change in regards to the bug.
> Here's the (updated) repost:
> I've had an issue for over a year affecting MOH + DAHDI timers, I
> reported it at:
> Basically the MOH channel goes dead after a 'moh reload' command is
> issued (these are streaming sources that use mpg123) and will not
> start back up unless you do a full asterisk stop/start. The issue
> hasn't caught anyone's attention yet. So I thought I'd try to put
> together a bounty to spark some interest in fixing this issue. Is
> anyone else interested in putting up something to get this bug fixed?
> I'd be willing to put up $250 myself.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev