SIP URI Conventions for Media Servers
draft-burger-sipping-msuri-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jeff Van Dyke , Eric Burger | ||
| Last updated | 2001-11-30 | ||
| 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
Application Servers, SIP Proxies, and SoftSwitches (a.k.a. Media Gateway Controllers) act as SIP [2] User Agents to control the media processing capabilities of media servers. The SIP Request URI identifies the desired service and provides a context for the media server to interpret the SIP message. This document describes a standard SIP addressing mechanism to address specific services. Because of SIP's flexibility, the existing protocol accommodates these services. This document proposes a standard URI scheme for important media services such as announcements and conferencing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)