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

James Rafferty <James.Rafferty@dialogic.com> Tue, 23 March 2010 23:13 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 BAB623A6D11 for <codec@core3.amsl.com>; Tue, 23 Mar 2010 16:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.169
X-Spam-Level:
X-Spam-Status: No, score=-0.169 tagged_above=-999 required=5 tests=[AWL=1.300, 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 X5cw3K2a6oh8 for <codec@core3.amsl.com>; Tue, 23 Mar 2010 16:13:52 -0700 (PDT)
Received: from outbound.dialogic.com (outbound.dialogic.com [65.220.90.252]) by core3.amsl.com (Postfix) with ESMTP id 0F70D3A6D1B for <codec@ietf.org>; Tue, 23 Mar 2010 16:13:44 -0700 (PDT)
Received: from MBX.dialogic.com ([fe80::d09:39e:8fa1:c2a3]) by pysxht02.dialogic.com ([::1]) with mapi; Tue, 23 Mar 2010 19:14:04 -0400
From: James Rafferty <James.Rafferty@dialogic.com>
To: Christian Hoene <hoene@uni-tuebingen.de>
Date: Tue, 23 Mar 2010 19:14:00 -0400
Thread-Topic: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
Thread-Index: AcrKrYfj3apVMECfQumBSXebrKc66AAIj/cwAABWsmAAAxkgoA==
Message-ID: <617DF0128820F9458AC39149A627EE6C01A2947C85@MBX.dialogic.com>
References: <062.4b6a3862c443b2d8917e027f2267f4d2@tools.ietf.org> <617DF0128820F9458AC39149A627EE6C01A2947C57@MBX.dialogic.com> <000701cacad3$4b99c7c0$e2cd5740$@de>
In-Reply-To: <000701cacad3$4b99c7c0$e2cd5740$@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
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: Tue, 23 Mar 2010 23:13:53 -0000

Christian, 

Please see my comments below. 

James

-----Original Message-----
From: Christian Hoene [mailto:hoene@uni-tuebingen.de] 
Sent: Tuesday, March 23, 2010 2:53 PM
To: James Rafferty
Cc: codec@ietf.org
Subject: RE: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?

Hi James,

>In my view, this is dodging the real issue.  I believe there WILL be transcoding for point to point
>calls between wireline and wireless networks, where the connection is IP on both sides and multiple
>wide band codecs are used.

Could you elaborate a bit more on this scenario? Do you mean that the wireline has -for example- Skype phone with the Internet codec and the wireless end will have an LTE codec? Of course, both sides will use IP.

JR - Yes, the example of Skype from the desktop connecting to a mobile phone with wideband audio (say G.722.2) is an example.  In order for that to happen, there would likely be a border element at the network edge (what the Speermint architecture calls a Data Border Element) which negotiates the transcoding to take place in real time.  Another use case example would be where an enterprise IP phone uses a wideband codec when calling to a mobile phone, again requiring transcoding to take place to complete the call, if the two handsets do not support a common HD codec.   

>For that matter, there will also be cases where a PSTN - IP gateway is needed, but that's not usually
>defined as transcoding.

As a manufacturer of IP-to-IP gateways your insight knowledge is highly appreciated.
 
With best regards,

  Christian Hoene



>
>James
>
>James Rafferty
>Product Line Director, Integrated Media Gateways
>Dialogic, Inc.
>15 Crawford Street
>Needham, MA 02494
>USA
>
>Tel:    781 433 9462
>Mobile: 781 929 3895
>Fax:    781 433 9268
>Email:  james.rafferty@dialogic.com
>Web:    www.dialogic.com
>This e-mail is intended only for the named recipient(s) and may contain information that is
>privileged, confidential and/or exempt from disclosure under applicable law. No waiver of privilege,
>confidence or otherwise is intended by virtue of communication via the internet. Any unauthorized use,
>dissemination or copying is strictly prohibited. If you have received this e-mail in error, or are not
>named as a recipient, please immediately notify the sender and destroy all copies of this e-mail.
>
>-----Original Message-----
>From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of codec issue tracker
>Sent: Tuesday, March 23, 2010 10:20 AM
>To: hoene@uni-tuebingen.de
>Cc: codec@ietf.org
>Subject: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
>
>#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 mailing list
>codec@ietf.org
>https://www.ietf.org/mailman/listinfo/codec