files/en-us/web/api/rtcrtpsender/index.md
{{APIRef("WebRTC")}}
The RTCRtpSender interface provides the ability to control and obtain details about how a particular {{domxref("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 {{domxref("RTCDTMFSender")}} which can be used to send {{Glossary("DTMF")}} codes (to simulate the user pressing buttons on a telephone's dial pad) to the remote peer.
telephone-event payloads on the {{Glossary("RTP")}} session represented by the RTCRtpSender object. If null, the track and/or the connection doesn't support DTMF. Only audio tracks can support DTMF.RTCRtpSender. If track is null, the RTCRtpSender doesn't transmit anything.null until the transport is established. When bundling is in use, more than transceiver may be sharing the same transport object.rtcpTransport {{deprecated_inline}}
track.RTCRtpSender.track is encoded and transmitted to the remote peer.RTCRtpSender with another track, without performing renegotiation. This method can be used, for example, to toggle between the front- and rear-facing cameras on a device.{{Specifications}}
{{Compat}}