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


From: Matthew Kaufman <matthew.kaufman@skype.net>
Date: Thu, 19 Jul 2012 14:27:10 +0000
To: Tim Panton <thp@westhawk.co.uk>, Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A4840E4B9B8F@TK5EX14MBXC273.redmond.corp.microsoft.com>

Tim Panton [thp@westhawk.co.uk]:
> All legacy signalling protocols I can think of have the ability to carry DTMF. Why do we want to make this a media
> issue ?
> Can't we just say it is out of scope an let the application's selected signalling deal with it?

No. This was discussed to death months ago on the IETF side. There are a large number of legacy devices that require that the DTMF events appear in the media, not signaling, stream. Requiring gateway of media, particularly secure media, just to mix in DTMF events is unacceptable.

Matthew Kaufman
Received on Thursday, 19 July 2012 14:27:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:28 UTC