[asterisk-bugs] [JIRA] (ASTERISK-20719) Monitor recordings change filename unexpectedly after a blind transfer, but not attended transfer

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-20719:
-----------------------------------

    Affects Version/s: 13.18.4

> Monitor recordings change filename unexpectedly after a blind transfer, but not attended transfer
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20719
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20719
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_monitor
>    Affects Versions: 1.8.16.0, 13.18.4
>         Environment: Debian 686
>            Reporter: Grzesiek
>         Attachments: extensions.conf, extensions.txt, sip.conf, xfer.txt
>
>
> Monitor when executed with b option on channel transfered call changes the filenames if transfered channel was monitored at the moment of bridging.
> Here is how it looks:
> A calls ----> B(let's assume ${UNIQUEUEID}=1)
> exten => _XXXX,1,NoOp
> seme => n,Set(MONITOR_FILENAME=call-${UNIQUEID})
> same => n,monitor(alaw,/var/spool/asterisk/monitor/${MONITOR_FILENAME},bm)
> When B answers the call, files call-1-in* and call1-out* are created. During The call, B tries to make attended transfer A is put on hold and B calls C using the same dialplan logic:
> B calls ----> C(let's assume ${UNIQUEUEID}=2)
> At the time off invoking monitor application none off the call-2 channels are monitored so the monitor application starts without errors, if B waits till C answers, everything is OK monitor starts recording and files call-2-in* and call-2-out* are created, When B transfers the call call-2 monitor is stopped. And call-2 files contain only the call between B and C.
> But there is problem when B does not wait until C answers the call, if transfer is done before C answers the call, the call-2* are not created and the call is still recorded to the call-1* files, but when the transferred call between A and C ends, the call-1* files get renamed to call-2* and the MONITOR_EXEC application is called with call-2* file names as parameters.
> This makes it impossible to locate the call record since the file names get changed, and there is no other way than figuring put file names from messages log.



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