[asterisk-bugs] [JIRA] (ASTERISK-22695) ARI: Add the ability to monitor a channel

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-22695.
----------------------------------

    Resolution: Duplicate

Whoops - duplicate of ASTERISK-22781
                
> ARI: Add the ability to monitor a channel
> -----------------------------------------
>
>                 Key: ASTERISK-22695
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22695
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_ari
>    Affects Versions: 12.0.0-beta1
>            Reporter: Matt Jordan
>
> Currently, bridges and channels can both be recorded.
> When a channel is recorded, all media from the channel is directed into the recording, i.e., they are essentially in "app_record". In general, you can't do much else with the channel while it is performing the recording. The use case for this kind of recording is really for applications like VoiceMail.
> When a bridge is recorded, all participants are recorded. This is really more of a monitoring of the bridge - participants can leave/join and the bridge will still happily record them all. This is useful when want you want to record is the action that occurs between multiple participants - such as in a Queue or a Conference - and the only thing you want recorded is when they are all talking to each other.
> What is missing is monitoring of a channel. For example, you may want to record all the audio of a caller to a Queue, regardless of how they are moved between various bridges. In that case, the recording needs to be tied to the channel - that is, Monitor or MixMonitor.
> (We don't need to differentiate here however; MixMonitor should be the general approach taken as opposed to Monitor)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira