what do i need to do for CID to the logfile?

Discussion:

(too old to reply)

spiderman

2007-09-13 00:13:37 UTC

09/12 18:40:44 yS2 vgetty: experimental test release 0.9.32 / with
duplex patch
09/12 18:40:44 yS2 mgetty: interim release 1.1.35-Feb22
09/12 18:40:44 yS2 reading generic configuration from config file /usr/
local/etc/mgetty+sendfax/voice.conf
09/12 18:40:44 yS2 reading program vgetty configuration from config
file /usr/local/etc/mgetty+sendfax/voice.conf
09/12 18:40:44 yS2 reading port ttyS2 configuration from config file /
usr/local/etc/mgetty+sendfax/voice.conf
09/12 18:40:44 yS2 check for lockfiles
09/12 18:40:44 yS2 locking the line
09/12 18:40:44 yS2 can't get group 'modem': Success
09/12 18:40:45 yS2 lowering DTR to reset Modem
09/12 18:40:46 yS2 send: \dATQ0V1H0[0d]
09/12 18:40:46 yS2 waiting for ``OK'' ** found **
09/12 18:40:46 yS2 send: ATS0=0Q0&D3#cid=1&C1[0d]
09/12 18:40:46 yS2 waiting for ``OK'' ** found **
09/12 18:40:46 yS2 mdm_send: 'ATI'
09/12 18:40:46 yS2 USR Courier/Sportster 56k detected
09/12 18:40:46 yS2 mdm_send: 'ATI3'
09/12 18:40:46 yS2 additional info: 'U.S. Robotics 56K Voice INT V5.19.1'
09/12 18:40:46 yS2 modem quirks: 0080
09/12 18:40:46 yS2 mdm_send: 'AT+FCLASS=2.0' -> OK
09/12 18:40:46 yS2 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
09/12 18:40:46 yS2 mdm_send: 'AT+FBO=1' -> OK
09/12 18:40:46 yS2 mdm_send: 'AT+FNR=1,1,1,0' -> OK
09/12 18:40:46 yS2 mdm_send: 'AT+FLI="THEREALNUMBER"' -> OK
09/12 18:40:47 yS2 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK
09/12 18:40:47 yS2 detecting voice modem type
09/12 18:40:48 yS2 US Robotics detected
09/12 18:40:49 yS2 US Robotics voice modem
09/12 18:40:49 yS2 This is a driver beta version. V0.4.b3
09/12 18:40:49 yS2 VTD setup successful
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive
09/12 19:40:48 yS2 mdm_send: 'AT' -> OK
09/12 19:40:49 yS2 waiting...

Gert Doering

2007-09-13 06:29:15 UTC

Permalink

Hi,

"let the phone RING"?

You're showing the initialization part of the log (which is good) but
not the part where a call is actually coming in...

Post by spiderman
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive
09/12 19:40:48 yS2 mdm_send: 'AT' -> OK
09/12 19:40:49 yS2 waiting...

... which would be right after this...

So we don't know what your modem is sending to mgetty (if anything)...

Don't forget to set "rings 2" in mgetty.conf

gert

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

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

spiderman

2007-09-13 15:41:49 UTC

Permalink

Thanks for the reply.

The posted log was right after a call came in.
I had vgetty setup and logging cid on the last slackware11, now 12, with
the same modem. I've compared the old .confs with the new. The only
difference is in mgetty.conf..

init-chat "" \d\d\d+++\d\d\dAT+FCLASS=8 OK
post-init-chat "" AT#CID=1 OK

So I thought maybe the #cid was getting reset and checked with minicom,
it was still 1.
I set rings 2, but I have a feeling that's not going to do it.
Do you have any other ideas?

Post by Gert Doering
Hi,
"let the phone RING"?
You're showing the initialization part of the log (which is good) but
not the part where a call is actually coming in...

Post by spiderman
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

... which would be right after this...
So we don't know what your modem is sending to mgetty (if anything)...
Don't forget to set "rings 2" in mgetty.conf
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/

~gert/

Post by Gert Doering
Gert Doering - Munich, Germany

spiderman

2007-09-13 15:59:17 UTC

Permalink

Oh darn silly me. After I posted that, a flash of inspiration!
The jacks were plugged in the wrong slots, I always thought that didn't
matter.

Great program mr. Doering, thanks again.

Post by spiderman
Thanks for the reply.
The posted log was right after a call came in. I had vgetty setup and
logging cid on the last slackware11, now 12, with the same modem. I've
compared the old .confs with the new. The only difference is in
mgetty.conf..
init-chat "" \d\d\d+++\d\d\dAT+FCLASS=8 OK post-init-chat "" AT#CID=1 OK
So I thought maybe the #cid was getting reset and checked with minicom,
it was still 1.
I set rings 2, but I have a feeling that's not going to do it. Do you
have any other ideas?

