RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
0 sources
RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
Summary
RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals is a Request for Comments[1].
Key Facts
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals authored RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — author (P50): Henning Schulzrinne[2].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals authored RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — author (P50): Tom Taylor[3].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's instance of is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — instance of (P31): Request for Comments[4].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's publisher is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — publisher (P123): Internet Engineering Task Force[5].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's DOI is recorded as 10.17487/RFC4733[6].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's language of work or name is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — language of work or name (P407): English[7].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's publication date is recorded as +2006-12-01T00:00:00Z[8].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's RfC ID is recorded as 4733[9].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's main subject is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — main subject (P921): Real-time Transport Protocol[10].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's work available at URL is recorded as https://tools.ietf.org/html/rfc4733[11].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4733.txt[12].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4733.txt[13].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4733.txt.pdf[14].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's number of pages is recorded as {'unit': '1', 'amount': '+49'}[15].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's replaces is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — replaces (P1365): RFC 2833: RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals[16].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's title is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals[17].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's amended by is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — amended by (P2567): RFC 4734: Definition of Events for Modem, Fax, and Text Telephony Signals[18].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's amended by is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — amended by (P2567): RFC 5244: Definition of Events for Channel-Oriented Telephony Signalling[19].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 2119: Key words for use in RFCs to Indicate Requirement Levels[20].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 2198: RTP Payload for Redundant Audio Data[21].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs[22].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 3264: An Offer/Answer Model with Session Description Protocol (SDP)[23].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[24].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 3555: MIME Type Registration of RTP Payload Formats[25].
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's cites work is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — cites work (P2860): RFC 3711: The Secure Real-time Transport Protocol (SRTP)[26].
Body
Designation and Status
RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals's instance of is recorded as RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — instance of (P31): Request for Comments[4].