[asterisk-dev] MixMonitor Bug - $1500(USD) Bounty

[Geoffrey Mina]

I understand where you are coming from.  To test beyond what I have
already done would require more time than I have right now.  Hence the
bounty.

If anyone thinks they could tackle this, but need more money, please
contact me off-list.

Thanks.

On 3/24/10, Klaus Darilion <klaus.mailinglists at pernau.at> wrote:
>
>
> Am 23.03.2010 17:08, schrieb Geoffrey Mina:
>> I haven't tried calling Answer() after MixMonitor... I also haven't
>> tried using the straight Monitor() to see what the different legs are
>> doing.  Either way, it's a bit inconsequential... since I am offering to
>> pay someone to fix it :)
>
> Ususally it is easier to fix if you know where/what to fix. My
> suggestions are just some tests to narrow down the bug.
>
> regards
> klaus
>
>
>
>> thanks.
>>
>> On Tue, Mar 23, 2010 at 11:09 AM, Klaus Darilion
>> <klaus.mailinglists at pernau.at <mailto:klaus.mailinglists at pernau.at>>
>> wrote:
>>
>>     Just a few comments ...
>>
>>     Does it make a difference if you Answer the call after MixMonitor?
>>
>>     Have you tried Monitor() instead of MixMonitor and check each leg
>>     separately?
>>
>>     btw: what does monitor if a channel uses VAD and thus there are no
>>     frames sent for some time? Will it record silence or will it just
>>     write each frame after the previous one (thus skipping the silence)?
>>
>>     klaus
>>
>>     Am 23.03.2010 14:47, schrieb Geoffrey Mina:
>>
>>         I am offering a $1500(USD) bounty for anyone willing to fix the
>>         following bug in the 1.4 branch of app_mixmonitor.
>>
>>         https://issues.asterisk.org/view.php?id=17078
>>
>>         It seems like it should be relatively simple... so hopefully
>>         this should
>>         be easy money for someone.
>>
>>         I would need a patch for both 1.4.30 and 1.4.26.
>>
>>         thanks.
>>
>>
>>
>

-- 
Sent from my mobile device