W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2011

Re: Mozilla/Cisco API Proposal: DTMF

From: Niklas Enbom <niklase@google.com>
Date: Fri, 15 Jul 2011 11:51:40 +0200
Message-ID: <CAHzHjDPkEoGbGYWAA6p3ssuxqSxn7novCuAS5W_u_5wSHLdLjw@mail.gmail.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Cc: Ian Hickson <ian@hixie.ch>, "public-webrtc@w3.org" <public-webrtc@w3.org>
SIP has too many ways of doing DTMF:
  * Inband waveform
  * RFC 4733
  * SIP Notify

It would be great if webrtc could stick to one.


On Thu, Jul 14, 2011 at 3:40 PM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> >On Tue, 12 Jul 2011, Cullen Jennings wrote:
> >>
> >> Just a side note, the best way to do DTMF (RFC 4733) is not as an audio
> >> tone but as a seperate coded for transering the data that keys werhe
> >> pressed.
> >
> >I'm all for supporting DTMF. It seems that the main use case would be
> >communicating with legacy systems (on the Web, one would presumably use a
> >native AJAX app or some such and only use audio/video conferencing to
> >speak to an actual human), so it seems one of our requirements here has to
> >be interoperability with the POTS, and thus with legacy SIP systems.
> >
> >How do legacy SIP systems support DTMF? We presumably have to do it the
> >same way.
> My understanding is that RFC 4733 is used (inserting a special payload
> carrying DTMF in the RTP stream).
Received on Saturday, 16 July 2011 20:15:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 16 July 2011 20:15:32 GMT