Interoperation of "Application Server" B2BUAs with SIP Call Control
draft-worley-sipcore-b2bua-passthru-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dale R. Worley | ||
| Last updated | 2010-01-24 | ||
| 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
Some SIP architectures use "application servers", B2BUAs that are inserted between two user agents during a conversation, to provide additional processing. Since B2BUAs do not follow the rules for SIP proxies, they do not by default interoperate with SIP call control operations. Augmenting application servers with suitable behaviors for handling SIP call control operations mitigates these problems, and in many cases, allows standard user agents to use SIP call control features without modification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)