SIP billing scenarios
draft-beck-sippping-billing-scen-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wolfgang Beck | ||
| Last updated | 2002-03-28 | ||
| 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
In contrast to other Internet services, most SIP sessions take place between individuals. Today's billing schemes (flat rate or volume based) do not reflect that. A caller causes costs on the callee's side. With SIP's authentication methods and few additional headers, a SIP billing service could be established that would enable callees to charge their callers. Call stateful proxies are not required.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)