Topic
Your Session has been disabled - Vicidial
About :
VICIdial is an enterprise class, open source, contact center suite in use by many large call centers around the world. VICIdial has a full featured predictive dialer. It is capable of inbound, outbound, and blended phone call handling.
Description :
You may notice the message "you session has been disabled " under below conditions
1. During agent login to vicidial agent portal
2. After successful login at frequent time its popups this message.
Root cause
Below are few root cause for the above said issue.
1. Vicidial Admin /manager have forceful logged out the particular agent from admin interface.
2. Mysql/Maridb database crash for the table vicidial_live_agent
3. Crontab DB query -queues.
4. Lack of Memory in Server.
Workaround :
1. Vicidial admin force logged out.
Make sure admin access are not misused, use strong password for admin, restrict admin rights .
Make sure public access to dialer is secured , as vicidial admin API can triggered to logout agents.
2. Database Table vicidial_live_agent crashed.
run the below command to check any table crashed in the database.
mysqlcheck -u root -p --check --all-database
(note: if you have set a root password then enter ,or press enter if dont know the password run below command)
mysqlcheck -u cron -p1234 --check --all-database
If you have received below output then the particular table is crashed, you need to repair.
asterisk.vicidial_live_agentsError : Incorrect file format 'vicidial_live_agents'error : Corrupt
Repair Command.
Run the below commands to repair and optimie.
(note if root password is unknow use cron with password 1234)
mysqlcheck -u root -p --auto-repair --all-databases
mysqlcheck -u root -p --optimize --all-databases
Force Repair:
if the above command failed to repair the crashed tabled ,use the below command to force the repair
Login to mysql console
mysql -p
use asterisk;
repair table vicidial_live_agents table use_frm;
optimize table vicidial_live_agents table;
3. Crontab DB query - queues.
crontab entry script that is running at those times that is running a database query that is causing this issue indirectly. ref link
solution: delete the TMM files in mysql data directory
search the .TMM files under /var/lib/mysql/asterisk/
similar to vicidial_live_agents.TMM
delete the file using rm -rf
rm -rf ./var/lib/mysql/asterisk/vicidial_live_agents.TMM
Also run the below command to flush the DB table for entries older than 1 hour
/usr/share/astguiclient/AST_flush_DBqueue.pl --seconds=240 --session-flush -q
I'd recommend changing the DBflush to run every 4 minutes: Ref LInk
### flush queue DB table every hour for entries older than 1 hour (changed to 4 minutes)
1,5,9,13,17,21,25,29,33,37,41,45,49,53,57 * * * * /usr/share/astguiclient/AST_flush_DBqueue.pl --seconds=240 --session-flush -q
4. Lack of System Memory
Check the Current usage of the memory in your system ,by typing top or htop command.
also run free -m to see current free ,used memory
Delete any cached memory by running below command
sync; echo 3 > /proc/sys/vm/drop_caches
you can schedule the above command to run every 30 min in crontab to delete cache at regular interval.
Also check