…tmfSender instance allows sending DTMF tones to/from the remote peer, as per [[!RFC4733]]. Operation An RTCDtmfSender object is constructed from an RTCRtpSender object. Interface Definition readonly attribute boolean canInsertDTMF Whether the RTCDtmfSender is capable of sending D…

…tmfSender instance allows sending DTMF tones to/from the remote peer, as per [[!RFC4733]]. Operation An RTCDtmfSender object is constructed from an RTCRtpSender object. Interface Definition readonly attribute boolean canInsertDTMF Whether the RTCDtmfSender is capable of sending D…

…tmfSender instance allows sending DTMF tones to/from the remote peer, as per [[!RFC4733]]. Operation An RTCDtmfSender object is constructed from an RTCRtpSender sender . If sender.track.kind is not "audio", throw an InvalidParameters exception. Interface Definition [ Constructor …

…tmfSender instance allows sending DTMF tones to/from the remote peer, as per [[!RFC4733]]. Operation An RTCDtmfSender object is constructed from an RTCRtpSender object. Interface Definition readonly attribute boolean canInsertDTMF Whether the RTCDtmfSender is capable of sending D…

…hey MUST use the same timestamp clock rate as the regular audio channel. Notes: RFC4733 was written in a way to avoid the multiple clock-rate problem by mandating the use of the same SSRC for DTMF and audio. However it's not explicitly written, which brings an ambiguity. It was c…

…hey MUST use the same timestamp clock rate as the regular audio channel. Notes: RFC4733 was written in a way to avoid the multiple clock-rate problem by mandating the use of the same SSRC for DTMF and audio. However it's not explicitly written, which brings an ambiguity. It was c…