Remove RTCPeerConnection.createDTMFSender and add RTCRtpSender.dtmf.

[pthatcherg]

Fixing #132

[alvestrand]

Needs to be integrated to main after #175, since it references RTCRTPSender.

[fluffy]

Need to think about how this interacts with SDP - Will all tracks have DTMF negotiated for them ? seems like a waste of PT when it is usually not needed.

[pthatcherg]

Cullen: Would it make sense to have an option in RTCOfferAnwerOptions.dtmf just as we have RTCOfferAnswerOptions.voiceActivityDetection in pthatcherg@90af82e?

If that would work, I can propose it on the list.

[pthatcherg]

In Chrome at least, we always put DTMF in the offer, so we're already using
the PT. Meanwhile, we're always negotiating PCMA and PCMU. In other
words, we're already using lots of PTs. Meanwhile, is it even possible to
re-negotiate with DTMF later if the DTMF isn't in the original offer? In
that case, we have to have it in the original offer anyway.

On Thu, Jan 15, 2015 at 7:54 AM, Cullen Jennings [email protected]
wrote:

Need to think about how this interacts with SDP - Will all tracks have
DTMF negotiated for them ? seems like a waste of PT when it is usually not
needed.

—
Reply to this email directly or view it on GitHub
#167 (comment).

[fluffy]

OK - seems reasonable to me

[adam-be]

Rebased and integrated.

[jesup]

I"ll note that Firefox has not thus far added DTMF to our offers (nor have we integrated support for it yet). If we're requiring DTMF on all audio channels, that's new - IMHO it should be in OfferAnswerOptions