RFC 6910: Completion of Calls for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
The "completion of calls" feature defined in this specification allows the caller of a failed call to be notified when the callee becomes available to receive a call. For the realization of a basic solution without queuing, this document references the usage of the dialog event package (RFC 4235) that is described as 'Automatic Redial' in "Session Initiation Protocol Service Examples" (RFC 5359). For the realization of a more comprehensive solution with queuing, this document introduces an architecture for implementing these features in the Session Initiation Protocol where "completion of calls" implementations associated with the caller's and callee's endpoints cooperate to place the caller's request for completion of calls into a queue at the callee's endpoint; when a caller's request is ready to be serviced, re-attempt of the original, failed call is then made. The architecture is designed to interoperate well with existing completion of calls solutions in other networks.
Document record
- Document ID
- RFC6910
- Published
- April 2013
- Authors
- D. Worley; M. Huelsemann; R. Jesske; D. Alexeitsev
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 4119A Presence-based GEOPRIV Location Object FormatUpdated
December 2005
- RFC 4827An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document ContentsCurrent
May 2007
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 9743Specifying New Congestion Control AlgorithmsCurrent
March 2025
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?