Recordings for this lead problem

[jessiekidfernando]

Hello Everyone,

We've been receiving complaints that our recordings are overlapping. For example, different recording ID having different seconds but when we listen, these are both identical recordings. Also why the seconds doesnt match the actual duration of each recordings.

RECORDINGS FOR THIS LEAD:
# LEAD DATE/TIME SECONDS RECID FILENAME LOCATION TSR Recording Duration
1 116470 2019-04-17 11:19:19 209 343354 20190417-103913_101387_8009015051_116470_11157 https://dialer.connect.fpsi... 101387 0:00/3:29
2 116470 2019-04-17 11:11:58 289 343280 20190417-103913_101387_8009015051_116470_11157 https://dialer.connect.fpsi... 101387 0:00/3:29

Hope you could provide an additional inputs to this kid of incident.

Thanks in advance.

Regards,

Jessie Kid Fernando

[williamconley]

If you have Ingroups set to record, Campaigns set to record, DIDs set to record, and Users set to record ... there will be conflicts.

Each of those is invoked at a different time. It would not be reasonable to segregate the recording into "DID, unti it gets to an ingroup, then end the recording and start a new one for the Ingroup, then end that when the call gets to the user and start a new recording for the user" each with a split second or several seconds depending on the timing of the process, plus the "interaction" between the recording requirements would be a major pain in the asterisk to code.

So instead, each of those recordings, invoked at a different time, creates a file. And all are stored on the lead record since they are all associated with that lead.

PS: Good job posting your specs!

[jessiekidfernando]

Hello Williamconley,

Thanks for your quick reply. Actually the record was only set on the Campaign settings since the calling method for these calls is predictive dialing (ratio). Any other aspect that you think might help us to identify the root cause?

Regards,

Jessie Kid Fernando

[williamconley]

... since the calling method for these calls is predictive dialing (ratio) ...

So ... these calls didn't have any Users involved? And you're saying that since there were no users, the user's recording setting would not be invoked? Or none of the users have recording set? (none, not just one or two you checked randomly, and definitely check all those associated with any of the example leads you checked).

And next up: Please post the carrier diaplan entry field (if you're not comfortable with identifying your carrier, change the name of the carrier to "CARRIERNAME" in the entry before posting). In case there is something non-standard about the carrier's diaplan entry.

Finally: Have you any custom extension entries? Modified the extensions.conf file? Custom dialplan entry in admin->system settings or any admin->server custom dialplan entries?

[jessiekidfernando]

None of the users have recording set. Also no custom dialplan entries either on custom dialplan or directly oon the extensions.conf files.

Here's the dialplan we are using.

Global string: DIALTRUNKUS1 = SIP/twilio-ob

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,n,Set(CallerIDString=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Set(CALLERID(num)=+1${CallerIDString:-10})
exten => _91NXXNXXXXXX,n,NoOp(CallerID : +1${CallerIDString:-10})
exten => _91NXXNXXXXXX,n,Dial(${DIALTRUNKUS1}/+1${EXTEN:2},,tTo)
exten => _91NXXNXXXXXX,n,Hangup()

[williamconley]

in that case i wonder what you have in crontab -e for recording management, and does it properly match your Vicidial Version? no custom scripts there?

[jessiekidfernando]

Hello Williamconley,

We have 4 servers under single cluster. These servers are all agent/dialer server. All cron jobs related to recordings on each server are:


[root@server1]# crontab -l
### recording mixing/compressing/ftping scripts
3,13,23,33,43,53 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
5,15,25,35,45,55 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl --run-check
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl –-MP3
* * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --WAV --YMDdatedir --list-limit=100 --transfer-limit=100 --run-check


[root@server2]# crontab -l
### recording mixing/compressing/ftping scripts
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl –-MP3
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --GSM
* * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --WAV --YMDdatedir --list-limit=100 --transfer-limit=100 --run-check


[root@server3]# crontab -l
### recording mixing/compressing/ftping scripts
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl –-MP3
* * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --WAV --YMDdatedir --list-limit=50 --transfer-limit=50 --run-check

[root@server4]# crontab -l
### recording mixing/compressing/ftping scripts
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl –-MP3
* * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --WAV --YMDdatedir --list-limit=100 --transfer-limit=100 --run-check

[williamconley]

different scripts are active on each of the systems. that's some interesting progress.

why are they different from each other?

why are they not set to the standard scripts?

[jessiekidfernando]

Should the cron schedule and scripts' parameters be the same on all active agent/dialer servers?

[williamconley]

they should be "the same" and they should be "stock" based on the recommendations for your version.

but there are instructions in each of those scripts ... available either by using a text editor to read the file or executing the file with perl and adding "--help" to get the options.

there is also, (of course) the Vicidial Manager's Manual. A ... useful read.