Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
jamiemurray wrote:The one you list here as duplicate look as though they are two different phone calls from the same number.
Let's break it down:
1933_20220930-091933_3333333333_193302_10101-all.wav > 20220930-091933 So this call was at 09:19:33 on Sept 30th 2022.
1933_20220930-144934_3333333333_193302_10101-all.wav > 20220930-144934 And this one was at 14:49:34 also on Sept 30th 2022.
jamiemurray wrote:If you have recording activated elsewhere (Ingroup / Agent / Campaign), turn it off in the DID entry and see if you still get the duplicates.
jamiemurray wrote:What about the CLI as the call enters all the way through to agent delivery? does it show two MixMonitor lines? if so, look at the stage in the dialplan the recordings both start, that may give you an indication of what's initiating each recording.
Ikram_Ali wrote:Just to clarify more on this issue.
I just made a test call on a toll-free from source number 2224447778 and there is duplicate recordings.
# LEAD DATE/TIME SECONDS RECID FILENAME LOCATION TSR
1 566277 2023-03-31 04:29:09 8 716458 2176_20230331-032908_2224447778_110001_13096 http://22.22.22.22/RECOR... 13096
2 566277 2023-03-31 04:29:08 9 716457 2176_20230331-042908_2224447778_110001_13096 http://22.22.22.22/RECOR... 13096
Asterisk CLI logs below.
-- Executing [58600051@default:1] MeetMe("Local/58600051@default-000438fa;2", "8600051,Fmq") in new stack
> Channel Local/58600051@default-000438fa;1 was answered.
-- Executing [8309@default:1] Answer("Local/58600051@default-000438fa;1", "") in new stack
-- Executing [8309@default:2] Monitor("Local/58600051@default-000438fa;1", "wav,2176_20230331-032908_2224447778_110001_13096") in new stack
-- Executing [8309@default:3] Wait("Local/58600051@default-000438fa;1", "7260") in new stack
-- Executing [58600051@default:1] MeetMe("Local/58600051@default-000438f8;2", "8600051,Fmq") in new stack
> Channel Local/58600051@default-000438f8;1 was answered.
-- Executing [8309@default:1] Answer("Local/58600051@default-000438f8;1", "") in new stack
-- Executing [8309@default:2] Monitor("Local/58600051@default-000438f8;1", "wav,2176_20230331-042908_2224447778_110001_13096") in new stack
-- Executing [8309@default:3] Wait("Local/58600051@default-000438f8;1", "7260") in new stack
== Manager 'sendcron' logged on from 127.0.0.1
jamiemurray wrote:Set AGI Output to BOTH on the server, repeat the test and post the output of screenlog.0 during your call to see if this helps identify exactly where the two recordings are being triggered from.
jamiemurray wrote:The agi debug cli output is not enough, there's more debugging info in the screenlog.0 file in /var/log/astguiclient/ when AGI Out is set to BOTH on the server entry (Admin > Servers)
jamiemurray wrote:You may have to restart the server for the screen log to begin.
I still get the feeling you have recording enabled in two places.
Check the recording value of each of the following:
- User
- Campaign
- Ingroup
- DID
If you want all calls to be recorded but only are interested in the agent conversation, set the recording to ALLCALLS or ALLFORCE on the campaign but turn it off on everything else. (Be careful of override options, check the help next to the field in each case)
Users browsing this forum: No registered users and 91 guests