SIP billing scenarios
draft-beck-sippping-billing-scen-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Wolfgang Beck | ||
| Last updated | 2002-03-28 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-beck-sippping-billing-scen-00.txt
https://www.ietf.org/archive/id/draft-beck-sippping-billing-scen-00.txt
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.)