Re: [rtcweb] Use cases - recording and voicemail

Stefan Håkansson LK <> Fri, 19 August 2011 12:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2DD4921F876A for <>; Fri, 19 Aug 2011 05:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.258
X-Spam-Status: No, score=-6.258 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LwpTOQKlIby8 for <>; Fri, 19 Aug 2011 05:32:46 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B7F6821F8744 for <>; Fri, 19 Aug 2011 05:32:39 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c47ae000000b17-19-4e4e581fd18a
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id F2.BF.02839.F185E4E4; Fri, 19 Aug 2011 14:33:35 +0200 (CEST)
Received: from ([]) by ([]) with mapi; Fri, 19 Aug 2011 14:33:35 +0200
From: Stefan Håkansson LK <>
To: "Elwell, John" <>, "" <>, "" <>
Date: Fri, 19 Aug 2011 14:33:35 +0200
Thread-Topic: Use cases - recording and voicemail
Thread-Index: AcxSt/LlJmDEj2CnTU+w+vCeEkemKwLhqs7gAAVmnc0AAi5qgAADou9i
Message-ID: <>
References: <> <>, <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [rtcweb] Use cases - recording and voicemail
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Aug 2011 12:32:47 -0000

>> 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).