- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Fri, 19 Aug 2011 19:46:52 +0200
- To: Ravindran Parthasarathi <pravindran@sonusnet.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Partha, thanks for updating me. Stefan ________________________________________ From: Ravindran Parthasarathi [pravindran@sonusnet.com] Sent: Friday, August 19, 2011 7:18 PM 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
Received on Friday, 19 August 2011 17:48:47 UTC