DTMF is being cranky for me (fwd)
Fuzzy (fuzzy@ns.asarian.org)
Tue, 2 Jun 1998 16:20:27 +0200
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--1120836768-311023436-896796428=:28430
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.3.96.980602100859.28430F@ns.ASARian.org>
currently using Pine 3.96 (linux kernel 1.2.13, slackware 3.0.0,
PGP 2.6.2 USA version).
is saying this is a non-text PGP attachment. if its meant to be
'signed' then its not showing up as signed/ascii text, but signed and
encrypted. meaning that PGP has to process the file to to make it
readable.
when I tried to extract the 'attachment' pine reported,
[Message 49 has only one part (the message body), and no attachments.]
extracting that gave me the following.... (see correctly signed email
below)... so it appears that pine 3.96 is 'confused'. this is strange
as it usually presents ascii-armored digitally signatures, such as
yours exactly as shown below. pine 3.96 can be taught how to call lynx
as a helper app for html attachments, we figure there must be some way
to convince it to correctly display this form too.
we are currently using PGP 2.6.2 usa version, if that makes a
difference. it appears to be pine's (MUA) error, its misinterpreting
what its seeing. any ideas as to how to work around it?
Fuzzy
Sys Admin, ASARian.org
cut/paste of screen pine shows me:
PINE 3.96 MESSAGE TEXT Folder: INBOX Message 49 of 114 ALL NEW
Date: Tue, 2 Jun 1998 09:54:34 +0200
From: Marc Eberhard <marc@poseidon.thphy.uni-duesseldorf.de>
To: Gert Doering <gert@greenie.muc.de>
Cc: mgetty@muc.de
Subject: Re: DTMF is being cranky for me
[Part 1, Application/PGP 1.8KB]
[Cannot display this part. Press "V" then "S" to save in a file]
output of pine's extract attachment screen:
-----BEGIN PGP SIGNED MESSAGE-----
Hi!
Gert Doering wrote:
> Marc Eberhard wrote:
> > > 05/28 17:39:15 yS0 voice command: 'AT+VTS=[1320,0,1]' -> ''
> > > 05/28 17:39:15 yS0 voice command: '' -> 'OK'
> > > 05/28 17:39:15 yS0 vgetty: Modem returned ERROR
>
> What I do not fully understand is what the "OK" is doing here? Could you
> explain the two "voice command" lines to me?
>
> It's sending "AT+VTS=...", this is clear to me. And then nothing ('')?
>
> Then it sends nothing ('') and gets back OK (-> 'OK')? Or how do I have to
> read this?
Look at the source code:
int IS_101_beep(int frequency, int length)
{
char buffer[VOICE_BUF_LEN];
int true_length = length / voice_modem->beep_timeunit;
reset_watchdog();
sprintf(buffer, voice_modem->beep_cmnd, frequency, true_length);
if (voice_command(buffer, "") != OK)
return(FAIL);
delay(((length - 1000) > 0) ? (length - 1000) : 0);
if ((voice_command("", voice_modem->beep_answr) & VMA_USER) != VMA_USER)
return(FAIL);
return(OK);
}
The reason for splitting the command and the answer into two commands is,
that a long beep would otherwise produce a timeout while waiting for the OK
response.
Bye,
Marc
_______________________________________________________________________________
Email: Marc.Eberhard@Poseidon.ThPhy.Uni-Duesseldorf.DE
WWW: http://Poseidon.ThPhy.Uni-Duesseldorf.DE/~marc/
PGP: http://Poseidon.ThPhy.Uni-Duesseldorf.DE/~marc/Marc_PGP.key
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBNXOvtjR1rYTfG0TdAQGg4wP/epr/hJVhhLV5fzGlyZifrEtkmpgNscjE
IgZn/ITjrxh1mckMLZzGcAaAZiE8TpPSFjd0w3A2ANWBlanKrpiQJJ0/DnTxnzf3
8fS2WTfvLFIDH7AHbCcYD5/SnUWGKi8CSdmMnkpXEZ7tRJNx0lrXOdiIdn9zt/t1
tr7RS+qbmao=
=6GAd
-----END PGP SIGNATURE-----
--1120836768-311023436-896796428=:28430
Content-Type: APPLICATION/PGP; FORMAT=text; X-ACTION=sign
Content-ID: <Pine.LNX.3.96.980602100124.28430D@ns.ASARian.org>
Content-Description:
-----BEGIN PGP SIGNED MESSAGE-----
Hi!
Gert Doering wrote:
> Marc Eberhard wrote:
> > > 05/28 17:39:15 yS0 voice command: 'AT+VTS=[1320,0,1]' -> ''
> > > 05/28 17:39:15 yS0 voice command: '' -> 'OK'
> > > 05/28 17:39:15 yS0 vgetty: Modem returned ERROR
>
> What I do not fully understand is what the "OK" is doing here? Could you
> explain the two "voice command" lines to me?
>
> It's sending "AT+VTS=...", this is clear to me. And then nothing ('')?
>
> Then it sends nothing ('') and gets back OK (-> 'OK')? Or how do I have to
> read this?
Look at the source code:
int IS_101_beep(int frequency, int length)
{
char buffer[VOICE_BUF_LEN];
int true_length = length / voice_modem->beep_timeunit;
reset_watchdog();
sprintf(buffer, voice_modem->beep_cmnd, frequency, true_length);
if (voice_command(buffer, "") != OK)
return(FAIL);
delay(((length - 1000) > 0) ? (length - 1000) : 0);
if ((voice_command("", voice_modem->beep_answr) & VMA_USER) != VMA_USER)
return(FAIL);
return(OK);
}
The reason for splitting the command and the answer into two commands is,
that a long beep would otherwise produce a timeout while waiting for the OK
response.
Bye,
Marc
_______________________________________________________________________________
Email: Marc.Eberhard@Poseidon.ThPhy.Uni-Duesseldorf.DE
WWW: http://Poseidon.ThPhy.Uni-Duesseldorf.DE/~marc/
PGP: http://Poseidon.ThPhy.Uni-Duesseldorf.DE/~marc/Marc_PGP.key
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBNXOvtjR1rYTfG0TdAQGg4wP/epr/hJVhhLV5fzGlyZifrEtkmpgNscjE
IgZn/ITjrxh1mckMLZzGcAaAZiE8TpPSFjd0w3A2ANWBlanKrpiQJJ0/DnTxnzf3
8fS2WTfvLFIDH7AHbCcYD5/SnUWGKi8CSdmMnkpXEZ7tRJNx0lrXOdiIdn9zt/t1
tr7RS+qbmao=
=6GAd
-----END PGP SIGNATURE-----
--1120836768-311023436-896796428=:28430--