Re: [vmeet] Audio echo

Douglas Otis <doug.mtview@gmail.com> Sat, 25 April 2009 03:20 UTC

Return-Path: <doug.mtview@gmail.com>
X-Original-To: vmeet@core3.amsl.com
Delivered-To: vmeet@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D0AE3A6920 for <vmeet@core3.amsl.com>; Fri, 24 Apr 2009 20:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level:
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NeG4+MVAkA1 for <vmeet@core3.amsl.com>; Fri, 24 Apr 2009 20:20:08 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by core3.amsl.com (Postfix) with ESMTP id 8BDCF3A68C7 for <vMeet@ietf.org>; Fri, 24 Apr 2009 20:20:08 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so1307468ana.4 for <vMeet@ietf.org>; Fri, 24 Apr 2009 20:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=OH7ayVchVzsflcOa6TuGQ7eQqQSdhqbSdc2/39LAQTA=; b=DGiioDwt1VqHnJISn5UEXUBAXuwpvLaDOSgrO9Z3zeUzTjljULPl3lF7GYWwHdqGkk yxj4M7r8rXB9V9TTqe3hTMv32EVfuQw/rH0PusV1v5t4gMV/qsFeHERfiZKk+OUq7OgC /6l9Q51NcpomDaH7JD46kVtUXzLqklBWtmOFw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=mfU3wrHt2GDAIyRRUgFF7bGk4ChkY61NWXhYG9BjOM1pzDEvR9noayjv8CUKwOF8tA dA7Zr8uXV5ViDOwPr6y76rir/X1qAJ12fhsFTTVd7yjCWHDulm96R0292pCx4NzO+xir sTIMQJ8XfTEOl458sYiHcoY990nUbzjKWgy/c=
Received: by 10.100.108.2 with SMTP id g2mr4309199anc.35.1240629687363; Fri, 24 Apr 2009 20:21:27 -0700 (PDT)
Received: from ?192.168.2.11? (64-142-13-68.dsl.static.sonic.net [64.142.13.68]) by mx.google.com with ESMTPS id c14sm4448196ana.12.2009.04.24.20.21.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 24 Apr 2009 20:21:26 -0700 (PDT)
From: Douglas Otis <doug.mtview@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <44C4C11A-1E22-4E63-B40F-4C074346119E@cs.columbia.edu>
References: <49F1FD36.4010208@bbiw.net> <A14D0D78-F418-430D-831C-96F4E132B062@gmail.com> <048201c9c520$99158700$cb409500$@net> <44C4C11A-1E22-4E63-B40F-4C074346119E@cs.columbia.edu>
Content-Type: text/plain
Date: Fri, 24 Apr 2009 20:21:39 -0700
Message-Id: <1240629699.12065.59.camel@64-142-13-68.dsl.static.sonic.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9)
Content-Transfer-Encoding: 7bit
Cc: vMeet@ietf.org, 'Dave CROCKER' <dcrocker@bbiw.net>
Subject: Re: [vmeet] Audio echo
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vmeet>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Apr 2009 03:20:09 -0000

On Fri, 2009-04-24 at 17:58 -0400, Henning Schulzrinne wrote:
>
> However, you only need these fancy boxes if you run full-duplex. If
> you mute the floor microphones when the remote caller speaks (and vice
> versa), i.e., in half-duplex mode, there can be no acoustic echo. This
> is, I think, what Doug is proposing. This is more human effort, but a 
> whole lot simpler to install.

Agreed. Even assuming the PA and the RMC were somehow closely
integrated, depending upon the location of the remote speaker, the
data-center offering the RMC services, and the location of the meeting,
transmission line effects still introduce complex and unstable delays.  

In addition, acoustic echo canceling is never perfect even when all
audio sources are fed through a common system.  These system are
expensive and difficult to configure when the goal is to allow both near
and far sides an ability to talk freely. Dealing with acoustic residuals
when both sides are talking represents a rather daunting problem. 

A manual half duplex mode ensures that those in the meeting room will be
able to ensure good audio quality and its use at a very low cost.  Also
note that the suggested low cost BTC wireless keyboard has both volume
and mute buttons to make the effort of controlling the Net-Box audio
fairly minimal.  Use of RDP protocols would eliminate passing around a
keyboard, but this would be dependent upon the network.

A wireless keyboard might be handy during network disruptions as it
would enable a meeting to continue when the hotel router gets depressed.
Slides for the meeting should also be stored in the Net-Box prior to the
start of the meeting.  While these devices also accept nearly any type
of memory stick and contain system recovery images, it may be unwise
from a security standpoint to rely on memory sticks being freely passed
around.

-Doug