Skip to main content

References to RFC 2833

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
draft-ietf-asap-sip-auto-peer Automatic Peering for SIP Trunks
References Referenced by
normatively references
RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
References Referenced by
Proposed Standard normatively references
RFC 3264 An Offer/Answer Model with Session Description Protocol (SDP)
References Referenced by
Proposed Standard informatively references
RFC 3372 Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
References Referenced by
Best Current Practice informatively references
RFC 3388 Grouping of Media Lines in the Session Description Protocol (SDP)
References Referenced by
Proposed Standard informatively references
RFC 3485 The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
References Referenced by
Proposed Standard informatively references
RFC 3660 Basic Media Gateway Control Protocol (MGCP) Packages
References Referenced by
Informational informatively references
RFC 3976 Interworking SIP and Intelligent Network (IN) Applications
References Referenced by
Informational informatively references
RFC 4083 Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)
References Referenced by
Informational informatively references
RFC 4103 RTP Payload for Text Conversation
References Referenced by
Proposed Standard informatively references
RFC 4317 Session Description Protocol (SDP) Offer/Answer Examples
References Referenced by
Informational informatively references
RFC 4351 Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream
References Referenced by
Historic informatively references
RFC 4463 A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks
References Referenced by
Informational informatively references
RFC 4504 SIP Telephony Device Requirements and Configuration
References Referenced by
Informational informatively references
RFC 4585 Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)
References Referenced by
Proposed Standard informatively references
RFC 4730 A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)
References Referenced by
Proposed Standard informatively references
RFC 4733 RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
References Referenced by
Proposed Standard informatively references
RFC 5086 Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)
References Referenced by
Informational informatively references
RFC 5244 Definition of Events for Channel-Oriented Telephony Signalling
References Referenced by
Proposed Standard informatively references
RFC 3794 Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents
References Referenced by
Informational Possible Reference
RFC 4734 Definition of Events for Modem, Fax, and Text Telephony Signals
References Referenced by
Proposed Standard Possible Reference