From: Thomas Tonino <ttonino@users.sf.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Asterisk] DTMF noise
Date: Wed, 08 Jan 2003 08:51:38 +0100 [thread overview]
Message-ID: <3E1BD88A.4080808@users.sf.net> (raw)
In-Reply-To: <D6889804-2291-11D7-901B-000393950CC2@karlsbakk.net>
Roy Sigurd Karlsbakk wrote:
> so - we DO NOT need a 'simplistic' DTMF decoder.
You need a good one. But good can be simplistic, is what I'm saying.
DTMF was designed to be easy to decode reliably. Complex doesn't automatically
mean better.
I remember reading a more specific version of the message I pointed a pointer
to, but couldn't find it back. But it came down to the devil being in the details.
It probably pays to have someone look at this with old hardware experience in
this. Telco newsgroup perhaps.
Thomas
next prev parent reply other threads:[~2003-01-08 7:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030107140012$1b66@gated-at.bofh.it>
[not found] ` <20030107150006$4896@gated-at.bofh.it>
2003-01-07 19:08 ` [Asterisk] DTMF noise Thomas Tonino
2003-01-07 22:46 ` Roy Sigurd Karlsbakk
2003-01-08 7:51 ` Thomas Tonino [this message]
2003-01-08 12:43 ` David D. Hagood
2003-01-08 13:04 ` Matti Aarnio
2003-01-08 15:49 ` Wolfgang Fritz
2003-01-08 16:30 ` Wolfgang Fritz
2003-01-08 19:48 ` Andrew McGregor
2003-01-08 22:19 ` Jamie Lokier
2003-01-09 12:51 ` David D. Hagood
2003-01-09 13:31 ` Wolfgang Fritz
2003-01-09 23:32 ` David D. Hagood
2003-01-10 6:52 ` Matti Aarnio
2003-01-10 12:42 ` David D. Hagood
2003-01-10 12:03 ` Roy Sigurd Karlsbakk
2003-01-08 20:22 ` Thomas Tonino
2003-01-09 12:42 ` David D. Hagood
2003-01-07 13:55 Roy Sigurd Karlsbakk
2003-01-07 14:49 ` [Asterisk] " Mark Spencer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E1BD88A.4080808@users.sf.net \
--to=ttonino@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox