[codec] #1: Application: 2.1. Point to point calls supporting transcoding?
"codec issue tracker" <trac@tools.ietf.org> Tue, 23 March 2010 17:19 UTC
Return-Path: <trac@tools.ietf.org>
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 3AB543A6B5A for <codec@core3.amsl.com>; Tue, 23 Mar 2010 10:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.87
X-Spam-Level:
X-Spam-Status: No, score=-98.87 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 LqmfNU0xS0dh for <codec@core3.amsl.com>; Tue, 23 Mar 2010 10:19:51 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id AC6293A67D6 for <codec@ietf.org>; Tue, 23 Mar 2010 10:19:50 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nu7lw-0002Iz-P4; Tue, 23 Mar 2010 10:20:08 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: codec issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: hoene@uni-tuebingen.de
X-Trac-Project: codec
Date: Tue, 23 Mar 2010 17:20:08 -0000
X-URL: http://tools.ietf.org/codec/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/codec/trac/ticket/1
Message-ID: <062.4b6a3862c443b2d8917e027f2267f4d2@tools.ietf.org>
X-Trac-Ticket-ID: 1
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: hoene@uni-tuebingen.de, codec@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Tue, 23 Mar 2010 10:22:55 -0700
Cc: codec@ietf.org
Subject: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Tue, 23 Mar 2010 17:19:52 -0000
#1: Application: 2.1. Point to point calls supporting transcoding? ------------------------------------+--------------------------------------- Reporter: hoene@… | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: requirements | Version: Severity: Active WG Document | Keywords: ------------------------------------+--------------------------------------- Question: Shall the point-to-point call support transcoding? If not, please add something like "This scenario does not include the use case of using a VoIP-PSTN gateway to connected to legacy telephone systems. In those cases, the gateway would make an audio conversion from broadband Internet voice to the frugal 1930’s 3.1 kHz audio bandwidth. Interconnections to the PSTN will most likely stick with its legacy codecs to avoid transcoding." -- Ticket URL: <http://tools.ietf.org/wg/codec/trac/ticket/1> codec <http://tools.ietf.org/codec/>
- [codec] #1: Application: 2.1. Point to point call… codec issue tracker
- Re: [codec] #1: Application: 2.1. Point to point … James Rafferty
- Re: [codec] #1: Application: 2.1. Point to point … Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … James Rafferty
- Re: [codec] #1: Application: 2.1. Point to point … Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … James Rafferty
- Re: [codec] #1: Application: 2.1. Point to point … Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … James Rafferty
- Re: [codec] #1: Application: 2.1. Point to point … stephen botzko
- Re: [codec] #1: Application: 2.1. Point to point … James Rafferty
- Re: [codec] #1: Application: 2.1. Point to point … Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … Marc Petit-Huguenin
- Re: [codec] #1: Application: 2.1. Point to point … Michael Knappe
- Re: [codec] #1: Application: 2.1. Point to point … Marc Petit-Huguenin
- Re: [codec] #1: Application: 2.1. Point to point … stephen botzko
- Re: [codec] #1: Application: 2.1. Point to point … Marc Petit-Huguenin
- Re: [codec] #1: Application: 2.1. Point to point … Michael Knappe
- Re: [codec] #1: Application: 2.1. Point to point … Dr. Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … codec issue tracker
- Re: [codec] #1: Application: 2.1. Point to point … stephen botzko
- Re: [codec] #1: Application: 2.1. Point to point … Christian Hoene
- Re: [codec] #1: Application: 2.1. Point to point … stephen botzko
- Re: [codec] #1: Application: 2.1. Point to point … Koen Vos
- Re: [codec] #1: Point to point calls supporting t… codec issue tracker