…hing the session without the need for audio transcoding, it is recommended in [ RFC7874 ] to include in the offer other suitable audio codecs beyond those that are mandatory to implement. This document provides some guidelines on the suitable codecs to be considered for WebRTC en…
…hing the session without the need for audio transcoding, it is recommended in [ RFC7874 ] to include in the offer other suitable audio codecs beyond those that are mandatory to implement. This document provides some guidelines on the suitable codecs to be considered for WebRTC en…
…he media formats MUST include the mandatory audio/video codecs as specified in [RFC7874], Section 3 , and [RFC7742], Section 5 . The m= line MUST be followed immediately by a "c=" line, as specified in [RFC4566], Section 5.7 . Again, as no candidates are available yet, the "c=" l…
…ment audio codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7874 ] . Mandatory-to-implement video codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7742 ] . WebRTC endpoints MAY additionally implement any other codec for which an RTP p…
…ment audio codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7874 ] . Mandatory-to-implement video codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7742 ] . WebRTC endpoints MAY additionally implement any other codec for which an RTP p…
…erConnection . Details of how DTMF is sent to the other peer are described in [ RFC7874 ]. 7.1 RTCRtpSender Interface Extensions The Peer-to-peer DTMF API extends the RTCRtpSender interface as described below. WebIDL partial interface RTCRtpSender { readonly attribute RTCDTMFSend…
…erConnection . Details of how DTMF is sent to the other peer are described in [ RFC7874 ]. 7.1 RTCRtpSender Interface Extensions The Peer-to-peer DTMF API extends the RTCRtpSender interface as described below. WebIDL partial interface RTCRtpSender { readonly attribute RTCDTMFSend…
…rConnection}}. Details of how DTMF is sent to the other peer are described in [[RFC7874]]. RTCRtpSender Interface Extensions The Peer-to-peer DTMF API extends the {{RTCRtpSender}} interface as described below. partial interface RTCRtpSender { readonly attribute RTCDTMFSender? dtm…
…erConnection . Details of how DTMF is sent to the other peer are described in [ RFC7874 ]. 7.1 RTCRtpSender Interface Extensions The Peer-to-peer DTMF API extends the RTCRtpSender interface as described below. WebIDL partial interface RTCRtpSender readonly attribute RTCDTMFSender…
…e normalized to uppercase on entry and are equivalent to A to D. As noted in [[!RFC7874]] Section 3, support for the characters 0 through 9, A through D, #, and * are required. The character ',' MUST be supported, and indicates a delay of 2 seconds before processing the next char…
…arameter. All other characters MUST be considered unrecognized . As noted in [[!RFC7874]] Section 3, support for the characters 0 through 9, A through D, #, and * are required. The duration parameter indicates the duration in ms to use for each character passed in the tones param…
…e normalized to uppercase on entry and are equivalent to A to D. As noted in [[!RFC7874]] Section 3, support for the characters 0 through 9, A through D, #, and * are required. The character ',' MUST be supported, and indicates a delay of 2 seconds before processing the next char…