failure notice (fwd)
Ard van Breemen (ard@cstmel.hobby.nl)
Mon, 21 Apr 1997 19:33:56 +0200 (MET DST)
Do I still have to sent it twice? How does it work?
---------- Forwarded message ----------
Date: 19 Apr 1997 10:50:57 -0000
From: MAILER-DAEMON@ns.crynwr.com
To: ard@cstmel.hobby.nl
Subject: failure notice
Hi. This is the qmail-send program at ns.crynwr.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<mgetty@crynwr.com>:
Hi! We have a policy on the mgetty mailing list that anyone can post to
the list, but your first message gets bounced back to you. This is done
to prevent spammers from getting through. Please resubmit your message
(included below) and it will get posted to the list. Oh, and while you're
doing that, please remember the following:
o This is an English-language mailing list.
o If you're submitting a bug report, you should also include the
log file output along with a description of the problem.
-russ <nelson@crynwr.com>, maintainer of the mgetty mailing list..
--- Below this line is a copy of the message.
Return-Path: <ard@cstmel.hobby.nl>
Received: (qmail 19711 invoked from network); 19 Apr 1997 10:50:54 -0000
Received: from vogon.muc.de (root@193.174.4.4)
by ns.crynwr.com with SMTP; 19 Apr 1997 10:50:53 -0000
Received: from hgatenl.hobby.nl ([193.78.42.1]) by vogon.muc.de with SMTP id <48703-175>; Sat, 19 Apr 1997 12:50:35 +0100
Received: by hgatenl.hobby.nl (Smail3.1.29.1 #21)
id m0wIYBJ-000QyZC; Sat, 19 Apr 97 13:19 MET DST
Received: from dec1.cstmel.hobby.nl by cstmel.hobby.nl.hobby.nl (5.59/25-eef)
id AA05119; Mon, 7 Apr 97 17:48:55 EDT
Date: Thu, 17 Apr 1997 21:26:42 +0200 (MET DST)
From: Ard van Breemen <ard@cstmel.hobby.nl>
To: "wisam@egal.jinjin.co.kr" <wisam@egal.jinjin.co.kr>
Cc: mgetty@muc.de
Subject: Re: Rockwell will not stop recording.
In-Reply-To: <33568590.2A2B@egal.jinjin.co.kr>
Message-Id: <Pine.LNX.3.95.970417211801.27141A-100000@dec1.cstmel.hobby.nl>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi,
Sorry for this.
It worked for the previous mgetty driver interface, and now it still works
for my tower-32 system. It uses USE_READ because it does not have poll and
select. So USE_READ does work, but you have to know what it means: the
first character received from the modem get's eaten by vgetty, so dialout
does have to care about that.
I recently planned switching completely to linux (power savings, my tower
costs me about $300,- a year..., and better I/O performance... not). But
I'm still on the way. I've discovered vgetty does not work right ( Yes, it
does not stop recording...), and planning to resolve this. It might be the
solution that during that you use USE_READ, or an older version of vgetty
(pre new driver interface release...). First I have to put in a faster
processor to cope with 38k4... under, well, no load at all... (1.3.39 did
it, so why not 2.0.18)
RegARDs
Somebody wrote:
> I am programming voice/fax answering application with vgetty.
> I have trouble in stopping voice recording in Rockwell modem.
>
> My environment is as follows
> OS : FreeBSD UNIX on IBM compatible PC
> Modem : RCV336ACF/SP based internal modem on com4
>
> The log of conversation is as follows.
> ---------------------log start ---------------------------------------
> to modem : ATQ0V1H0
> to modem : ATS0=0Q0&D3&C1
> to modem : AT#CLS=8
> to modem : AT#VSP=70
> to modem : AT#VSD=0
> to modem : AT#VTD=3F,3F,3F
> to modem : AT#BDR=16
> to modem : AT#VSS=1
> to modem : AT&K3
>
> comment : playing voice
> to modem : AT#VBS=4
> to modem : AT&K3
> to modem : AT#VLS=0
> to modem : AT#VTX
> playing voice and stopped by a dtmf code
> ............
>
> comment : recording voice
> to modem : AT#VBS=4
> to modem : AT#VTS=[933,0,15]
> to modem : AT&K3
> to modem : ATS30=20
> to modem : AT#BDR=16
> to modem : AT#VRX
> recorded byte message : write<DATA 280 bytes>
> recorded byte message : write<DATA 294 bytes>
> recorded byte message : write<DATA 293 bytes>
> recorded byte message : write<DATA 294 bytes>
> recorded byte message : write<DATA 294 bytes>
> recorded byte message : write<DATA 279 bytes>
> recorded byte message : write<DATA 266 bytes>
> recorded byte message : write<DATA 280 bytes>
> recorded byte message : write<DATA 266 bytes>
> recorded byte message : write<DATA 294 bytes>
> from modem : <DLE> <q>
> to modem : !
> to modem : AT
> from modem : e[ab][b2]hL[c6][8a]h[86][fa]{[86]qk[ca]
> F8[a8][d8][a6][a8] * j[a5][d6]x[9b][17]
> [88][a8][94]hV[99]F[d0]I[19][98]w[97]w
> ig]V[e1]WyxIS[cd][98]7[88]U[99][d8]U{9
> [a5]'[99][e9]vY[c6]W[
> 7f]e[87][ca][85][86][c7]}9[95][bb][93]z
> .....endless garvage and won't go to command mode by any AT command....
> -------------------- log end -------------------------------------
> Line is hanged up so I must power it off.
.