RTCRtpSender interface provides the ability to control and obtain details about how a particular
MediaStreamTrack is encoded and sent to a remote peer.
With it, you can configure the encoding used for the corresponding track, get information about the device's media capabilities, and so forth. You can also obtain access to an
RTCDTMFSender which can be used to send DTMF codes (to simulate the user pressing buttons on a telephone's dial pad) to the remote peer.
RTCDTMFSenderwhich can be used to send DTMF tones using
telephone-eventpayloads on the RTP session represented by the
null, the track and/or the connection doesn't support DTMF. Only audio tracks can support DTMF.
MediaStreamTrackwhich is being handled by the
RTCRtpSenderdoesn't transmit anything.
RTCDtlsTransportover which the sender is exchanging the RTP and RTCP packets used to manage transmission of media and control data. This value is
nulluntil the transport is established. When bundling is in use, more than transceiver may be sharing the same transport object.
This property has been removed; the RTP and RTCP transports have been combined into a single transport. Use the
RTCRtpParametersobject describing the current configuration for the encoding and transmission of media on the
Applies changes to parameters which configure how the
trackis encoded and transmitted to the remote peer.
Attempts to replace the track currently being sent by the
RTCRtpSenderwith another track, without performing renegotiation. This method can be used, for example, to toggle between the front- and rear-facing cameras on a device.
|WebRTC 1.0: Real-Time Communication Between Browsers (WebRTC 1.0)|
BCD tables only load in the browser