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

Re: [webrtc-pc] canInsertDTMF transitions not specified

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Feb 2018 12:33:13 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-366963505-1519129992-sysbot+gh@w3.org>
After chewing through this in real code for a while, I think that the conditions for canInsertDTMF = true (in addition to "track" being present and being an audio track) are:
1) Negotiation done
2) Direction is sendrecv or sendonly
3) DTMF-capable codec ("telephone-event") negotiated
4) PeerConnection in "connected" state
SInce the last point is a state transition that we have an event for, it may make sense to hang the value change off the text that triggers the event.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1619#issuecomment-366963505 using your GitHub account
Received on Tuesday, 20 February 2018 12:33:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:01 UTC