Who Calls

This Excel sample uses the Samples\CallLog.xls database to record the caller information for an incoming caller. It is a simple example that logs every call through its date/time and CallerID. The advantage of using VBS rather than DDE is that Excel does not need to be kept open.
The syntax is exactly the normal VBS (Visual Basic Script) syntax except that the variables are replaced before the execution of the script.

const StartRow = 4 'First row to use
Dim ex, I
 

'Get path of WhoCalls directory
Set WSHShell = CreateObject("WScript.Shell")
sCurPath = WSHShell.RegRead("HKCU\Software\MAW Software\WhoCalls\" )

Set ex=CreateObject("Excel.Application")
ex.Workbooks.Open sCurPath & "\Samples\CallLog.xls" 'Open file

'Find first empty Line
I=StartRow 
while ex.ActiveSheet.Range("A" & I).Value <>""
    I=I+1
wend

'Record values
ex.ActiveSheet.Range("A" & I).Value = "@DATE" 'Set Time
ex.ActiveSheet.Range("B" & I).Value = "@TIME" 'Set Date
ex.ActiveSheet.Range("C" & I).Value = "@CID"  'Set CallerID
ex.ActiveSheet.Range("D" & I).Value = "@CIN"  'Set CallerID Name
ex.ActiveSheet.Range("E" & I).Value = "@PORT" 'Set Port
ex.ActiveWorkbook.Save
ex.Quit
WScript.Quit(0) 

VBS Call to MSAccess  

Dim AccApp, dbs, rst

'Get path of WhoCalls directory
Set WSHShell = CreateObject("WScript.Shell")
sCurPath = WSHShell.RegRead("HKCU\Software\MAW Software\WhoCalls\" )

Set AccApp= CreateObject("Access.Application")
AccApp.OpenCurrentDatabase(sCurPath & "\samples\CallerCenter.mdb")

Set dbs = AccApp.CurrentDb

Set rst = dbs.OpenRecordset("SELECT * FROM CallLog")

rst.AddNew

rst.dDate ="@DATE" 'Set Time
rst.tTime ="@TIME" 'Set Date
rst.cCID ="@CID" 'Set CallerID
rst.cCIN ="@CIN" 'Set CallerID Name


rst.Update

'Clean up
rst.Close
dbs.Close
set rst = Nothing
set dbs = Nothing
AccApp.Quit
set AccApp = Nothing

WScript.Quit(0) 
 

VBS Call to MySQL
This sample connects to a MySQL database to transmit the received information.
Please refer to the VBS code for more information.

Please note that DDE should not be used anymore as it is an outdated technology now. The DDE samples here are given only for reference, in the case your application still requires a DDE connection.

DDE to MsAccess

The MsAccess sample uses DDE and the Samples\CallerCenter.mdb database to display the caller information of an incoming caller.
If MsAccess is not yet running it will be started by using the information in the EXE Path and DB Path field of the Setup.

No data will be "poked" (transferred) as all data transfer is handled by the commands. 

Line 1 shows the usage of a comment by using a semicolon in front of the line.
Line 2 requests MsAccess to emit a beep.
Line 3 runs a SQL query that adds the Date, Time and CallerID information to a table called CallLog in MsAccess. This table will be used to monitor the frequency of the calls received by every caller.
Line 4 opens the form Customers and displays the record with the matching CallerID.
Line 5 runs a macro that enters the CallerID information into the right field if a new record is created.

Note:
For the sample to work correctly it is important to change the security settings of MsAccess to allow the running of macros without asking for your permission. (Tools->Macro->Security->Low) and to also disable Options->Edit/Find->Confirm: Record changes and Options->Edit/Find->Confirm: Action queries.

DDE to Excel

The Excel sample uses the Samples\CallLog.xls database to record the caller information for an incoming caller. It is a simple example that logs every call through its date/time and CallerID.
If Excel is not yet running it will be started by using the information in the EXE Path and DB Path field of the Setup
As soon as the CallerID is available it is transferred "poked" to the Excel sheet CallLog.

The "Poke data" field is set to

@DATE{TAB}@TIME{TAB}@CID{TAB}@CIN{TAB}@PORT

which sends the Date, Time, CallerID, CallerName and Port information across five columns, the destination being from cell R3C1 to R3C5.

Then two commands are executed.

Line 1 selects the cells R3C1 to R3C5 and Line 2 inserts an empty line above. This ensures that the next time information is transmitted it will not overwrite the previous data.

Server Mode

WhoCalls can also run in server environment. This means that you may have WhoCalls running on one PC with a modem attached and distribute the received caller information to other PCs running WhoCalls in client mode. The clients do not need to have a modem as they receive the required information over the network.
The following schema shows a possible configuration:

The server starts WhoCalls with the /server command line while the clients start it with /client and the IP address of the server.
The server can still be used as normal WhoCalls station in active or passive mode. If the server only acts as gateway without displaying any information, then select the server mode in the settings.

IMPORTANT: Please make sure that the port used for the communication between the client and the server (Default: 50134) is not blocked by a firewall, this for the server and all the clients. Instead of opening the port you can also enable the communication for the two processes ..\whocalls\WhoCalls.exe and ..\whocalls\WhoCallsService.exe)

Server Mode as Windows service

For additional security you can also run the WhoCalls server as Windows service. This will run the WhoCalls server as background task and just let it distribute its information it receives through the modem.
To install WhoCalls as service please follow those steps:

1. Start WhoCalls.exe without command line.

2. Configure the modem, server port and directory you want to use in the settings.

3. Close WhoCalls.exe

4. Install the service with the short cut provided under ..\WhoCalls\Service\InstallService

5. Start the service with the short cut provided under ..\WhoCalls\Service\StartService

6. Check with the Taskmanager that the process WhoCallsService.exe (runs under the SYSTEM account) is running. If not please go to the Windows services and try to start the service manually.

From then on the service will start every time you start your computer. To uninstall the service again please follow those steps:

1. Stop the service with the short cut provided under ..\WhoCalls\Service\StoptService

2. Uninstall the service with the short cut provided under ..\WhoCalls\Service\UninstallService

Dynamic Data Exchange (DDE)

DDE has three parts: the name of the application; the file name or topic; and the cell range, value, field, or data that's referred to. The following illustration shows the parts of a remote reference formula and the use of the required separator character (|).
 

Topic:              Excel|Sheet1
Item:                R1C1  

You can either get data form a DDE server, send data to the DDE server or execute a macro on the DDE server.
The program that contains the data you want to link must support Dynamic Data Exchange (DDE). To determine whether your program supports DDE or to learn the DDE name and topic information for the program, contact the software vendor of the program.

Note(s):

• To be able to read values from an application through DDE the application needs to be running.
• To access data on a remote computer on a network use the NetDDE format as topic.
  IE \\ComputerName\Application|Topic
• When using Excel please note that the Topic and Item is language dependent. This means that for instance in German a call to cell A1 in Excel becomes
      Excel|Tabelle1 and Z1S1 

Caller ID

To use WhoCalls with Caller ID you need two things:

*       Caller ID Service From your local telephone company
*       A MODEM or hardware device that supports Caller ID

The first is required as only your local telephone company can supply this data. The second is required so that the data sent by the Telephone Company can be passed to software programs for processing.
Many current MODEMs offer support for Caller ID. The key question is always what setup string to use to enable Caller ID (virtually every MODEM disables Caller ID as the default).

For most MODEMs, the string AT#CID=1 will enable Caller ID. On some voice based MODEMs the string is AT#CLS=8#CID=1. Look in the user's manual for your MODEM to see if any setup string is referenced or mentioned.

Other common setup strings are:

*       AT#CID=2
*       AT%CCID=1
*       AT%CCID=2
*       AT+VCID=1
*       AT#CC1
*       AT*ID1

The best way to test is to use a terminal data program. In Windows 3.X, the TERMINAL program (usually in the accessories folder) can be used, (be sure you set the COM port to the PORT your MODEM uses). In Windows 95 the HyperTerminal program can be used.

To use HyperTerminal do the following:

1) Select "HyperTerminal" by navigating through the Start button to "Programs," then "Accessories," then "HyperTerminal"
2) Double click on "hyperterm" or "hyperterm.exe"
3) Name the new connection "test," and select OK
4) Change the "connect using" to Direct to COM X, were X is the COM port used by the Caller ID device
5) Click on OK on the screen for port settings

To test your MODEM, do the following:

1. Type the string ATZ, (OK should appear on the screen)
2. Enter the Caller ID string to be tested, (AT#CID=1 for most modems)
3. If OK results, continue; If ERROR results the modem may not support Caller ID; try a different setup string
4. Have someone call you and watch the terminal screen
5. If Caller ID is working, you will see the word RING, followed by one or more additional data lines. The word RING will then continue to appear for each incoming ring.
6. If Caller ID is not working, you will only see the word RING for each incoming ring. If this is the case try another setup string and go back to step two.

  The most common result, when Caller ID data works, is the following:

        RING
        DATE = xxxxx
        TIME = xxxx
        NMBR = xxxxxxxxx
        NAME = xxxxxxxx
        RING
        RING ...

How can I get more information?