[sr-dev] git:master: modules/ims_charging: updated documentation for new parameter: single_ro_session_per_dialog

[Richard Good]

Module: sip-router
Branch: master
Commit: eb8551205f651263f6c7cdf3afa41ad4b77a87e8
URL:    http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=eb8551205f651263f6c7cdf3afa41ad4b77a87e8

Author: Richard Good <richard.good at smilecoms.com>
Committer: Richard Good <richard.good at smilecoms.com>
Date:   Wed Mar  5 13:40:24 2014 +0200

modules/ims_charging: updated documentation for new parameter: single_ro_session_per_dialog

---

 modules/ims_charging/doc/ims_charging_admin.xml |   28 ++++++++++++++++++++++-
 1 files changed, 27 insertions(+), 1 deletions(-)

diff --git a/modules/ims_charging/doc/ims_charging_admin.xml b/modules/ims_charging/doc/ims_charging_admin.xml
index a6ef005..7fd6b89 100644
--- a/modules/ims_charging/doc/ims_charging_admin.xml
+++ b/modules/ims_charging/doc/ims_charging_admin.xml
@@ -338,6 +338,28 @@ modparam("ims_charging", "cdp_event_latency_log", 1)
     </section>
     <section>
       <title>
+      <varname>single_ro_session_per_dialog</varname>(integer)</title>
+      <para>This tells the module whether it should do a single ro session per dialog no matter 
+	  how many times Ro_send_CCR is called from the config file or initiate an ro session 
+	  each time Ro_send_CCR is called.  It is useful for IMS charging where you might want 
+	  to  charge for on-net originating and off-net originating calls but always have only 
+	  a single ro session.
+      </para>
+      <para>
+        <emphasis>Default value is 0.</emphasis>
+      </para>
+      <example>
+        <title>
+        <varname>single_ro_session_per_dialog</varname>parameter usage</title>
+        <programlisting format="linespecific">
+...
+modparam("ims_charging", "single_ro_session_per_dialog", 1)
+...
+        </programlisting>
+      </example>
+    </section>
+    <section>
+      <title>
       <varname>origin_host</varname>(string)</title>
       <para>Origin host to be used in Diameter messages to charging-server.</para>
       <para>
@@ -519,7 +541,7 @@ modparam("ims_charging", "service_context_id_release", "262")
     <section>
       <title>
         <function moreinfo="none">Ro_CCR(route_name, direction, charge_type, unit_type,
-        reservation_units)</function>
+        reservation_units, domain</function>
       </title>
       <para>Perform a CCR on Diameter Ro interface for Charging</para>
       <para>Meaning of the parameters is as follows:</para>
@@ -549,6 +571,10 @@ modparam("ims_charging", "service_context_id_release", "262")
           <emphasis>reservation_units</emphasis>how many units (at the moment seconds) should be
           reservated at the moment.</para>
         </listitem>
+	<listitem>
+          <para><emphasis>domain</emphasis>- Logical domain within
+          registrar.</para>
+        </listitem>
       </itemizedlist>
       <para>This function can be used from REQUEST_ROUTE.</para>
       <para>This method is executed asynchronously. See example on how to retrieve return