| Summary: | ASTERISK-22695: ARI: Add the ability to monitor a channel | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2013-10-14 12:51:05 | Date Closed: | 2013-10-28 14:06:39 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_ari |
| Versions: | 12.0.0-beta1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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) | ||
| Comments: | By: Matt Jordan (mjordan) 2013-10-28 14:06:39.144-0500 Whoops - duplicate of ASTERISK-22781 | ||