Skip to content

Commit

Permalink
carrierroute: docs - removed trailing spaces
Browse files Browse the repository at this point in the history
  • Loading branch information
@miconda
miconda committed Nov 13, 2023
1 parent 3d864d6 commit 3a2de01
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 21 deletions.
34 changes: 17 additions & 17 deletions src/modules/carrierroute/doc/carrierroute_admin.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ modparam("carrierroute", "subscriber_user_col", "username")
<section>
<title><varname>subscriber_domain_col</varname> (string)</title>
<para>
The name of the column in the subscriber table containing the domain of
The name of the column in the subscriber table containing the domain of
the subscriber.
</para>
<para>
Expand Down Expand Up @@ -304,8 +304,8 @@ modparam("carrierroute", "fetch_rows", 3000)
<section>
<title><varname>db_load_description</varname> (integer)</title>
<para>
Toggle on/off loading in memory the description column in the
carrierroute/carrierfailureroute database tables. This reduces the
Toggle on/off loading in memory the description column in the
carrierroute/carrierfailureroute database tables. This reduces the
shared memory used by the module.
</para>
<para>
Expand Down Expand Up @@ -350,7 +350,7 @@ modparam("carrierroute", "match_mode", 10)
<section>
<title><varname>avoid_failed_destinations</varname> (integer)</title>
<para>
Integer parameter to toggle on/off the possibility that in the failurerouting cases
Integer parameter to toggle on/off the possibility that in the failurerouting cases
destinations that previously failed are avoided. Possible values are 0 (off), 1 (on).
Also see cr_route section.
</para>
Expand Down Expand Up @@ -470,7 +470,7 @@ cr_tree_rewrite_uri(tree, domain)
<itemizedlist>
<listitem>
<para>
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
string containing either carrier id (nummeric) or carrier name (arbitrary string).
It also accepts any pseudo-variable as input.
</para>
Expand Down Expand Up @@ -545,7 +545,7 @@ cr_tree_rewrite_uri(tree, domain)
<itemizedlist>
<listitem>
<para>
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
string containing either carrier id (nummeric) or carrier name (arbitrary string).
It also accepts any pseudo-variable as input.
</para>
Expand Down Expand Up @@ -613,7 +613,7 @@ cr_tree_rewrite_uri(tree, domain)
<itemizedlist>
<listitem>
<para>
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
<emphasis>carrier</emphasis> - The routing tree to be used. It must be
string containing either carrier id (nummeric) or carrier name (arbitrary string).
It also accepts any pseudo-variable as input.
</para>
Expand All @@ -627,7 +627,7 @@ cr_tree_rewrite_uri(tree, domain)
</listitem>
<listitem>
<para><emphasis>prefix_matching</emphasis> - User name to be used for prefix matching
in the routing tree.
in the routing tree.
It also accepts any pseudo-variable as input.
</para>
</listitem>
Expand Down Expand Up @@ -663,7 +663,7 @@ cr_tree_rewrite_uri(tree, domain)
route {
# route calls based on hash over callid
# choose route domain 0 of the default carrier

if(!cr_route("default", "0", "$rU", "$rU", "call_id")){
sl_send_reply("403", "Not allowed");
} else {
Expand Down Expand Up @@ -806,14 +806,14 @@ domain register {
<section>
<title>Database setup</title>
<para>
Before running &kamailio; with carrierroute, you have to setup the database
table where the module will store the routing data. For that, if
Before running &kamailio; with carrierroute, you have to setup the database
table where the module will store the routing data. For that, if
the table was not created by the installation script or you choose
to install everything by yourself you can use the carrierroute-create.sql
<acronym>SQL</acronym> script in the database directories in the
kamailio/scripts folder as template.
Database and table name can be set with module parameters so they
can be changed, but the name of the columns must be as they are
<acronym>SQL</acronym> script in the database directories in the
kamailio/scripts folder as template.
Database and table name can be set with module parameters so they
can be changed, but the name of the columns must be as they are
in the <acronym>SQL</acronym> script.
You can also find the complete database documentation on the
project webpage, &kamailiodbdocs;.
Expand Down Expand Up @@ -859,7 +859,7 @@ domain register {
support the user specific carrier lookup. The routing rules for carrier 1
and carrier 2 for the <quote>49</quote> prefix contains an additional rule
with the domain 2, that can be used for example as fallback if the gateways
in domain 1 are not reachable. Two more fallback rules (domain 3 and 4) for
in domain 1 are not reachable. Two more fallback rules (domain 3 and 4) for
carrier 1 are also supplied to support the functionality of the carrierfailureroute
table example that is provided in the next section.
</para>
Expand Down Expand Up @@ -971,7 +971,7 @@ domain register {
<para>Suggested changes:</para>
<programlisting format="linespecific">
...
ALTER TABLE subscriber ADD cr_preferred_carrier int(10) default NULL;
ALTER TABLE subscriber ADD cr_preferred_carrier int(10) default NULL;
...
</programlisting>
</example>
Expand Down
8 changes: 4 additions & 4 deletions src/modules/carrierroute/doc/carrierroute_db.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ modparam("carrierroute", "carrierroute_flags_col", "flags")
</section>
<section>
<title><varname>carrierroute_mask_col</varname> (string)</title>
<para>This column contains the mask that is applied to the message flags before rule
<para>This column contains the mask that is applied to the message flags before rule
matching.</para>
<example>
<title>Set <varname>carrierroute_mask_col</varname> parameter</title>
Expand All @@ -136,8 +136,8 @@ modparam("carrierroute", "carrierroute_mask_col", "mask")
traffic shall be routed to gateway A, the other 30 % shall be routed to
gateway B, we define a rule for gateway A with a prob value of 0.7 and a
rule for gateway B with a prob value of 0.3.


If all probabilities for a given prefix, tree and domain don't add to 100%,
the prefix values will be adjusted according the given prob values. E.g. if
three hosts with prob values of 0.5, 0.5 and 0.4 are defined, the resulting
Expand Down Expand Up @@ -276,7 +276,7 @@ modparam("carrierroute", "carrierfailureroute_domain_col", "domain")
<para>Name of column contains the scan prefixes. Scan prefixes define the matching
portion of a phone number, e.g. we have the scan prefixes 49721 and 49, the called number is
49721913740, it matches 49721, because the longest match is taken. If no prefix matches,
the number is not failure routed. To prevent this, an empty prefix value of
the number is not failure routed. To prevent this, an empty prefix value of
could be added.</para>
<example>
<title>Set <varname>carrierfailureroute_scan_prefix_col</varname> parameter</title>
Expand Down

0 comments on commit 3a2de01

Please sign in to comment.