Sean ..
Hello, All.
Anyone know how to set up BinkleyTerm with caller ID?
The first part of this is the needed modem commands to make sure that your modem will spit out the caller ID data. At that point, you set up the modem initialization string in the Bink configuration file to get the modem to do that. This setup is task oriented in the Binkley.cfg file. For example, here is a part of my Binkley.cfg file for Task#3,based on the ZyXel 2864e+ modem(s) I've used here for years.
[%Task%==3]
; ZyXEL 2864E+ ROM 6.92
WindowTitleFmt BT-XE #%%d : %%s
PutEnv ADAPTER=MODEM
PreInit v``^``
Init AT&FE0M0S0=0S7=80S11=55S40=4|
;PreDial ATDT,*67W
;Predial v``^`````ATDT*67W
Prefix ATDT*67W
Answer ATA|
NoFilter /ARQ
ModemTrans 1 / /HST
ModemTrans 2 / /V32
ModemTrans 4 ATDT*67W/ /ZYX
ModemTrans 8 / /VFC
ModemTrans 16 / /V32T
ModemTrans 32 / /V120
ModemTrans 64 / /X75
ModemTrans 128 ATDT/ /INH
AfterCall 17 ATI2|
In the Init codes above, one of the S codes enables the ID to be yielded by the
modem. Then, to make sure you get to see it, you have to set the answer mode to not answer until at least the SECOND ring. The reason for that is that if the modem answers on the first ring, you won't get to see the output from the caller ID from the modem. At this point,with this done, you'll get to see the caller ID spit out in the Binkley log when the modem answers on the second or third ring.
A caveate is needed here. In many cases, the modem doesn't reset to clear the caller ID spin out until you send the init string back to it for a full init as
in the above. This means that unless you do the full init, you'll not see a caller ID processed after the full init. You won't see the next ID until a full init has been processed by the modem again. This, as far as I know, varies from modem to modem as to how they work. You'll just have to experiment. Each modem is different as to what commands control the specialized operations for the modem.
Now .. what do you do with this data and how can you use it? There is a registered use only option of some kind with either Bink or Max, I'm not sure what. I think that is based on whether or not the BBS for an automated connection is in the nodelist or not. But I'm not aware of any way to punch out user exit calls from a give CNID return.
As well, chasing the CNID snoop data in the BBS log is a little interesting. It is just a line of data among many. For my own use here, as part of my ZIPLOG professional management template, I long ago wrote a complete CNID trace
and emergency page, trash a call, or evne call the cops if needed program, based on the Rochelle professional caller ID adapters. Rochelle over in Austin, Texas, has for years made a special state mode dedicated little computer to monitor phone line activity. Two models are made, one which serves
two lines and a more expensive one, the Model 2046 four line version. This tool returns not only caller line ID, but full call progress tone and all other
tone sequencing data for each line in full stateful I/O via a serial port connection. You can write a program which uses their stateful data output for *ALL* things that go on over each of the phone lines and use the data for whatever.
In my case, every bit of data is analyzed in my professional ZNITCH program, all data digits, pin codes, call progress tones, the works. My program not only
logs *ALL* outbound, inbound, and security code traffic for all the phone lines, but it also can intercept any given phone number, in or out, any given security code, in or out. It can then, if needed, forward the data or perform some other dedicated outbound dial or TCP action to whatever other entity is needed. Be it you personal pager, your text messaging, the local police department,if needed, the CIA, FBI .. whatever.
The entire phone line activity is also professionally interfaced with full total ID and use creation and case analysis for my entire professional template
operations in ZIPLOG. It can be automerged, as needed, even with professional RF site monitoring for such things as HF or other RF channel activity. All in REAL-TIME and all with complete GPS latitude and longitute coordinate tracing in REAL-TIME, if that data is available from the output or database support. Since 1974 here!
You could, for example, cross-reference any phone call activity, inbound or outbound, against RF site monitoring data, if you are authorized to do that, for example, with professional receiver and monitoring tool equipment, to cross
compare in REAL-TIME what someone at or into the hard montitored site might be doing with RF transmission of data at some remote site as well.
At this time, for the whole Net 117 Fido operations for at least the largest ZNITCH database I have, which is mirrored, by the way, courtesy of OS/2, remotely for ultimate bail out if horror really should strike the complete industrial relay rack systems that run all this stuff across multiple mirrored sites, for now ..
Over 500,000 totally logged telephone transactions and complete
phone call trace records .. both incoming, outbound, cross-line
service .. and all progress operations ..
If you really do want to work with equipment such as the Rochelle products from
over in Austin, Texas, as well as things like the Motorolla professional transmitter and receiver service equipment, for RF monitoring, there is simply No Place To Hide.
I've not had the time to add IPTRACE record insertion into this for IP port and
analysis work to the ZIPLOG professional management template here. Of even Bink traffic, but it could be done to really play worse ZNITCH on whatever. There's still too much to do for the finishing touches for where I'm going for medical system personal care interfaces and service work, which at this point also has a complete HIPAA data interface to these same REAL-TIME records. And I'm finishing as to what I want to do with embedding this whole system into a Tivo-like box,one for every person in a nursing home bed .. or a jail cell .. or a lawyer's desk. To make sure there is no place to hide either for the individual or the professional.
And .. curiously .. even Bink and Max are interfaced to this whole system for a
last ditch messaging backup notice, if needed! And, what you asked about, that
Bink can do, is .. curiously .. still the starting point for what to do when you connect to the BBS here and what you see in the user log-in hits.
; --- BANNER / EMSI / BBS-INTRO SETUP ----------
; Banner Line displayed when someone calls
Banner ---> TRACING your call, please stand-by.....
Now you see how, starting back with all this in about 1983, the FidoNet game and pornography and early virus mess attempts and counterfiet Fido dog chomping
by certain others, sort of vanished here in Net 117. And why Net 117 sorta drifted away as a playground for bad-dog-users.
But CNID enablement of a modem as described above, is sure a place to start with the registers which will enable it. If you need it! And learn what else you could do with the log line output!
Sleep well; OS/2's still awake! ;)
Mike @ 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)