Vicidial agent screen Sorry, there are no available sessions

Ajit Kumar
15 Jan, 2014
1

    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.

vicidial sorry there are no available sessions

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

    Below are list of troubleshoots to resolve the vicidial no available sessions issue.

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

Type screen -list   in linux console,
you should  get below outputs of running screens
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.
vi /etc/rc.d/rc.local

Troubleshoot 3 : Dahdi driver issue

Make sure the DAHDI driver is installed properly by running the below command in the linux shell

dahdi_cfg -v
The above command will display the below result
DAHDI Version: 2.6
Echo Canceller(s): HWEC
Configuration
======================

Channel map:

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_dummy
dahdi_cfg -vvvv
asterisk -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

Note **
For those who are using the Telephony cards like digium, sangoma,allo  follow the below my article on How to configure digium cards and how to configure sangoma cards

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

/usr/share/astguiclient/ADMIN_update_server_ip.pl
just press enter for prompts and enter your new IP once it prompts.

Troubleshoot 5:  Force update the IP in DB

    Sometimes the new IP won't get updated, even after running the IP update script. or DB get updated with some funny letters instead of IP (like  localhost,a]b]d],127.0.0.1:mask2

run the below command to force the new ip to update in db
/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=oldipaddress
enter your new ip when it prompts for new ip.

note: if your db is update with ip as 127.0.0.1:mask2 then run below command
/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=127.0.0.1:mask2

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

login to mysql cli using below commands
mysql -p 
if you dont know the mysql root password then run below command
mysql -u cron -p 1234
Once logged in to the mysql console run the below commands, replace newip and oldip with your IP address.
mysql>use asterisk
mysql>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
reboot the server 

note **  replace  newip  and oldip  with your server ip address.

Troubleshoot 7:  vicidial meetme Conference missing

    Login to the vicidial/goautodial admin page and check whether the conference sessions are created under ADMIN > conferences, ADMIN > vicidial conferences
If it is empty you have to create the sessions, Instead of creating manually we can use the existing script to create in bulk, follow the below steps for the same

login to the server via ssh using putty and run below commands in linux shell
cd /usr/src
svn checkout svn://svn.eflo.net/agc_2-X/trunk
cd /usr/src/trunk
mysql -u crong -p 1234
mysql>use asterisk
mysql>\. /usr/src/trunk/first_server_install.sql
mysql>quit
/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.15
reboot

once rebooted and login as agent and check whether your issue resolved.

Conclusion:

    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

1 Comments
  • Ajit Kumar
    Ajit Kumar April 4, 2022 at 11:23 AM

    vicidial Sorry, there are no available sessions

    Reply
Add Comment
comment url