I'm not sure when this problem first came up, but I noticed that for some
reason my caller ID is doing something rather odd. Here's something from a
log file:
+ 09 Oct 04:31:47 BINK begin, BinkleyTerm Version 2.60 -uSoft8.0
# 09 Oct 07:18:01 BINK Ring
# 09 Oct 07:18:03 BINK Date = 1009
# 09 Oct 07:18:03 BINK Time = 0720
# 09 Oct 07:18:03 BINK Name = Devries Gary
# 09 Oct 07:18:03 BINK Mesg = 030737383332363830
# 09 Oct 07:18:17 BINK Connect 28800/Arq
This all looks fine for a Canadian caller ID sequence (the "hex" phone number
display). But the number is show as being a "MESG" not a "NMBR".
For the last little while I noticed that a utility I use for logging caller
ID numbers was reporting "error" when a call came in. I finally had time to
try and figure out what the problem was, and this is about as close to what I
can determine is causing the problem. I believe the program is expecting a
NMBR message, like I used to get.... but not anymore.
A friend of mine works for the phone company, and he doesn't think they
changed anything... but he's going to do some checking. And I've also
recently (beginning of the month) deleted my binkley log file. So I can't
even figure out when this started.
If there's another sysop in Net140 with caller ID, can they check what's
being reported? If someone from Supra's reading... is this a possible bug?
I'm not using the latest flash... which I'll try upgrading too tonight...
--- FMail/386 1.02
---------------
* Origin: Hi-Res BBS (1:140/111)
|