W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2018

[webrtc-pc] DTMF sending: Permit only in connected status?

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Feb 2018 12:26:01 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-298575509-1519129559-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== DTMF sending: Permit only in connected status? ==
I had the dubious honor to debug a race condition involving an attempt to send DTMF before the connection was fully opened today.
It wasn't pretty.
It seems ugly (and silly) to require the implementation to buffer DTMF until the channel is open, and it seems ugly (and silly) to have behavior here diverge across browsers.
Can we have the spec say that CanSendDTMF MUST be FALSE unless the RTCPeerConnection's "connectionState" is in the "connected" state?
Yes, there are cases where that is too pessimistic (the audio channel's transport might be open before everything is settled), but at least it's a consistent behavior pattern.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1777 using your GitHub account
Received on Tuesday, 20 February 2018 12:26:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 February 2018 12:26:35 UTC