[asterisk-bugs] [JIRA] (ASTERISK-21094) MixMonitorMute mutes through stream if already slinear (e.g. Originate)

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235019#comment-235019 ] 

Friendly Automation commented on ASTERISK-21094:
------------------------------------------------

Change 4865 merged by zuul:
audiohooks:  Muting a hook can mute underlying frames

[https://gerrit.asterisk.org/4865|https://gerrit.asterisk.org/4865]

> MixMonitorMute mutes through stream if already slinear (e.g. Originate)
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-21094
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21094
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_mixmonitor
>    Affects Versions: 1.8.20.1
>         Environment: CentOS 5.3.  VMWare.
>            Reporter: David Woolley
>            Severity: Minor
>         Attachments: ASTERISK-21094-Patch-1.8-1.txt
>
>
> We backported MixMonitorMute to 1.6.1 and found a problem that, according to my code reading still exists in the 1.8 branch SVN version, namely that, if the codec is already slinear, using MixMonitorMute causes the orignal media stream to be silenced, as well as the monitored stream.
> We are using MixMonitor on queues.  If the incoming call on the queue arrives from a normal channel (in our case a local channel instantiated from a normal channel), MixMonitorMute works correctly, and replaces the audio on the recording by an equivalent period of silence.
> If the call on the queue is initiated by AMI Originate (again via a local channel), the through media in both directions is also replaced by equivalent silence.  For the avoidance of doubt, these are frames containing silence, not the absence of frames.
> MixMonitorMute is applied in both directions.



--
This message was sent by Atlassian JIRA
(v6.2#6252)