Session Initiation Protocol Exceptional Procedure Examples
draft-hasebe-sipping-exceptional-procedure-example-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Miki Hasebe | ||
| Last updated | 2006-03-21 (Latest revision 2006-03-05) | ||
| Replaced by | draft-hasebe-sipping-race-examples | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-hasebe-sipping-race-examples | |
| 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 document gives examples of Session Initiation Protocol (SIP) call flows in race condition. Call flows in race conditions are confusing and this document shows the best practices to handle them. The elements in these call flows include SIP User Agents and SIP Proxies. Call flow diagrams and message details are shown.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)