IETF Logo Mail Archive

Re: [rtcweb] Use cases - recording and voicemail

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Fri, 19 August 2011 17:18 UTC

Return-Path: <pravindran@sonusnet.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 C002C21F8B66 for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 10:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.149, 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 mfPDKI8wVv+A for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 10:18:01 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 39C7C21F8B27 for <rtcweb@ietf.org>; Fri, 19 Aug 2011 10:18:00 -0700 (PDT)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p7JHJLJa030273; Fri, 19 Aug 2011 13:19:21 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Aug 2011 13:18:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Aug 2011 22:48:36 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510640D0@sonusinmail02.sonusnet.com>
In-Reply-To: <BBF498F2D030E84AB1179E24D1AC41D616C389F24A@ESESSCMS0362.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Use cases - recording and voicemail
Thread-Index: AcxSt/LlJmDEj2CnTU+w+vCeEkemKwLhqs7gAAVmnc0AAi5qgAADou9iAAG1oJAAA27vJwAEvE9w
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>
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, rtcweb@ietf.org, public-webrtc@w3.org
X-OriginalArrivalTime: 19 Aug 2011 17:18:54.0304 (UTC) FILETIME=[125B3600:01CC5E94]
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: Fri, 19 Aug 2011 17:18:01 -0000

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

v2.23.0 | Report a Bug | By Email