RE: Proposed text for remote recording use case

Jim,

Good point. Unfortunately the nature of  tones/announcements will vary considerably between jurisdictions, so the JS would either need to provide an explicit description of what is to be inserted, or would need to provide a source. In many cases nothing at all would be needed. Often it is the case that all callers into a contact centre are played an initial announcement that calls may be recorded, before being forwarded to the agent. So if an RTC-Web-based agent is acting as the recording client for remote recording, it perhaps won't need to provide any tone/announcement. 

John


> -----Original Message-----
> From: Jim McEachern [mailto:jim.mceachern@genband.com] 
> Sent: 22 August 2011 19:30
> To: Elwell, John; rtcweb@ietf.org; public-webrtc@w3.org
> Subject: RE: Proposed text for remote recording use case
> 
> John,
> It has previously been pointed out that in some jurisdictions 
> there is a legal requirement to insert a tone (e.g. an 
> intermittent beep) that indicates the conversation is being 
> recorded.  It seems like this would be a good thing to mention here.  
> 
> If this makes sense, I'm thinking something like the 
> following sentence added to the end of 4.2.yy:
> "... If required, the web application will direct the browser 
> to insert an appropriate indication (e.g. an intermediate 
> beep) into the media stream to show that the communication is 
> being recorded."
> 
> This also suggests an additional requirement.  
> "Ayy2: The web application MUST be able to ask the browser to 
> insert an appropriate indication into the media stream to 
> indicate that the communication is being recorded."
> 
> I believe that F15 already covers the requirments for the 
> browser in this case.
> F15:         The browser MUST be able to process and mix
>                    sound objects (media that is retrieved from another
>                    source than the established media 
> stream(s) with the
>                    peer(s) with audio streams).
> 
> Thoughts?
> Jim
> 
> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Monday, August 22, 2011 10:42 AM
> To: rtcweb@ietf.org; public-webrtc@w3.org
> Subject: [rtcweb] Proposed text for remote recording use case
> 
> 4.2.yy Remote Session Recording
> In this use case, the web application user wishes to record a 
> real-time communication at a remote recording device, such 
> that transmitted and received audio, video or other real-time 
> media are transmitted in real-time to the remote device. The 
> remote device can perform archiving, retrieval, playback, 
> etc., but can also perform real-time analytics on the media. 
> A typical deployment might be in a contact centre. For a 
> given medium, the two directions of transmission can be 
> transmitted together (mixed) or separately. The web 
> application also sends metadata that gives context to the 
> stored media.
> 
> New requirements:
> Fyy1: The browser MUST be able to send in real-time to a 
> remote recording device media that are being transmitted to 
> and received from remote participants.
> 
> Ayy1: The web application MUST be able to ask the browser to 
> transmit in real-time to a remote recording device media that 
> are being transmitted to and received from remote 
> participants and, in the case of audio at least, ask for the 
> two directions of transmission to be transmitted to the 
> remote recording device mixed or separately.
> 
> John
> 
> 
> John Elwell
> Tel: +44 1908 817801 (office and mobile)
> Email: john.elwell@siemens-enterprise.com
> http://www.siemens-enterprise.com/uk/
> 
> Siemens Enterprise Communications Limited.
> Registered office: Brickhill Street, Willen Lake, Milton 
> Keynes, MK15 0DJ.
> Registered No: 5903714, England.
> 
> Siemens Enterprise Communications Limited is a Trademark 
> Licensee of Siemens AG.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

Received on Tuesday, 23 August 2011 07:51:40 UTC