Caller ID problem Second try with correctly formatted log files. Sorry Gert
"Dave Packham" (dpackham@darkstar.utah.edu)
Sun, 10 Jan 1999 15:08:15 -0700
>> 01/10 10:28:25 yS1 waiting for line to clear (VTIME), read:
>> 01/10 10:28:25 yS1 send: AT#CID=2[0d]
>
>Why "2"? The mgetty documentation recommends AT#CID=1. I have no idea
>what AT#CID=2 is supposed to do, it's not what I recommend, so it's your
>turn to debug problems (or explain why you did it that way so that I can
>improve the documentation).
The #CID=2 is another form of caller ID that I found on USR's page just
trying it here. When I use the CID=1 I get no different log entry here
>The modem is supposed to deliver caller ID between the first and second
>RING. It doesn't do that. (The log level is high enough so that every
>single byte received will be logged).
>
The USR page states the this modem does CID. Its an internal 33.6. Its the
model that cannot be upgraded by flash so I have to live with it.
Thanks for your time
Dave