Post by Gert Doering
Hi,
"let the phone RING"?
You're showing the initialization part of the log (which is good) but
not the part where a call is actually coming in...

Post by spiderman
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

www.muc.de/

Post by spiderman
~gert/

Post by Gert Doering
Gert Doering - Munich, Germany

spiderman

2007-09-13 22:11:23 UTC

Permalink

nope, still no cid.

Oh darn silly me. After I posted that, a flash of inspiration! The jacks
were plugged in the wrong slots, I always thought that didn't matter.
Great program mr. Doering, thanks again.

Post by Gert Doering
Hi,
"let the phone RING"?
You're showing the initialization part of the log (which is good) but
not the part where a call is actually coming in...

Post by spiderman
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

www.muc.de/

Post by spiderman
~gert/

Post by Gert Doering
Gert Doering - Munich, Germany

Gert Doering

2007-09-14 07:19:19 UTC

Permalink

Hi,

Post by spiderman
nope, still no cid.

You've still not sent the relevant part of the log (after the "waiting..."
part, and before the next version number).

gert

Stroller

2007-09-13 18:41:33 UTC

Permalink

Post by spiderman
09/12 18:40:44 yS2 vgetty: experimental test release 0.9.32 / with
duplex patch
09/12 18:40:44 yS2 mgetty: interim release 1.1.35-Feb22
...
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive
09/12 19:40:48 yS2 mdm_send: 'AT' -> OK
09/12 19:40:49 yS2 waiting...

09/09 19:39:01 yS0 waiting...
09/09 20:14:28 yS0 wfr: waiting for ``RING''
09/09 20:14:28 yS0 wfr: waiting for ``RING''
09/09 20:14:28 yS0 wfr: waiting for ``RING''
09/09 20:14:30 yS0 wfr: waiting for ``RING''
09/09 20:14:33 yS0 wfr: waiting for ``RING''
09/09 20:14:36 yS0 reading ring_type ring configuration from config
file /etc/mgetty+sendfax/voice.conf
09/09 20:14:41 yS0 playing voice file /var/spool/voice/messages/
standard.rmd
09/09 20:14:57 yS0 recording voice file /var/spool/voice/incoming/
v-30611-1189365280-01908502901.rmd
09/09 20:15:46 yS0 vgetty: <DLE> <ETX> received
09/09 20:15:48 yS0 closing voice modem device
09/09 20:15:48 ##### message keep, length=00:00:49, name='',
caller=01908502901, dev=ttyS0, pid=30611
09/09 20:15:48 yS0 vgetty: Executing shell script /usr/local/bin/
voice2email.sh with shell /bin/bash

A modem which supports CID?
(Here in the UK few do, as caller ID here is sent differently than it
is in the US).

Stroller.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

spiderman

2007-09-13 23:40:58 UTC

Permalink

That's nice. All I get is waiting..
09/13 11:52:36 yS2 waiting...
09/13 12:52:34 yS2 checking if modem is still alive
09/13 12:52:34 yS2 mdm_send: 'AT' -> OK
09/13 12:52:34 yS2 waiting...
09/13 13:52:33 yS2 checking if modem is still alive
09/13 13:52:33 yS2 mdm_send: 'AT' -> OK
09/13 13:52:33 yS2 waiting...

Throughout rings.

no RING messages

#CID=n
n=0 Caller ID Off
n=1 Formatted Caller ID
n=2 Unformatted Caller ID

Post by Stroller

Post by spiderman
09/12 18:40:44 yS2 vgetty: experimental test release 0.9.32 / with
duplex patch
09/12 18:40:44 yS2 mgetty: interim release 1.1.35-Feb22 ...
09/12 18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

09/09 19:39:01 yS0 waiting...
waiting for ``RING'' 09/09 20:14:28 yS0 wfr: waiting for ``RING'' 09/09
20:14:30 yS0 wfr: waiting for ``RING'' 09/09 20:14:33 yS0 wfr: waiting
for ``RING'' 09/09 20:14:36 yS0 reading ring_type ring configuration
from config file /etc/mgetty+sendfax/voice.conf
09/09 20:14:41 yS0 playing voice file /var/spool/voice/messages/
standard.rmd
09/09 20:14:57 yS0 recording voice file /var/spool/voice/incoming/
v-30611-1189365280-01908502901.rmd
09/09 20:15:46 yS0 vgetty: <DLE> <ETX> received 09/09 20:15:48 yS0
closing voice modem device 09/09 20:15:48 ##### message keep,
length=00:00:49, name='', caller=01908502901, dev=ttyS0, pid=30611 09/09
20:15:48 yS0 vgetty: Executing shell script /usr/local/bin/
voice2email.sh with shell /bin/bash
A modem which supports CID?
(Here in the UK few do, as caller ID here is sent differently than it is
in the US).
Stroller.

