Caller ID problem Second try with correctly formatted log files. Sorry Gert

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Sun, Jan 10, 1999 at 10:14:18AM -0700, Dave Packham wrote:
> I have included my log file.  I cannot get to the callerid number.  but I
> can deny callers by dialin.conf numbers.

The modem doesn't deliver any number.  So yes, if you use a dialin.conf
that doesn't permit "any caller", it will reject callers.  All of them.

Let's look at the log:

> 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).

[..]
> 01/10 10:28:40 yS1   do_makelock: lock='/var/lock/LCK..ttyS1'
> 01/10 10:28:40 yS1   lock made
> 01/10 10:28:40 yS1  wfr: waiting for ``RING''
> 01/10 10:28:40 yS1   got: [0a][0d][0a]RING[0d]
> 01/10 10:28:40 yS1   wfr: rc=0, drn=0
> 01/10 10:28:40 yS1  wfr: waiting for ``RING''
> 01/10 10:28:40 yS1   got: [0a][0d][0a]RING[0d]
> 01/10 10:28:46 yS1   wfr: rc=0, drn=0

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).

[remainder of the log file removed]

Interesting enough, I can't see any evidence that you can "deny callers
based on caller ID".  What brings you to that conclusion?  Back it by log
files, please!

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de