Re: [rtcweb] Use cases - recording and voicemail

"Elwell, John" <john.elwell@siemens-enterprise.com> Fri, 19 August 2011 13:24 UTC

Return-Path: <john.elwell@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 7D10C21F8AFD for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 06:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.155
X-Spam-Level:
X-Spam-Status: No, score=-103.155 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 vRWRdJb0UhlZ for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 06:24:43 -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 C6AC821F8AD9 for <rtcweb@ietf.org>; Fri, 19 Aug 2011 06:24:42 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 1722923F053A; Fri, 19 Aug 2011 15:25:37 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 19 Aug 2011 15:25:37 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Date: Fri, 19 Aug 2011 15:25:35 +0200
Thread-Topic: Use cases - recording and voicemail
Thread-Index: AcxSt/LlJmDEj2CnTU+w+vCeEkemKwLhqs7gAAVmnc0AAi5qgAADou9iAAG1oJA=
Message-ID: <A444A0F8084434499206E78C106220CA09BDB6A397@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>
In-Reply-To: <BBF498F2D030E84AB1179E24D1AC41D616C389F245@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: Fri, 19 Aug 2011 13:24:43 -0000

Stefan,

No, I am not suggesting both local recording and remote recording at the same time. Sometimes local recording will be required, sometimes remote recording.

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.

John


> -----Original Message-----
> From: Stefan Håkansson LK [mailto:stefan.lk.hakansson@ericsson.com] 
> Sent: 19 August 2011 13:34
> To: Elwell, John; rtcweb@ietf.org; public-webrtc@w3.org
> Subject: RE: Use cases - recording and voicemail
> 
> John,
> >> I'm less sure about that the recorded media should also be an
> >> RTP source - couldn't you just as well send the file over and
> >> then play it at the remote end?
> >[JRE] Yes, the file could be streamed across, but there are 
> folks who want it to get across more or less in real time, 
> e.g., where the recorder is performing real-time analytics, 
> perhaps in a >contact centre. This is the basis for the work 
> done in the IETF SIPREC WG. The same considerations that 
> require RTP browser-to-browser for RTC-Web also dictate RTP 
> as the transport for >sending media to a recorder.
> [Stefan] If you want to do stuff remotely in real time, could 
> you not just avoid recording locally? Regardless of if the 
> analysis is to happen on a locally generated stream, or on a 
> stream received via RTP, that stream can be streamed to the 
> analysing server (via a p2p-connection), right? (Probably I 
> am missing something).
> 
> Stefan