spiderman

2007-09-14 03:55:57 UTC

Permalink

i know everyone is dying to know what's going on.
my atx was defaulting to 0. i've set it to default to 4 now.
hopefully that'll do the trick. nobody ever calls me so it might take
awhile to find out.

Post by spiderman
That's nice. All I get is waiting..
09/13 11:52:36 yS2 waiting...
09/13 12:52:34 yS2 checking if modem is still alive 09/13 12:52:34 yS2
mdm_send: 'AT' -> OK 09/13 12:52:34 yS2 waiting...
09/13 13:52:33 yS2 checking if modem is still alive 09/13 13:52:33 yS2
mdm_send: 'AT' -> OK 09/13 13:52:33 yS2 waiting...
Throughout rings.
no RING messages
#CID=n
n=0 Caller ID Off
n=1 Formatted Caller ID
n=2 Unformatted Caller ID

Post by Stroller

Post by spiderman
09/12 18:40:44 yS2 vgetty: experimental test release 0.9.32 / with
duplex patch
09/12 18:40:44 yS2 mgetty: interim release 1.1.35-Feb22 ... 09/12
18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

09/09 19:39:01 yS0 waiting...
waiting for ``RING'' 09/09 20:14:28 yS0 wfr: waiting for ``RING''
waiting for ``RING'' 09/09 20:14:36 yS0 reading ring_type ring
configuration from config file /etc/mgetty+sendfax/voice.conf 09/09
20:14:41 yS0 playing voice file /var/spool/voice/messages/
standard.rmd
09/09 20:14:57 yS0 recording voice file /var/spool/voice/incoming/
v-30611-1189365280-01908502901.rmd
09/09 20:15:46 yS0 vgetty: <DLE> <ETX> received 09/09 20:15:48 yS0
closing voice modem device 09/09 20:15:48 ##### message keep,
length=00:00:49, name='', caller=01908502901, dev=ttyS0, pid=30611
09/09 20:15:48 yS0 vgetty: Executing shell script /usr/local/bin/
voice2email.sh with shell /bin/bash
A modem which supports CID?
(Here in the UK few do, as caller ID here is sent differently than it
is in the US).
Stroller.

spiderman

2007-09-21 04:11:13 UTC

Permalink

so strange. the modem is reporting rings now that i've moved it to ttyS0.
disabled the onboard serial ports.

or maybe it just decided to start working again-

i know everyone is dying to know what's going on. my atx was defaulting
to 0. i've set it to default to 4 now. hopefully that'll do the trick.
nobody ever calls me so it might take awhile to find out.

Post by spiderman
That's nice. All I get is waiting..
09/13 11:52:36 yS2 waiting...
09/13 12:52:34 yS2 checking if modem is still alive 09/13 12:52:34 yS2
mdm_send: 'AT' -> OK 09/13 12:52:34 yS2 waiting... 09/13 13:52:33 yS2
checking if modem is still alive 09/13 13:52:33 yS2 mdm_send: 'AT' ->
OK 09/13 13:52:33 yS2 waiting...
Throughout rings.
no RING messages
#CID=n
n=0 Caller ID Off
n=1 Formatted Caller ID
n=2 Unformatted Caller ID

Post by Stroller

Post by spiderman
09/12 18:40:44 yS2 vgetty: experimental test release 0.9.32 / with
duplex patch
09/12 18:40:44 yS2 mgetty: interim release 1.1.35-Feb22 ... 09/12
18:40:50 yS2 waiting...
09/12 19:40:48 yS2 checking if modem is still alive 09/12 19:40:48 yS2
mdm_send: 'AT' -> OK 09/12 19:40:49 yS2 waiting...

Gert Doering

2007-09-14 07:20:27 UTC

Permalink

Hi,

Post by spiderman
That's nice. All I get is waiting..
09/13 11:52:36 yS2 waiting...
09/13 12:52:34 yS2 checking if modem is still alive
09/13 12:52:34 yS2 mdm_send: 'AT' -> OK
09/13 12:52:34 yS2 waiting...
09/13 13:52:33 yS2 checking if modem is still alive
09/13 13:52:33 yS2 mdm_send: 'AT' -> OK
09/13 13:52:33 yS2 waiting...
Throughout rings.
no RING messages

Now that's the interesting part: your modem does not send anything to
the host when the phone is RINGing - the problem is much more serious
than "no caller ID".

Check the wiring to the modem, and the modem itself.

gert