vicidial.org

Hello Team,
I will need some help as this is important to our QC. For some reason, recordings stopped appearing under user stats. in campaign, it is set to allforce and has been working for over six months. From Inbound DID, I can see the recording links, from the cli I can see the recordings in the directory. but with user stats, it does not show under location.









Cluster of three servers, 2 dialers and 1 web and DB server
2GSM gateways and 2 E1 lines
Vicibox10
VERSION: 2.14-832a
BUILD: 211027-1031
© 2021 ViciDial Group

Thank you for posting your stats.

Are your recording scripts running in the crontab successfully on ALL dialers?

Example possibility:

Code: Select all

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 --MP3 --run-check --ftp-persistent --ftp-validate


Note that you can run these with --debugX to see what happens.

Below are my recording scripts in crontab. Do I need to modify anything?

### 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 --MP3 --run-check
#0 1 * * * /usr/share/astguiclient/AST_CRON_audio_4_ftp2.pl --ftp-server=server.ip --ftp-login=user --ftp-pass=pass --ftp-directory=/ --ftp-persistent --ftp-validate --transfer-limit=10000$

Yes. Those are the scripts. Now: Are they running successfully?

Check your system logs. Check your /var/log/astguiclient logs. And run the scripts (with --debugX) and see if they run or crash.

I think it is running with error.

dialer:/var/log/astguiclient # perl /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --debug

----- DEBUG -----

Can't find soxmix binary! Trying sox...
DONE... EXITING

worseo wrote:I think it is running with error.

dialer:/var/log/astguiclient # perl /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --debug

----- DEBUG -----

Can't find soxmix binary! Trying sox...
DONE... EXITING

Perhaps try again with --debugX for more information, but if soxmix is missing, of course it's failing. The question is ... how did soxmix disappear? Did you reinstall? Did you get infected? Did you alter the format of the stored recordings? (from GSM to MP3 to save space?)

If soxmix is missing, your installation was not complete. But it can be added.

Everything was working until one day it suddenly stopped. I did not make any change. How can I reinstall soxmix without causing further problems?

Installing a package (such as soxmix, specfiically) shouldn't disrupt at all. The question is how it disappeared. If it didn't disappear (always a possibility) why did the system suddenly stop finding it.

Backup before attempting, but I'd start with installing soxmix to see if it was somehow deleted. If you're not sure how, have a look in the vicibox installer script.

This is what I get trying to install soxmix.

dialer02:~ # zypper install soxmix
Retrieving repository 'openSUSE-Leap-15.3-PERL' metadata ..............................................................................................................................[done]
Building repository 'openSUSE-Leap-15.3-PERL' cache ...................................................................................................................................[done]
Retrieving repository 'openSUSE-Leap-15.3-ViciDial' metadata ..........................................................................................................................[done]
Building repository 'openSUSE-Leap-15.3-ViciDial' cache ...............................................................................................................................[done]
Retrieving repository 'openSUSE-Leap-15.3-ViciDial-Ast13' metadata ....................................................................................................................[done]
Building repository 'openSUSE-Leap-15.3-ViciDial-Ast13' cache .........................................................................................................................[done]
Retrieving repository 'openSUSE-Leap-15.3-ViciDial-ViciBox' metadata ..................................................................................................................[done]
Building repository 'openSUSE-Leap-15.3-ViciDial-ViciBox' cache .......................................................................................................................[done]
Loading repository data...
Reading installed packages...
'soxmix' not found in package names. Trying capabilities.
No provider of 'soxmix' found.
Resolving package dependencies...
Nothing to do.


dialer02:~ # zypper install sox
Loading repository data...
Reading installed packages...
'sox' is already installed.
No update candidate for 'sox-14.4.2-bp153.1.23.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.

The highest available version is already installed

Code: Select all

updatedb
locate soxmix

Then find the part of the offending script that attempts to use soxmix and find out why that script can't find it. Assuming it's there, of course. Usually soxmix vicidial scripts attempt to check a couple locations for soxmix and use the one that's found.

This is also where I suggest that posting the FULL installer name/version is handy. If this turns out to be some sort of bug, linking the bug to the version of the installer may be helpful for others with the same issue. Plus it's just a good idea to put that information in your original post anyway.