With certain dialer installations experiencing problems with outbound dialing, the dialing process can be slow or the calls might not go through at all. In this case, open your SSH Client (i.e. we use Putty) and connect to the Asterisk CLI: asterisk -vvvr If your CLI gives you an error/notice similar to: “Extension not found” or
When experiencing database problems, most often manifested by an outbound dialing issue or a time syncronization issue, try running the following command from your SSH client: mysqlcheck -u cron -p 1234 –auto-repair –check –optimize –all-databases
If you are running a predictive dialer (or any kind of Asterisk server) or a web hosting server, you have probably experienced often hacker/lamer brute force attempts. These attacks can be easily blocked by implementing optimal server configuration, using a good Firewall (i.e. SonicWall, PfSense, Tomato) etc. A very useful method of blocking brute force attacks is installing Fail2Ban, which
1. Backup your data Ideally, export your whole database 2. Check if your running version Your version GOautodial CE 2.1 and your MySQL password is the default “vicidialnow”. # cat /etc/vicidialnow-release # mysqladmin password vicidialnow -p Enter password: … 3. Install the GAD yum repository # cd /etc/yum.repos.d/ # wget http://downloads2.goautodial.org/centos/5/goautodial.repo 4. Remove conflicting packages
After updating your GoAutoDial 3.0 CE to the GoAdmin 3.3, some users experience that although calls seem to be going fine in the Asterisk CLI, the agent screen (or the AGC) serve no live calls to the agent. If so, please check the following: That you have updated your Asterisk to 1.8 That you have updated ViciDial
1. Append the goautodial-testing repo # nano /etc/yum.repos.d/goautodial.repo 2. Update Vicidial to 2.7RC1 # yum -y update Make sure to check the active version: # cat /usr/src/vicidial/version …and to change your MySQL password to your original password, if needed # mysqladmin -pvicidialnow password “myoriginalpassword” 3. Update GOautodial-CE package # yum -y update goautodial-ce –enablerepo goautodial-testing
GoAutoDial CE 3.3 monitoring and barge function do not work out of the box. To fix this, log in via SSH and run the following commands: For CentOs distros: yum install glibc.i686 -y For Ubuntu distros: apt-get install libc6-i386 Then run: usr/share/astguiclient/ip_replay/relay_control start Voila!
Creating a suppression list can be very useful when ordering new data / lists from data providers, helping you avoid purchasing duplicates. To create a suppression list, login via SSH and run the following commands: mysql -uroot -pWhen prompted, enter your password. The default for GoAutoDial is vicidalnow, ViciBox – blank. use asterisk; SELECT distinct
Small, clean database will always perform better than a huge one. In order to see what is the total size of all the databases in the dialer, log in via SSH and run the following command: du -kh /var/lib/mysql To check the size of the asterisk database only, you can run: du -kh /var/lib/mysql/asterisk To
Sometimes, admin would like to change / reset only specific dial statuses within only specific campaign – i.e. Reset all NA, NI, NP and similar statuses while keeping others (like DNC, SALE etc.) intact. To do so, log SSH in and open mysql: mysql -ucron -p1234 use asterisk Afterwards, run the following command (Example –
