Module: sip-router
Branch: tmp/ims_charging
Commit: e98012e859ea6dd2c198d650f272d3e489758a22
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e98012e…
Author: Carsten Bock <carsten(a)ng-voice.com>
Committer: Carsten Bock <carsten(a)ng-voice.com>
Date: Mon Sep 30 13:30:38 2013 +0200
Fixed minor typos in ims_charging-documentation
---
modules/ims_charging/doc/ims_charging_admin.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/modules/ims_charging/doc/ims_charging_admin.xml b/modules/ims_charging/doc/ims_charging_admin.xml
index cccfc06..33e72e7 100644
--- a/modules/ims_charging/doc/ims_charging_admin.xml
+++ b/modules/ims_charging/doc/ims_charging_admin.xml
@@ -45,6 +45,7 @@
<title>External Libraries or Applications</title>
<para>This modules requires the internal IMS library.</para>
</section>
+</section>
<section>
<title>Understanding Charging in the IP-Multimedia-Subsystem (IMS)</title>
<para>Before each service usage, the charging system must be asked for permission (credit authorization). The charging server must make a decision: Either authorize or deny the session.
@@ -133,7 +134,6 @@ As a result, we have the following three scenarios:
</mediaobject>
</section>
</section>
- </section>
<section>
<title>Parameters</title>
<section>
Module: sip-router
Branch: tmp/ims_charging
Commit: bcdc27641fbec8176cea19fd4cefad1830a5c4db
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bcdc276…
Author: Carsten Bock <carsten(a)ng-voice.com>
Committer: Carsten Bock <carsten(a)ng-voice.com>
Date: Mon Sep 30 13:23:05 2013 +0200
Fixed minor typos in ims_charging-documentation
---
modules/ims_charging/doc/ims_charging_admin.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/modules/ims_charging/doc/ims_charging_admin.xml b/modules/ims_charging/doc/ims_charging_admin.xml
index 86dd442..cccfc06 100644
--- a/modules/ims_charging/doc/ims_charging_admin.xml
+++ b/modules/ims_charging/doc/ims_charging_admin.xml
@@ -117,7 +117,7 @@ As a result, we have the following three scenarios:
</itemizedlist>
</section>
<section>
- <title>Online Charging (Ro)</title>
+ <title>Online Charging (Ro): A practical example</title>
<para>But how does it look in reality? Let us make a more practical example:</para>
<para>Let us assume we have a subscriber, who has sufficient credit for 75 seconds of talking. The subscriber initiates a call; as we do not know, how long the call will take, we start with requesting credit for 30 seconds (CCR-Request, we could request any duration, e.g. 2 hours, but it would probably block other calls if we reserve all the required credit).</para>
<para>The call proceeds, so after 30 seconds we send another CCR-Request with the indication that we used the reserved 30 seconds and that we request another 30 seconds. We reduce the account of the subscriber by 30 seconds, so he has a credit of 45 seconds. Since 45 seconds is more than the requested 30 seconds, this second request can also easily be accepted and another 30 seconds can be granted. After this request, the account is at 45 seconds and we still (or again) have 30 seconds reserved.</para>
Module: sip-router
Branch: tmp/ims_charging
Commit: e8a054d0e684b8f73bd0733d7d00d5e6b5e9b23f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e8a054d…
Author: Carsten Bock <carsten(a)ng-voice.com>
Committer: Carsten Bock <carsten(a)ng-voice.com>
Date: Mon Sep 30 13:20:04 2013 +0200
Fixed minor typos in ims_charging-documentation
---
modules/ims_charging/doc/ims_charging_admin.xml | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/modules/ims_charging/doc/ims_charging_admin.xml b/modules/ims_charging/doc/ims_charging_admin.xml
index b7d2d5a..86dd442 100644
--- a/modules/ims_charging/doc/ims_charging_admin.xml
+++ b/modules/ims_charging/doc/ims_charging_admin.xml
@@ -48,14 +48,14 @@
<section>
<title>Understanding Charging in the IP-Multimedia-Subsystem (IMS)</title>
<para>Before each service usage, the charging system must be asked for permission (credit authorization). The charging server must make a decision: Either authorize or deny the session.
-For postpaid scenarios this is fairly easy: The charging-server only needs to collect the usage data for processing it at the end of the month. As no realtime account updating is needed, this is often called „offline-charging“.
-For prepaid scenarios the charging server needs to know the user's account balance and it will need to update the account in real-time. This is often referred to as „online-charging“.
-
+For postpaid scenarios this is fairly easy: The charging-server only needs to collect the usage data for processing it at the end of the month. As no realtime account updating is needed, this is often called "offline-charging".
+For prepaid scenarios the charging server needs to know the user's account balance and it will need to update the account in real-time. This is often referred to as "online-charging".</para>
+<para>
Question: What is the double of the Radius?
-Answer: It's the Diameter!
-
-As quite often, we use the Diameter-Protocol to do the Charging in the IMS. And as quite often, IMS uses a huge bunch of acronyms to describe the different interfaces: We call the diameter-interface for offline-charging the „Rf“-interface and the interface for online charging the „Ro“-interface.
-
+Answer: It's the Diameter!</para>
+<para>
+As quite often, we use the Diameter-Protocol to do the Charging in the IMS. And as quite often, IMS uses a huge bunch of acronyms to describe the different interfaces: We call the diameter-interface for offline-charging the "Rf"-interface and the interface for online charging the "Ro"-interface.</para>
+<para>
Each system, that needs this credit authorization, have to be equipped with a proper charging trigger, a so-called charging-trigger-function (CTF) in order to communicate with the charging-server (also called charging-function):
</para>
<mediaobject>