Redirection Service Capability in SIP
draft-bharatia-sipping-redirect-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jayshree A. Bharatia | ||
| Last updated | 2001-11-19 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
SIP is selected as a session control protocol for many VOIP applications. Hence it should provide capabilities for supporting such redirection-based services as automatic call distribution for call centers, third-party voicemail, follow-me service etc. The concept of Call Redirection is implicit in the capabilities already defined for SIP Proxies and Clients.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)