Implementing Call Park and Retrieve using the Session Initiation Protocol (SIP)
draft-ietf-bliss-call-park-extension-01
Document | Type |
Expired Internet-Draft
(bliss WG)
Expired & archived
|
|
---|---|---|---|
Author | Michael Procter | ||
Last updated | 2009-10-14 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Call Park and Call Retrieve are useful telephony services that are familiar to many users. Existing implementations using the Session Initiation Protocol (SIP) show that a variety of approaches can be Taken, with varying degrees of interoperability. This draft discusses a number of feature variations, and how they may be implemented using existing techniques. An additional URI parameter is also described, which enables further common use-cases to be implemented.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)