Re: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?

stephen botzko <stephen.botzko@gmail.com> Wed, 24 March 2010 21:21 UTC

Return-Path: <stephen.botzko@gmail.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F5F93A6DC0 for <codec@core3.amsl.com>; Wed, 24 Mar 2010 14:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 GeiVMrO-WFlM for <codec@core3.amsl.com>; Wed, 24 Mar 2010 14:21:44 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 34F713A6BE0 for <codec@ietf.org>; Wed, 24 Mar 2010 14:21:44 -0700 (PDT)
Received: by pwi10 with SMTP id 10so4345115pwi.31 for <codec@ietf.org>; Wed, 24 Mar 2010 14:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=93DXxacJAqO8HR6gGV8ffhtjhS/OZRlBl1BBx65jAlA=; b=nwU3ENPkljIL1QdqpEntO92PURlBxQPYqqzVoxgiYzifRtbjdO6ocjsoGCxjqVdPZV dBjQmM+qkCczPSD+Uwg8aShF/2QS4Y/Yv2o6npJMmp12SdRiegOmo5vx8iAkISf+nwxg CF34H1Cv1/wPtRm6O02zyLIVB/xRhrvxteBeg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cw47ZCtV30sytYuM4pgQ6eyyuCSpnuDl5k8LEvDOng/zQUmb4T+fvlGpsvNEFPMMxu 8VTJkHcczpWW8aTwMAwrYaHyri555id0IlctLM7LuNyUrk830o7urLnJJfSCGtcdg8Kf JXYIZhRdz5TYKOWPaptxv7MI5tA3KrPRqILz4=
MIME-Version: 1.0
Received: by 10.142.56.17 with SMTP id e17mr3946911wfa.12.1269465722481; Wed, 24 Mar 2010 14:22:02 -0700 (PDT)
In-Reply-To: <617DF0128820F9458AC39149A627EE6C01A294822A@MBX.dialogic.com>
References: <062.4b6a3862c443b2d8917e027f2267f4d2@tools.ietf.org> <617DF0128820F9458AC39149A627EE6C01A2947C57@MBX.dialogic.com> <000701cacad3$4b99c7c0$e2cd5740$@de> <617DF0128820F9458AC39149A627EE6C01A2947C85@MBX.dialogic.com> <000501cacb6c$37c4a0a0$a74de1e0$@de> <617DF0128820F9458AC39149A627EE6C01A2948104@MBX.dialogic.com> <001501cacbd2$d8120230$88360690$@de> <617DF0128820F9458AC39149A627EE6C01A294822A@MBX.dialogic.com>
Date: Wed, 24 Mar 2010 14:22:01 -0700
Message-ID: <6e9223711003241422u6b0348f5r4e249faf1724c778@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: James Rafferty <James.Rafferty@dialogic.com>
Content-Type: multipart/alternative; boundary="001636b2bcbb7182b90482928585"
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 21:21:45 -0000

Seems to me that there are two cases here - single gateway, and double
gateway.:In the double gateway case, Endpoint A connects to Endpoint B via a
gateway pair using PSTN.  The audio is converted to G.711 narrowband by the
first gateway, and back to the internet codec by the second.  The best
quality that can result is G.711, and the acoustic bandwidth is also limited
to narrowband, even though both endpoints can not see the G.711 hop.  Users
may have other expectations, but they cannot be met.

In any event, measuring the tandeming quality performance of this codec with
all other standard or popular) codecs would be a very tedious exercise, and
IMHO not practical.   We'd have to pick one or two codecs and let it go at
that.

Stephen Botzko



On Wed, Mar 24, 2010 at 1:59 PM, James Rafferty <James.Rafferty@dialogic.com
> wrote:

> Hi Christian,
>
> See below (JR).
>
> James
>
> -----Original Message-----
> From: Christian Hoene [mailto:hoene@uni-tuebingen.de]
> Sent: Wednesday, March 24, 2010 9:23 PM
> To: James Rafferty; codec@ietf.org
> Subject: RE: [codec] #1: Application: 2.1. Point to point calls supporting
> transcoding?
>
> Hi James,
>
> >-----Original Message-----
> >From: James Rafferty [mailto:James.Rafferty@dialogic.com]
> ...
> >Vendors of products on these network edges will take the steps needed to
> get endpoints to communicate
> >(as driven by their service provider customers), even if it requires a
> codec change to complete the
> >call.
>
> So, the main requirement in these cases is the interoperability.
> Conversational quality is of lesser importance.
> Thus, we need not particular quality requirements beside that it works OK?
>
> JR - An ability to interop is the first consideration and quality is still
> important; the customer will expect (whether reasonable or not) better than
> PSTN quality if wideband codecs are being used by both endpoints.
>
> Christian
>
> >
> >James
> >
> <snip>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
>