Caller ID capture

Bob Hansen · Post by **Bob Hansen** » Fri Dec 14, 2007 4:27 am

I am trying to create a unility script like this concept:
IF ComPort input includes Caller id Then Run Database routine.

I know of a number of utilities that display Caller ID on screen, and adds to log files. Using Macro Scheduler, I am currently monitoring the log file for change, then reading the last line, parsing out the caller's number. I then send that number to a database application to retrieve the customer record for that caller.

But this involves too many products and is too slow, I want the record to show pn screen before the call is answered.

What I am looking for is a method to trap the caller id at the com port myself, creating a new file with just the caller phone number. That way I can run a macro in the background. If File Exists, retrieve the customer record.

I know that the caller id comes in the com port between the first and second ring. Is there some command line, VBScript, or other utility I can use to capture the com port and trap the caller id?

Post by **Marcus Tettmar** » Fri Dec 14, 2007 8:47 am

The question is - do you have exclusive access to the COM port?

If so then, in theory, you can use ReadLn:

ReadLn>COM1:,1,line

You'd need to have a loop that keeps doing that looking for the data you want.

It is one thing reading from the COM port if you are the only one doing so, but if you wish to intercept data being read by some other application then that is a different matter. To do that you would need something like this ActiveX serial port sniffer:

http://www.serial-port-communication.co ... r-activex/

Me_again · Post by **Me_again** » Fri Dec 14, 2007 4:37 pm

If the traffic on the com port is only one way, i.e the PC is just listening to the other device with no handshake, you can use GPS Gate to share the data between multiple apps with no com port conflicts using virtual serial ports. (Although it's designed for GPS it will handle any serial data, just the GPS specific functions aren't any use to you.)

Bob Hansen · Post by **Bob Hansen** » Fri Dec 14, 2007 6:11 pm

Thanks for suggestions, I will follow up on them.

Re dedicated usage of the com ports, I was expecting to be using a modem with caller id capabilities. This is getting in hardware issues that I am not yet familiar with. Not sure how this fits in with the suggestions above, but I am sure I will find out.

Me_again · Post by **Me_again** » Fri Dec 14, 2007 7:39 pm

Are you thinking of having the modem on the same line as someone answering the call? I think that should work, this basic info may help. http://www.mtnsys.com/Pages/howto/htmdmtst.htm