964282 - Include telephone-event at 48000 Hz in SDP

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Signaling, defect, P2)

Description

[Adam Roach [:abr]]

Currently, we offer PCMU at 8 kHz and opus at 48 kHz, but only offer DTMF at 8 kHz. This apparently causes problems for some implementations.

cf. https://mailarchive.ietf.org/arch/msg/mmusic/s-bRERKTuaoQnx4eFMdAU6rgjVM%3D/

Comment 2

[Byron Campen [:bwc]]

We don't do telephone-event anymore, and we don't need to re-add telephone-event, right?

Comment 3

[Adam Roach [:abr]]

(In reply to Byron Campen [:bwc] from comment #2)
> We don't do telephone-event anymore, and we don't need to re-add
> telephone-event, right?

draft-ietf-rtcweb-audio-08 section 3 requires support, as does <http://w3c.github.io/webrtc-pc/#peer-to-peer-dtmf>. These documents are pretty mature, and quite unlikely to change in this regard.

That said, *this* bug has been overtaken by events. We just need to make sure to get the clock handling right when we reimplement our telephone-event SDP handling. When you close this, please open two new bugs: one each for the SDP and API components of this task.

Comment 4

[Randell Jesup [:jesup] (needinfo me)]

Agreed.  we need to add telephone-event, RFC 5833 (IIRC) and the associated JS APIs to our backlog for spec-compliance; likely in new bugs if we don't have one lying around (we might).  

Maire - we should link whatever bug(s) are identified to a meta-bug for spec compliance, and we should probably file such a meta-bug (again if it doesn't exist).

Comment 5

[Maire Reavy [:mreavy]]

As mentioned above, this is overtaken by events.  I've opened two new bugs for the work we want to do for spec compliance: Bug 1165689, Bug 1165690.