[asterisk-bugs] [JIRA] (ASTERISK-25674) Mixmonitor stop recording after atxfer
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Thu Jan 14 07:25:33 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton closed ASTERISK-25674.
-----------------------------------
Resolution: Not A Bug
{quote}
I can make a test on this way, but starting the MixMonitor on the called channel will just "move the problem a bit farther", without solving the general user problem of "I want to record this call... whatever it happens". I will make some tests, but what happens if it will be the called party to make an attended transfer?
A wants all his calls recorded
A calls B (the call is recorded because the MixMonitor is attached to B)
B make an attended transfer to C (call is not recorded and that can be right because that will be a "private" talk between B and C)
B transfer the call from A to C
A and C talks (but I think the call will not be recorded)
{quote}
MixMonitor is following a channel, not following a call. "calls" in Asterisk are quite ambiguous. In the case you describe - if you want MixMonitor to follow both channels then you should call MixMonitor on both channels.
Going beyond that you are asking for a new feature. I'm also not sure it would make sense to have MixMonitor by default follow the channel and all bridged/connected channels. I could imagine that getting out of hand quickly in some situations.
{quote}
Maybe the AUDIOHOOK_INHERIT was not so bad?
{quote}
As far as I can tell the behavior is the same as with AUDIOHOOK_INHERIT, you simply don't have to call the function now.
I'm closing this out as Not a Bug since it appears to be operating by design. We try to avoid discussing new features in depth on the tracker when we don't have a patch. It makes more sense on the mailing list so that others can join the conversation. Feel free to bring the issue up on the asterisk-dev mailing list if you want to suggest and discuss changes or propose a patch.
> Mixmonitor stop recording after atxfer
> --------------------------------------
>
> Key: ASTERISK-25674
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25674
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_mixmonitor
> Affects Versions: 13.6.0
> Environment: Asterisk 13.6 compiled from source on CentOS 6.7 64 bit. I have also tried asterisk 13.7.0-rc2 finding the same problem
> Reporter: Leandro Dardini
> Assignee: Unassigned
> Severity: Minor
>
> This seems the same bug affecting asterisk few years ago and that got fixed in asterisk 11. I tested asterisk 11.20 and the bug is not present. In short, when recording is active on a call, making an attended transfer will continue to record (in a different file, but that is correct) the "short talk", but does not record the transferred call. Let me picture better the case, if not enough clear.
> Extension 104 dials number 555-12345, recording is active and the call is recorded correctly.
> Extension 104 puts the call on hold and dials extension 105, recording is active and the call is recorded correctly.
> Extension 104 transfer the 555-12345 call leg to 105. Recording is NOT active and the call is NOT recorded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list