AB> How does one go about capturing a caller's Caller ID
AB> information?  I'm running Bink/Max under OS/2 and Courier
AB> v.everything modems.
Hmmm... I can see Gary tensing already... I'll be brief, honest... :-) This 
should answer the questions of several who wrote about it:
Not sure on the Couriers, but for Bink/Max/DOS and a Supra, its pretty easy. 
First you enable CID on your modem, which for a Supra means just adding 
#CID=1 to your init. Then you add a couple lines to Bink's config files, 
namely:
modemignore RING RESPONSE
Modemringing RING
ModemRinging Nmbr  <---- This one and
modemringing Mesg  <---- This one
modemconnect CONNECT
Or just Nmbr if you only have Number Delivery instead of Name/Number. Watch a 
CId response from your modem to get the exact verbage to put there. Poof, 
you're done. Caller ID info will be displayed when the caller calls, and Bink 
will log it. If you use a program like Sentry CID or similar that I mentioned 
earlier, it will let you screen calls, and ALSO aside from its own log, 
writes a quick two-liner to MAXIMUS'S log as to who called. So you see an 
unbroken entry when you're looking for info on someone, instead of having to 
paste together two different logs, like this:
: 22 Dec 09:15:53 SCID Scanned number is (541)
                       888-xxxx [Doe, Joe & Jane]
+ 22 Dec 09:15:54 SCID Jane Doe - AUTO-LOGIN/NO AUTO-PASSWORD (2)
+ 22 Dec 09:15:58 MAX  Begin, v3.01
: 22 Dec 09:15:59 MAX  Caller at 2400 bps
+ 22 Dec 09:16:01 MAX  Jane Doe calling
and so on.  More than once I've called the parents of someone who was 
misbehaving the next day and asked them about the calls... which were 
received here in the early AM. "It can't be our son, he was up studying all 
night in his room... HMMmmm... we'll look into it.." In one case, the dad 
asked for the logs to be mailed to him.
Problem solved... :-)
Mark
---
---------------