Vgetty reports: Huh? Junk in the line?

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

First of all thank you very much for your prompt reply. I am really very
impressed with the "Linux community support" :-))) .

Marc SCHAEFER wrote:

> Giovanni Biscuolo <giovanni.biscuolo@libero.it> wrote:
> > My modem only answer once, ignoring all following calls, with the "OH"
> > led blinking.
>
> Are you sure noone else is using the line (no dial-out) ?
>

Yes (almost). I am the "sysadmin" of a standalone home workstation: one user at a time.
To be sure noone means process I'm going to test vgetty again checking for it.

>
> > Please help me for I am not able to use vgetty since Sept. 1999 and it
>
> Has this worked before ? If yes, what version of vgetty or mgetty ?
>

Yes, it "worked" since Dec. 1999 (mgetty 1.1.21 RedHat 6.0 package)
with other problem: often vgetty stopped recording
a voice message before the caller stopped to talk. Maybe there are some messages (and
related logfiles) in the mailing-list archive.

I looked at the old log file, it was:
11/24 12:29:22 yS0    US Robotics: <DLE> <i>
11/24 12:29:22 yS0    vgetty: queued event DIAL_TONE at position 0006
11/24 12:29:22 yS0    vgetty: unqueued event DIAL_TONE at position 0006
11/24 12:29:22 yS0    vgetty: voice_handle_event got event DIAL_TONE with data <e>
11/24 12:29:22 yS0    vgetty: <STOP RECORDING>

Now is:
01/14 12:13:33 yS0    US Robotics: AT#VRX
01/14 12:13:33 yS0    US Robotics: CONNECT
01/14 12:13:41 yS0    US Robotics: <DLE> <i>
01/14 12:13:41 yS0    USR_handle_dle: Ignoring <DLE> <i> because the modem is RECORDING.

Maybe this is the patch I needed: ignore DIAL_TONE while recording: thank you !!!  ;-)

> > 01/14 12:13:58 yS0    US Robotics: AT
> > 01/14 12:13:58 yS0    US Robotics: OK
> > 01/14 12:13:58 yS0   vgetty: Restoring signal handlers
> > 01/14 12:13:58 yS0   waiting for line to clear (VTIME), read:
> > 01/14 12:13:58 yS0   removing lock file
> > 01/14 12:13:58 yS0  waiting...
>
> Everything fine.
>

Well !

> > 01/14 12:24:34 yS0    select returned 1
>
> Ah, something to read on the serial line.

This is the second voice call, it was me testing the program from a pubblic telephone.

> > 01/14 12:24:34 yS0   checking lockfiles, locking the line
> > 01/14 12:24:34 yS0   makelock(ttyS0) called
> > 01/14 12:24:34 yS0   do_makelock: lock='/var/lock/LCK..ttyS0'
> > 01/14 12:24:34 yS0   lock made
>
> noone is doing a *proper* dialout.

This means that no other process is "using" the modem, too. Is it?

> > 01/14 12:24:34 yS0  wfr: waiting for ``RING''
> > 01/14 12:24:34 yS0   got: [0a]CS[f3]CS[f3]CS[f3]
>
> get crap instead of ring

Ooops ...
No rings, no reason to answer :-(

> > 01/14 12:24:44 yS0  mdm_read_byte: read returned -1: Interrupted system call
>
> 10 seconds later no more information.
>

I stopped calling (from outside).

> > 01/14 12:24:54 yS0   got: [0a]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]CS[f3]
>
> same scenario.
>

Not the same, unfortunately.  I don't remember well, maybe I was doing the third test call.
The scenario is non the same because the log file stopped recording events at 12:24:54 (same
time).
What does it means?
Vgetty should respawn because I use this command in /etc/inittab:
vg:2345:respawn:/bin/nice --6 /usr/sbin/vgetty ttyS0.