Re: [rtcweb] Use cases - recording and voicemail

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Mon, 22 August 2011 08:31 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
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 B8D1E21F88B6 for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 01:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.222
X-Spam-Level:
X-Spam-Status: No, score=-3.222 tagged_above=-999 required=5 tests=[AWL=-0.923, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 dw+qsnStBY2r for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 01:31:02 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id E924821F88A0 for <rtcweb@ietf.org>; Mon, 22 Aug 2011 01:31:01 -0700 (PDT)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id C799023F04AC; Mon, 22 Aug 2011 10:32:05 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 22 Aug 2011 10:32:05 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Date: Mon, 22 Aug 2011 10:32:04 +0200
Thread-Topic: Use cases - recording and voicemail
Thread-Index: AcxSt/LlJmDEj2CnTU+w+vCeEkemKwLhqs7gAAVmnc0AAi5qgAADou9iAAG1oJAAA27vJwCJPYqw
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E31018BF62FD@MCHP058A.global-ad.net>
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>
In-Reply-To: <BBF498F2D030E84AB1179E24D1AC41D616C389F24A@ESESSCMS0362.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 08:31:02 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Stefan Håkansson LK
> Sent: 19 August 2011 15:56
> 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.

[AndyH] It might do but I assume this would limit the RTP model that could be used to the endpoint model. We are currently reviewing how the RTP model for a session recording client should look like with the AVT experts (See http://tools.ietf.org/html/draft-eckel-siprec-rtp-rec-01). This might result in some requirements on how the client handles RTCP for example.


> 
> Stefan
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb