Re: [MEDIACTRL] RFC 4117 Vs MCCF for Transcoding service invocation

"Rai, Shambhu" <srai@sonusnet.com> Tue, 04 March 2008 12:39 UTC

Return-Path: <mediactrl-bounces@ietf.org>
X-Original-To: ietfarch-mediactrl-archive@core3.amsl.com
Delivered-To: ietfarch-mediactrl-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 264C528C41A; Tue, 4 Mar 2008 04:39:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.017
X-Spam-Level:
X-Spam-Status: No, score=-0.017 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_17=0.6, RDNS_NONE=0.1]
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 qw+h9gcM3RLd; Tue, 4 Mar 2008 04:39:01 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD8753A6A07; Tue, 4 Mar 2008 04:39:01 -0800 (PST)
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 491BD3A6A07 for <mediactrl@core3.amsl.com>; Tue, 4 Mar 2008 04:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 qHh2C4OuR7Cy for <mediactrl@core3.amsl.com>; Tue, 4 Mar 2008 04:38:59 -0800 (PST)
Received: from sonussf2.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id 4E7E03A697D for <mediactrl@ietf.org>; Tue, 4 Mar 2008 04:38:59 -0800 (PST)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonussf2.sonusnet.com (8.13.7/8.13.7) with ESMTP id m24Ccpd4018254 for <mediactrl@ietf.org>; Tue, 4 Mar 2008 07:38:51 -0500
Received: from SONUSINMAIL01.sonusnet.com ([10.128.254.7]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Mar 2008 07:38:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 04 Mar 2008 18:08:47 +0530
Message-ID: <70798CF421F00F4DA018059E5B7EEB8C01E65AD7@sonusinmail01.sonusnet.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEDIACTRL] RFC 4117 Vs MCCF for Transcoding service invocation
Thread-Index: Ach1mJx+gHDKzejYS+2PoQ1fomF86wEK9TvgANK6Q6AAOTyj0A==
From: "Rai, Shambhu" <srai@sonusnet.com>
To: mediactrl@ietf.org
X-OriginalArrivalTime: 04 Mar 2008 12:38:49.0884 (UTC) FILETIME=[B269F5C0:01C87DF4]
Subject: Re: [MEDIACTRL] RFC 4117 Vs MCCF for Transcoding service invocation
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control BOF Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mediactrl-bounces@ietf.org
Errors-To: mediactrl-bounces@ietf.org

HI,

I am not sure, if my message reached the list.. Can some one comment on
my questions on Transcoding service using media control channel
framework in the mail below?

Regards,
Shambhu
-----Original Message-----
From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On
Behalf Of Rai, Shambhu
Sent: Monday, March 03, 2008 2:55 PM
To: mediactrl@ietf.org
Subject: [MEDIACTRL] FW: RFC 4117: Sip signaling for Transcoding
serviceinvocation

Hi Guys,

I am new to this list. So, please excuse me if I am raising already
discussed questions. 

1. I am looking at the signaling model options for Transcoding service
invocation on media server. Is there a package defined in the
"mediactrl" framework for invoking the transcoding service on media
server or one has to support conference packages to support the
transcoding? 

2. RFC 4117 proposes framework/call flows to invoke the transcoding
service on Media server from a 3PCC AS. What is the MediaCtrl group's
position on the same?
 
Regards,
Shambhu



-----Original Message-----
From: Rai, Shambhu 
Sent: Thursday, February 28, 2008 10:23 AM
To: sip-implementors@lists.cs.columbia.edu;
'Gonzalo.Camarillo@ericsson.com'; 'eburger@brooktrout.com'
Subject: RFC 4117: Sip signaling for Transcoding service invocation 

HI All, 

Is anyone aware of any Media server / MRF / Transcoder using 3PCC
control mechanism described in RFC 4117 for invoking a transcoding
service?

I am evaluating the Signaling model to invoke transcoding service on
MRF. I can think of following options.

1. RFC 4117 based 3PCC transcoding service invocation:
        In this case AS setup only one Dialog (with SDP of A and
B)towards MRF requesting the transcoding service. 

2. 3PCC AS Use an identifier like a conference identifier to move both
parties in the same context.
    I am wondering, If setting up transcoding as two party conference
will be a good idea?  As there will be need to distinguish transcoder
service from the conferencing service. Like A party doing hold unhold
etc, These scenarios needs to be handled differently for transcoding
from conference.

It will be good to know industry accepted mechanism for the same. Any
inputs are welcome.

Regards,
Shambhu

_______________________________________________
MEDIACTRL mailing list
MEDIACTRL@ietf.org
https://www.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl

_______________________________________________
MEDIACTRL mailing list
MEDIACTRL@ietf.org
https://www.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl