Sorry ,There are no available sessions - In Vicidial While log in as agent you will often see this alert message saying no available sessions. In this article we are going to see the root cause and solution for the issue No available sessions in vicidial.
What is Vicidial?
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.
Major Cause For vicidial no available sessions
The major reason for the vicidial No available sessions issue are stated below
1. vicidial database crashed
2. vicidial background scripts not running
3.The vicidial is using the MeetMe conference module for the agent sessions,These MeetMe conference module requires timing resources like DAHDI, ZAPTEL, or hardware based module like sangoma USB timer , if they are not installed or loaded properly this alert will be displayed
4.Forget to update the new ipaddress in the vicidial database
5.Wrong ip set in DB even after ip updated using the vicidial script
6.MeetMe conference sessions are not created or deleted accidently
How to solve vicidial no available sessions
Troubleshoot 1: Vicidial Database crashed
It is often the vicidial database got crashed due to variable reasons like overload, improper shutdown, lack of disk space due to this vicidial scripts failed to update the session details while agent logs in, to resolve the Vicidial Database crash follow my blog article how to repair and avoid vicidial database crash
Troubleshoot 2 : Vicidial Screens/Background scripts
If the Vicidial background scripts running which are running in cronjob keeps the vicidial up and running , so Make sure the vicidial Screen and background scripts are running properly
There are screens on:2307.ASTVDauto (Detached)2147.astshell20140626063212 (Detached)2105.ASTVDadapt (Detached)2304.ASTlisten (Detached)2301.ASTsend (Detached)2153.asterisk (Detached)2109.ASTconf3way (Detached)2107.ASTfastlog (Detached)2310.ASTVDremote (Detached)2298.ASTupdate (Detached)
If some sockets missing or No Sockets found in screen -list command output
Make sure crontab entries are there by typing crontab -e, if its empty copy paste the default vicidial cronjobs which I mentioned in my Vicidial scratch install article
also the vicidial startup scripts enabled in below file.
Troubleshoot 3 : Dahdi driver issue
Make sure the DAHDI driver is installed properly by running the below command in the linux shell
DAHDI Version: 2.6
Echo Canceller(s): HWEC
0 channels to configure.
If the above command displays error like dahdi not found error
then reinstall the latest dahdi driver, Follow my How to remove and reinstall DAHDI article
Once latest DAHDI reinstalled then run the below commands to load the dahdi drivers
modprobe dahdi_dummydahdi_cfg -vvvvasterisk -rx "module unload chan_dahdi.so"asterisk -rx "module load chan_dahdi.so"reboot
Now login as agent and check whether the problem arises, if not follow other troubleshoots
Troubleshoot 4: update the server IP in database
Once you have changed the server IP address you need to update the same ip in the vicidial database, run the below command to update ip in vicidial DB
Troubleshoot 5: Force update the IP in DB
Troubleshoot 6: update IP with MySQL commands
Sometimes in vicidial the new IP address will not updated properly for Phonse, conferences and server , you can use the MySQL commands to update the IP, below are the commands and tables to be updated with new IP
mysql -u cron -p 1234
mysql>use asteriskmysql>UPDATE conferences SET server_ip='
newip' where server_ip=' oldip'mysql>UPDATE vicidial_conferences SET server_ip=' newip' where server_ip=' oldip'mysql>UPDATE servers SET server_ip=' newip' where server_ip=' oldip'mysql>UPDATE phones SET server_ip=' newip' where server_ip=' oldip'myql>quit
Troubleshoot 7: vicidial meetme Conference missing
cd /usr/srcsvn checkout svn://svn.eflo.net/agc_2-X/trunkcd /usr/src/trunkmysql -u crong -p 1234mysql>use asteriskmysql>\. /usr/src/trunk/first_server_install.sqlmysql>quit/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.15reboot
once rebooted and login as agent and check whether your issue resolved.
Hope this article is helpful in resolving the vicidial issue "Sorry, There are no available sessions" while logging as agent .For professional support reach me on skype or telegram id: striker24x7