<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Georgia","serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>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 1.8.9.0 it's a good time to revisit since I did not receive any responses last time.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XSBUMJHD65R5A">https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XSBUMJHD65R5A</a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On Mon, Nov 7, 2011 at 9:30 AM, Luke Hamburg <<a href="mailto:luke@solvent-llc.com">luke@solvent-llc.com</a>> wrote:<o:p></o:p></p><p class=MsoPlainText>> Hi all-<o:p></o:p></p><p class=MsoPlainText>> So I posted this some months back to asterisk-users but I was told <o:p></o:p></p><p class=MsoPlainText>> that bounties need to be sent to the -dev list. I believe this to be <o:p></o:p></p><p class=MsoPlainText>> a fairly common issue and I am now bumping my original offer up to <o:p></o:p></p><p class=MsoPlainText>> $250. I'm trying to get the overall bounty up to the $500 mark with <o:p></o:p></p><p class=MsoPlainText>> help (hopefully) from a handful of others who I know have been affected<o:p></o:p></p><p class=MsoPlainText>> by this issue.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Since my original post I've updated my test system to Asterisk <o:p></o:p></p><p class=MsoPlainText>> 1.8.8-rc2 + DAHDI 2.5.0.2 and fwiw, no change in regards to the bug. <o:p></o:p></p><p class=MsoPlainText>> Here's the (updated) repost:<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> I’ve had an issue for over a year affecting MOH + DAHDI timers, I <o:p></o:p></p><p class=MsoPlainText>> reported it at:<o:p></o:p></p><p class=MsoPlainText>> <a href="https://issues.asterisk.org/jira/browse/ASTERISK-17474">https://issues.asterisk.org/jira/browse/ASTERISK-17474</a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Basically the MOH channel goes dead after a 'moh reload' command is <o:p></o:p></p><p class=MsoPlainText>> issued (these are streaming sources that use mpg123) and will not <o:p></o:p></p><p class=MsoPlainText>> start back up unless you do a full asterisk stop/start. The issue <o:p></o:p></p><p class=MsoPlainText>> hasn't caught anyone's attention yet. So I thought I'd try to put <o:p></o:p></p><p class=MsoPlainText>> together a bounty to spark some interest in fixing this issue. Is <o:p></o:p></p><p class=MsoPlainText>> anyone else interested in putting up something to get this bug fixed? <o:p></o:p></p><p class=MsoPlainText>> I'd be willing to put up $250 myself.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> thanks,<o:p></o:p></p><p class=MsoPlainText>> Luke<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Georgia","serif"'><o:p> </o:p></span></p></div></body></html>