- From: cbran <cbran@cisco.com>
- Date: Wed, 13 Jul 2011 11:50:58 -0700
- To: Cullen Jennings <fluffy@cisco.com>, Harald Alvestrand <harald@alvestrand.no>
- CC: <public-webrtc@w3.org>
Harald, For the WebRTC API, it seems desirable, for the user agent to expose a high level API that provides the capabilities for web applications to send DTMFs and notify the web application when DTMFs are received. I agree with what Cullen said below and would defer the underlying mechanism(s) for the actual sending/receiving of DTMFs to the RTC-Web WG. > On 7/13/11 7:49 AM, "Cullen Jennings" <fluffy@cisco.com> wrote: > On Jul 13, 2011, at 3:56 , Harald Alvestrand wrote: > >> On 07/12/2011 06:27 PM, cbran wrote: >>> Thanks for sending this Stefan. >>> >>> After reviewing the document, it appears that there are no requirements >>> around sending DTMFs. I would propose that we add the following >>> requirements to the requirements list: >>> >>> The User Agent must provide capabilities to send and receive DTMFs. >>> The Web Application must be able to send and receive DTMFs. >> Cary, >> >> in the interest of getting clear requirements: >> do you mean that the User Agent MUST create a special event when DTMF tones >> occur in the media stream, or do you mean that the User Agent MUST create a >> special event when DTMF is signalled by a non-media mechanism, such as the >> multiple SIP mechanisms? > > by whatever mechism the RTCWeb group decided to do DTMF I think. But seriously > this is not going to be in band tone detection - that just does not really > work. > >> >> I'm eager to know if this requirement means that browsers have to implement >> an audio DTMF detector or not. Generation should be straightforward enough. > >
Received on Wednesday, 13 July 2011 18:51:34 UTC