This command allows
you to specify the purpose of setting up a group-of-ruledefs as
either charging, post-processing, or for other purposes.
Privilege:
Security Administrator,
Administrator
Syntax
group-of-ruledefs-application { charging | content-filtering | gx-alias | post-processing }
no group-of-ruledefs-application
no
If previously configured,
deletes the group-of-ruledefs-application configuration from the current
group-of-ruledefs.
charging
Specifies that the
current group-of-ruledefs is for charging purposes.
content-filtering
Specifies
that the current group-of-ruledefs is for content-filtering purposes.
gx-alias
Specifies
that the current group-of-ruledefs is for Gx-alias purposes.
post-processing
Specifies that the
current group-of-ruledefs is for post-processing purposes, that
is, for use by the post-processing CLI
command or automatic name-matching to the Diameter Filter-Id AVPs.
Usage:
Use this command to
specify the purpose of setting up a group-of-ruledefs. If not specified,
by default the rule-application type will be charging.
If the group-of-ruledefs-application
is configured for content-filtering, no ruledef can be added to
it. Similarly, if configured explicitly for charging or post-processing,
a content-filtering policy cannot be configured in it.
The
group-of-ruledefs may be dynamically selected by Diameter, as described
by the policy-control
charging-rulebase-name command in the Active Charging
Service Configuration Mode. If so selected, the priority field of
the add-ruledef instances within the group-of-ruledefs are ignored,
and all of the rules named by the ruledef keyword that are also
configured with the same name in the action command
are selected.
Example:
The following command
configures the current group-of-ruledefs as for post-processing purposes:
group-of-ruledefs-application
post-processing