Skip to main content

Completion of Calls for the Session Initiation Protocol (SIP)
RFC 6910

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The "completion of calls" feature defined in this specification allows the caller of a failed call …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-12-31
Jean Mahoney Closed request for Last Call review by GENART with state 'No Response'
2015-10-14
(System) Notify list changed from bliss-chairs@ietf.org, draft-ietf-bliss-call-completion@ietf.org to (None)
2013-04-22
(System) Posted related IPR disclosure: Research In Motion, Limited's Statement about IPR related to RFC 6910 and draft-ietf-bliss-call-completion-19
2013-04-15
(System) RFC published