HooDaHek 0.2 review

HooDaHek (hoo-dah-hek, as in 'who-the-heck?') is a collection of Asterisk AGI scripts, CGI scripts, and MySQL tables intended to impl

License: GPL (GNU General Public License) File size: 4K Developer: Nathan E. Pralle

0

HooDaHek (hoo-dah-hek, as in 'who-the-heck?') is a collection of Asterisk AGI scripts, CGI scripts, and MySQL tables intended to implement your own in-house Caller ID database and notification services.

I wrote these scripts originally to enable my household phone system to identify who was calling, be able to modify and specify my own custom CallerID labels, and to have the phone system alert us via AOL Instant Messenger or MSN Messenger as to who was calling (or had called).

Here are some key features of "HooDaHek":
Caller calls into your Asterisk system via IAX, SIP, or PSTN
Your extensions.conf context sends CLID information to the hoodahek_dbhandle AGI script.
hoodahek_dbhandle determines if the caller has called before based on the phone number.
If YES, it does nothing.
If NO, it inserts a row into the 'hoodahek' table to identify the caller on subsequent calls. The initial information used is the information supplied by the telco's CLID transmission. If configured, an email is sent notifying someone of the insertion into the system. This information can then be edited by the CGI scripts provided.
Control returns to the dialplan.
The dialplan passes information to the hoodahek_notify AGI script.
hoodahek_notify looks to see if stored information about this caller is in the 'hoodahek' table.
If YES, hoodahek_notify uses this information to announce the caller via AIM/MSN.
If NO, hoodahek_notify looks to see if the CLID system has passed information about the caller (name, number)
If YES, it uses that information to announce the caller via AIM/MSN.
If NO, it announces the caller anonymously.
hoodahek_notify uses the information it found to write a call queue file in the queue directory for the hoodahekbot.
Control passes back into the dialplan to do whatever comes next.
hoodahekbot scans the queue directory every second to look for new call files. When it finds one, it opens it, scans in the lines, and deletes it. It then sends an IM to each recipient as configured.