Re: [rtcweb] Use cases - recording and voicemail

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 22 August 2011 13:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B54F21F8B28 for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 06:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.244
X-Spam-Level:
X-Spam-Status: No, score=-2.244 tagged_above=-999 required=5 tests=[AWL=-0.245, BAYES_00=-2.599, J_CHICKENPOX_36=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVcAw5SlUwUn for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 06:17:53 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by ietfa.amsl.com (Postfix) with ESMTP id 5795221F8B0C for <rtcweb@ietf.org>; Mon, 22 Aug 2011 06:17:53 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta12.westchester.pa.mail.comcast.net with comcast id PR3W1h0061swQuc5CRJy0e; Mon, 22 Aug 2011 13:18:58 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta15.westchester.pa.mail.comcast.net with comcast id PRJl1h02E0tdiYw3bRJsXr; Mon, 22 Aug 2011 13:18:58 +0000
Message-ID: <4E525734.80209@alum.mit.edu>
Date: Mon, 22 Aug 2011 09:18:44 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <BBF498F2D030E84AB1179E24D1AC41D616C389F16D@ESESSCMS0362.eemea.ericsson.se><4E3AB4D4.4070308@jesup.org>, <A444A0F8084434499206E78C106220CA09BDB6A238@MCHP058A.global-ad.net><BBF498F2D030E84AB1179E24D1AC41D616C389F242@ESESSCMS0362.eemea.ericsson.se>, <A444A0F8084434499206E78C106220CA09BDB6A34F@MCHP058A.global-ad.net><BBF498F2D030E84AB1179E24D1AC41D616C389F245@ESESSCMS0362.eemea.ericsson.se>, <A444A0F8084434499206E78C106220CA09BDB6A397@MCHP058A.global-ad.net> <BBF498F2D030E84AB1179E24D1AC41D616C389F24A@ESESSCMS0362.eemea.ericsson.se> <2E239D6FCD033C4BAF15F386A979BF510640D0@sonusinmail02.sonusnet.com> <A444A0F8084434499206E78C106220CA0B00FDABAD@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0B00FDABAD@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] Use cases - recording and voicemail
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 13:17:54 -0000

On 8/22/11 2:28 AM, Elwell, John wrote:
> Partha,
>
> You are talking here about the metadata, I think. I assume the web page / JavaScript has to deal with that - not the browser.

I don't understand your point John. The javascript is executed by the 
browser.

The actual awareness of information that is to become siprec metadata 
may well be distributed - some of it in the client/browser, and some of 
it in the server. That will somewhat complicate getting it all together.

	Thanks,
	Paul

> John
>
>
>> -----Original Message-----
>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>> Sent: 19 August 2011 18:19
>> To: Stefan Håkansson LK; Elwell, John; rtcweb@ietf.org;
>> public-webrtc@w3.org
>> Subject: RE: [rtcweb] Use cases - recording and voicemail
>>
>> Stefan,
>>
>> In case recording similar to SIPREC, it is little bit more
>> than spanning two media (RTP stream) alone because recording
>> has to include some context data about recording apart from
>> the media stream.
>>
>> Thanks
>> Partha
>>
>>> -----Original Message-----
>>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
>>> Behalf Of Stefan Håkansson LK
>>> Sent: Friday, August 19, 2011 8:26 PM
>>> To: Elwell, John; rtcweb@ietf.org; public-webrtc@w3.org
>>> Subject: Re: [rtcweb] Use cases - recording and voicemail
>>>
>>>> However, I did suggest (in other text in my previous
>> message) that one
>>> possible solution might be to record locally and use a
>> second RTC-Web
>>> session to transmit from the local file to the>remote
>> recorder. What I
>>> failed to say was that in this case the local file would be
>> a temporary
>>> repository - just a buffer between the two sessions.
>>> This makes sense. Also, if you look at the API proposals
>> available, it
>>> would be quite easy to forward (in real time) a stream
>> being received
>>> to another entity. There is no explicit recording, a stream being
>>> received (via RTP) is just streamed to another entity (via
>> a separate
>>> RTC-Web session). I think this would solve this case.
>>>
>>> Stefan
>>> _______________________________________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>