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

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

Here it is in minicom this is a block and copy including spaces

##start here##
RING

MESG = ..0110163.O.








                   8018090623f

RING
ATQ0V1H0
OK
##end here##

This is my cellphone numbers I have changed the first 6 digits to 5' to save
my phone bill but otherwise its right


----- Original Message -----
From: Gert Doering <gert@greenie.muc.de>
To: Dave Packham <dpackham@darkstar.utah.edu>; Gert Doering
<gert@greenie.muc.de>; <mgetty@muc.de>
Sent: Sunday, January 10, 1999 3:34 PM
Subject: Re: Caller ID problem Second try with correctly formatted log
files. Sorry Gert


>Hi,
>
>On Sun, Jan 10, 1999 at 03:08:15PM -0700, Dave Packham wrote:
>> >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.
>
>You're sure that the local Telco is actually sending CID information down
>the line?
>
>If yes, go to a terminal program, set AT#CID=1, let someone call in, and
>see whether something is printed.  If yes, try from vgetty.  If nothing is
>seen there, maybe the modem setting gets lost (there is evidence for that
>in the mailing list archives).  If that is so, come back.  First do some
>homework :-)
>
>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