SIP endpoint service charging requirements
draft-beck-sipping-svc-charging-req-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2002-12-20 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| 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-sipping-svc-charging-req-01.txt
https://www.ietf.org/archive/id/draft-beck-sipping-svc-charging-req-01.txt
Abstract
Today, a SIP user wanting to charge for a service needs to establish an agreement with all prospective callers. This administrative overhead can be avoided if caller and callee can prove the duration and existence of a call in case of a dispute. The draft describes requirements for protocols and SIP extension that can be used to implement such functionality.
Authors
Wolfgang Beck (beckw@t-systems.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)