Hosted Vicidial server starts from $39 Contact Us Buy Now!

Vicidial:Sorry, there are no available sessions

Estimated read time: 3 min

 Sorry, there are no available sessions

(vicidial , goautodial , vicibox, asterisk)
vicidial no available sessions



*****************************************  
Error: Sorry, there are no available sessions
*****************************************

     The major cause for this alert in vicidial

  • vicidial background scripts not running
  • 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
  • Forget to update the new ipaddress in the vicidial database
  • Wrong ip set in DB even after ip updated using the vicidial script
  • MeetMe conference sessions are not created or deleted accidently
~~~~~~~~~~~~~~~~~~~~~~~~~~
Below are the list of troubleshoots to get rid of this issue/alert
~~~~~~~~~~~~~~~~~~~~~~~~~~
*****************************************
Troubleshoot 1-1 :  Vicidial Screens/Background scripts
*****************************************

Type screen -list   in linux console,,
you should  get below 
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 /run/screen/S-root.
Make sure cron entries are there also the vicidial startup scripts
vi /etc/rc.d/rc.local

*****************************************
Troubleshoot 1.2 :  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.

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

If the above command displays error like dahdi not found error
then reinstall the latest dahdi driver ,follow the below link for the reinstalling the dahdi


Once latest dadhi  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 links

Digium          > sangoma     > allo
*****************************************
Troubleshoot 2 :  Updating the server ip in DB
*****************************************

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 fro prompts.

*****************************************
Troubleshoot 3 :  Force update the IP in DB
*****************************************
Sometimes the new ip wont get updated ,even after running the IP update script. or db get updated with some funcky 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 3(a):  update ip with mysql commands
*****************************************
         you can update the mysql commands to update the ip, below are the commands and tables to be udpated with new ip

login to mysql cli using below commands
mysql -p    ; if you know the mysql root password
or
mysql -u cron -p 1234

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 ipaddress.

*****************************************
Troubleshoot 4:  Conference Sessions
*****************************************
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 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
wget https://download.vicidial.com/vicidial/trunk/extras/first_server_install.sql
mysql -u crong -p 1234
mysql>use asterisk
mysql>\. /usr/src/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.
if problem still arises, kindly post in the vicidial or goautodial forums  or  ping me in my skype , below is the skype id

Post a Comment

Cookie Consent
We serve cookies on this site to analyze traffic, remember your preferences, and optimize your experience.