[webrtc-pc] insertDTMF when transceiver.currentDirection is null

soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:

== insertDTMF when transceiver.currentDirection is null ==
Currently step 4 of `insertDTMF` throws `InvalidStateError` when `currentDirection` is `recvonly` or `inactive`. But `currentDirection` is only set after setting answer description.

Since it probably doesn't make sense to send DTMF before connection is established, we can probably make `insertDTMF` throw `InvalidStateError` as well when `currentDirection` is `null`.

One minor issue remain is that `insertDTMF` can be called before the RTP connection is fully established. Though I guess that just means the tone sent is lost and it is up to the application to control the UI to prevent sending before connected.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1515 using your GitHub account

Received on Friday, 28 July 2017 09:06:47 UTC