Private Session Initiation Protocol ((SIP) extension for Called Party Identity
draft-garcia-sip-called-party-id-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Miguel Angel García | ||
| Last updated | 2002-06-05 | ||
| 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
This memo describes a private extension to SIP in the form of a P-Called-Party-ID header. A proxy inserts this header typically in an INVITE, en-route to its destination. The header is populated with the Request-URI received by the proxy in the request. The UAS identifies which ID out of several IDs the invitation was sent to (for example, the user may be using simultaneously a personal and a business SIP URI to receive invitation to sessions). The UAS may use the information to render different distinctive audiovisual alerting tones, depending on the ID used to receive the invitation to the session.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)