Session Initiation Protocol (SIP) based Media overload control Requirement
draft-partha-dispatch-sip-media-overload-control-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Parthasarathi R | ||
| Last updated | 2011-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
Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. SIP based overload mechanism exists for dedicated SIP signaling servers. But there is a need for overload control solution of SIP based media servers like PSTN GW, Session border controllers (SBC), Session Recording Server(SRS). This document summarizes problem specific to SIP media servers, requirements for the solution of SIP based media overload control.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)