RFC 5373: Requesting Answering Modes for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document extends SIP with two header fields and associated option tags that can be used in INVITE requests to convey the requester's preference for user-interface handling related to answering of that request. The first header, "Answer-Mode", expresses a preference as to whether the target node's user interface waits for user input before accepting the request or, instead, accepts the request without waiting on user input. The second header, "Priv-Answer-Mode", is similar to the first, except that it requests administrative-level access and has consequent additional authentication and authorization requirements. These behaviors have applicability to applications such as push-to-talk and to diagnostics like loop-back. Usage of each header field in a response to indicate how the request was handled is also defined. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5373
- Published
- November 2008
- Authors
- D. Willis; A. Allen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5318The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)Updated
December 2008
- RFC 4964The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over CellularUpdated
September 2007
- RFC 6337Session Initiation Protocol (SIP) Usage of the Offer/Answer ModelCurrent
August 2011
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 7261Offer/Answer Considerations for G723 Annex A and G729 Annex BCurrent
May 2014
- RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent
November 2016
- RFC 8122Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)Updated
March 2017
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
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?