Reports work in AsteriskNow 1.5

I suppose you have already installed AsteriskNow 1.5 and you would have found that reports don’t work out of the box. It always says “No data”. Apparently the system is not logging the calls and we have to enable this with some additional configuration. Below are the steps for that:

Login to your asterisk server as root and type yum install asterisk-addons-mysql. Select Y when it asks for installation. Once this is done you can see that all calls that go through your server are tracked and reported. But the Admin web interface displays the following error: reporting an error “Asterisk Manager Connection Failure” (If you don’t get that error then below step is not required).

To fix the error go to web interface, Choose Administrators under Basic section. Select admin user and give the password (same as what you have in amportal.conf and manager.conf files). Apply changes. That’s it.

After that the system will starts tracking all the calls getting through it.

AsteriskNow 1.5 installation tips

AsteriskNow 1.5 was recently released. I already had a box with 1.0.2 version and thought of giving the new version a try. Downloaded the ISO from the site and burned it to a CD. The new version is built on CentOS 5.3. I installed the new version in the same system overwriting 1.0.2. Note that the installation did not detect the old version nor did it give me any option for upgrade. Since my server was not in production i went ahead removing all the partitions and reinstalled the new version. If you have a production box backup the configuration files or install the new version in a test system and then copy the existing setup/accounts. You have been warned.

I installed AsteriskNow with the default partitions schema. Read more at http://techsk.blogspot.com/2009/04/asterisknow-15-installation-and.html

Selectively relay emails using postfix

Several machines in my internal network run automated jobs and send out emails. All emails were getting delivered without problems and one fine day my public IP got listed in RBLs and the mail servers, using those RBLs, stopped accepting mails from mine.

I have now set my main network router to restrict outgoing port 25 so that my public ip doesn’t get black listed again. This means Internal machines cannot send mails to any of the domains outside my network. I needed a mechanism to route all my emails through my external mail server which has a proper mx record. My external email server, that is outside my network, allows users to relay emails only after successful auth on port 465 (SSL).  I configured postfix for this. Read More

FTPs in VSFTPD with existing keys from httpd

Once a security key is issued for a particular service (eg: tomcat) it won’t be possible to reissue another key for any other service. But we can use the same keys in many services with some little work.

Read this to configure ftps in vsftpd using Apache httpd’s SSL keys.

how to run a cronjob on last Friday of every month

Posted new entry on the above topic here: http://techsk.blogspot.com/2008/06/how-to-run-cronjob-on-last-friday-of.html

Saravana Kumar

Blogged with the Flock Browser

Tags: linux, cron

Learning about SAN – Basics

When you first get to work on SAN it may be difficult to understand how it works and what those terms mean. I have put up an article on basics of SAN. Tried to be as simple as possible.