IETF Logo Mail Archive

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

James Rafferty <James.Rafferty@dialogic.com> Wed, 24 March 2010 20:59 UTC

Return-Path: <James.Rafferty@dialogic.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 EE4D43A6846 for <codec@core3.amsl.com>; Wed, 24 Mar 2010 13:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.467
X-Spam-Level:
X-Spam-Status: No, score=-0.467 tagged_above=-999 required=5 tests=[AWL=1.002, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 QCtxMbxfRQM6 for <codec@core3.amsl.com>; Wed, 24 Mar 2010 13:59:28 -0700 (PDT)
Received: from outbound.dialogic.com (outbound.dialogic.com [65.220.90.252]) by core3.amsl.com (Postfix) with ESMTP id 283163A682E for <codec@ietf.org>; Wed, 24 Mar 2010 13:59:28 -0700 (PDT)
Received: from MBX.dialogic.com ([fe80::d09:39e:8fa1:c2a3]) by pysxht02.dialogic.com ([::1]) with mapi; Wed, 24 Mar 2010 16:59:49 -0400
From: James Rafferty <James.Rafferty@dialogic.com>
To: Christian Hoene <hoene@uni-tuebingen.de>, "codec@ietf.org" <codec@ietf.org>
Date: Wed, 24 Mar 2010 16:59:46 -0400
Thread-Topic: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
Thread-Index: AcrKrYfj3apVMECfQumBSXebrKc66AAIj/cwAABWsmAAAxkgoAAgP9rAAAjKMpAAFB0u4AAPb6YQ
Message-ID: <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>
In-Reply-To: <001501cacbd2$d8120230$88360690$@de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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 20:59:29 -0000

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>

v2.23.0 | Report a Bug | By Email