WhoIsCalling 1.0.0b2 README

WHAT is this?
This project aims at providing the CLI (caller line identification) information on your computer terminals, whenever you get a call on your landline telephone. It works as a Windows service in background and listenes for incoming call data on serial port. On data arrival. It tries to parse the data and broadcasts extension and calling no details on network as UDp packets, so that any client application listening for broadcast can use the information as per their logic.

WHY/WHERE should I use it?
It can be used in many situations/places. e.g.

1. In Inbound call centers : You can create a custom client application which will get the customer information from database and with the use of this server you can know which client is calling you (even before the call lands on your handset, provided the EPABX sends the CLI information before transferring the call to extension)
2. In telemarketing
3. Any other which you can think of...
In short it can be used anywhere where you want to get alert of the incoming call.

HOW to use?
To use this server you need the following..

1. Dot Net v2.0 (It should be able to work on MONO also, but I haven't tested it on MONO)
2. A decent PC with operating system >= Windows 2000
3. A working serial port (RS232)
4. EPABX which provides incoming call information on serial port.
5. Lan card >= 10 MBps

To use it..
1. Install the server (Install Dot net 2.0 framework if it is not already installed before installing this application)
3. Change configuration accroding to your needs using WICConfig utility provided with the package.
4. Make sure that RS232 port is in working condition and EPABX is really sending incoming call info on RS232 port. You can check this on hyperterminal.
5. If everything is in order then restart the WhoIsCalling service from service manager.
6. sit back and enjoy the incoming call alerts...

1. The only problems which I have faced till now in this release, is the firewall blocking the UDP broadcasts.

Changes since last version
1. WIC now uses SQLite (www.sqlite.org) for database backend, so there is no need to seperately install and configure MSDE/MSSQL Server database for the WIC service. WIC use System.Data.SQLite package (http://sqlite.phxsoftware.com) for database interaction.
2. UDP broadcaster code has been merged with the WIC source.
3. A utility (WICConfig) has been included with the package for configuring the WIC Service.
4. And most importantly WIC project gets its name :). Previously it was just cliserver-net.

If you have any problems, comments, suggesstions etc regarding WIC, you can contact me on really.dumb.coder@gmail.com.

Code well,
Dumb Coder