Wednesday, February 15, 2017

8 Sockets Detached Only in Asterisk, Can't call Softphone

After my hard drive was full again from recordings, I deleted the extra recordings and then rebooted. After this, the users told me that their X-Lite (our softphone) wasn't being called into the conference anymore.

For those unfamiliar, every time the agent logs into the website of Vicidial, the softphone will ring and will join a conference. Vicidial will dial numbers and when it gets an answered call, it will connect this phone call to the conference.

Upon checking using the "screen -ls" command, there are only 8 sockets detached (vs the usual 9). I found that "astsend" was missing. I assume this is the socket that "sends" the calls to the softphones.

I found 2 suggestions on how to fix it:

1. Recompile Asterisk - I don't know how to do this exactly, but might be worth looking into for those who know how to do this.

2. Perform a Mysql Repair - Thankfully, this was the solution that worked for me! Turns out, when deleting unwanted recordings, it also damaged the mysql database.
mysqlcheck --auto-repair asterisk
sudo reboot
After performing the mysql repair and rebooting, Asterisk now calls my X-lite again.

Sunday, January 22, 2017

No More Leads in the Hopper for Campaign

Early this morning, I had to free up some space by deleting unneeded .WAV files. Later in the day, we found out that we couldn't make any outbound calls for all of the campaigns (but we could still receive inbound calls). The error was "No more leads in the hopper for campaign: <campaign name>". This was the same error message regardless of if it was Manual Dialing or Predictive Dialing.



I found the way to identify the issue through Support ALG's blog (see link below).
https://supportalg.blogspot.com/2015/06/how-to-fix-error-this-campaign-has-zero.html

It was the 2nd method that helped me identify the error:
/usr/share/astguiclient/AST_VDhopper.pl --debugX
Sorry, I was only able to get a partial screenshot

Because of this, I was able to identify that the /asterisk/vicidial_list table had crashed. After googling "table vicidial list is marked as crashed", I found this vicidial.org forum thread:
http://www.vicidial.org/VICIDIALforum/viewtopic.php?t=20206

Scrolling down below, I found this command (first when mysql has no password, second has password - you'll only need one of them):
mysqlcheck --auto-repair asterisk vicidial_list
mysqlcheck --auto-repair asterisk vicidial_list -p

Now after running the mysqlcheck, I logged out of and in to the campaign, and I can dial outbound calls again!

Tuesday, November 22, 2016

Long Silence at the Start of Inbound Calls

It's my first time setting up an inbound call and I ran into a problem where after the initial 2 rings, there's a long silence before the greeting plays. The longest was 17 seconds!

If I were the customer and there was no sound for 17 seconds, I'd hang up immediately. Customers hanging up mid-way isn't a good thing, of course.

Here are the steps I did to remedy the situation:
  1. Make sure the DID points to the IP address you need: It will take longer to route the calls to the right place if you have 2 or more servers. I had our DID provider remove the 4 other unnecessary IP addresses which shaved off 10 seconds.
  2. [Update: Don't do this! I ended up having a lot of outbound calls dropped because asterisk couldn't find this file] Remove sip-silence.gsm from the sequence: Observing asterisk logs, when an inbound call arrives, sip-silence.gsm is played twice before the first greeting. I'm too scared to tinker with the asterisk script (it's a really long text of code) and remove the 2 lines of sip-silence. Instead, I just renamed sip-silence.gsm into sip-silence2.gsm so it would skip playing that file. This shaved off another 3 seconds. Aside from removing sip-silence.gsm, I was thinking of replacing it with a ringing sound. However, I can't find the default ringing sound in the asterisk folder, so I chose to just remove sip-silence.gsm instead.
From 17 seconds of long silence, I was able to cut it down to 4 seconds of silence.

Tuesday, November 8, 2016

Converting Sound Files to WAV for Vicidial

I felt like I should post what settings I put in to convert sound files to .wav for Vicidial (For call menus and voicemail greeting). I did it the last time, but I forgot it today. Now, I'm taking down notes so I won't forget in the future.

Link to Online Converter:
http://audio.online-convert.com/convert-to-wav

Settings Needed:

  • Change Bit Resolution: 16 Bit
  • Change Sampling Rate: 8000 Hz
  • Change Audio Channels: Mono
  • PCM Format (Under advanced options): PCM Unsigned 8-bit
Anything else higher than this won't work.

Monday, August 22, 2016

Audio Store is Just A White Box

I encountered the "plain white box" error upon clicking any link in the administration which mentions "audio chooser". I also mysteriously found that by clicking this and having the white box issue, the disk space runs out quickly and I have to delete the logs.

By following the instructions here, I was able to fix the problem.
http://striker24x7.blogspot.com/2014/06/vicidial-goautodial-audio-store-white.html

Turns out, the directory that Vicidial was pointing to did not exist. I needed to create the folder and made sure the permissions were okay.

Now, upon clicking the Audio Chooser, this pops up!

P.S. Striker 24x7 - I <3 you!



Wednesday, July 27, 2016

There is a time synchronization problem with your system [Unsolved]

While calls were happening, the system stopped calling. The error message was "There is a time synchronization problem with your system, please tell your system administrator".

It could be a number of errors, but according to our provider, it was because our RAM wasn't working anymore. The server was 2 years old and was used every weekday since then.

When I replaced the RAM, it was working again for a while. But then the problem came back.

Until now, I still don't know why the error happens and I haven't been able to get back to it.

Tuesday, April 5, 2016

No MySQL.sock because Root Partition is 100% Full

Last week our Vicidial Server crashed and our agents couldn't make calls anymore. After restarting the server and trying to do the ol' rename-mysql.sock solution, I found that the mysql.sock file was missing. What gives??!

When I try to access the agent page in Vicidial, the error was: "MySQL connect ERROR: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)". Normally, I would follow the process of renaming or deleting the existing mysql.sock file then restart the mysql service. However, this time, there was no mysql.sock. (Impt: Please DO NOT delete the mysql! They are not the same as mysql.sock!)

After checking with the provider, turns out that the root partition is already full. Here are the steps that the provider gave to resolve the issue.

Steps and SSH commands:
  1. Find out how much space you have left.
    SSH Command: df -h
    In the Admin Page, go to "Reports" and scroll down and look for "Disk". It should provide the percentage of use.
  2. Delete unwanted files. In this case, you can delete the .WAV duplicates. It won't delete your .MP3 recordings.
    SSH Command:
    rm -f /var/spool/asterisk/monitorDONE/ORIG/*.wav
    rm -f /var/log/httpd/*
  3. Restart the server via SSH. Do not just push the power button or pull the plug.
    SSH Command: sudo reboot
And there you go! If that still doesn't work but you have the mysql.sock file already, follow the old process of renaming or deleting the existing mysql.sock file then restart the mysql service