RFC 4504: SIP Telephony Device Requirements and Configuration
In plain English — editorial summary, not part of the RFC
This document describes the requirements for SIP telephony devices, based on the deployment experience of large numbers of SIP phones and PC clients using different implementations in various networks. The objectives of the requirements are a well-defined set of interoperability and multi-vendor-supported core features, so as to enable similar ease of purchase, installation, and operation as found for PCs, PDAs, analog feature phones or mobile phones. We present a glossary of the most common settings and some of the more widely used values for some settings. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4504
- Published
- May 2006
- Authors
- H. Sinnreich; S. Lass; C. Stredicke
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 4245High-Level Requirements for Tightly Coupled SIP ConferencingCurrent
November 2005
- RFC 4240Basic Network Media Services with SIPCurrent
December 2005
- RFC 4896Signaling Compression (SigComp) Corrections and ClarificationsCurrent
June 2007
- RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)Updated
December 2004
- RFC 3968The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3959The Early Session Disposition Type for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3911The Session Initiation Protocol (SIP) "Join" HeaderCurrent
October 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?