Cisco Cisco ASR 5700
ACS Rulebase Configuration Mode Commands
▀ override-control
▄ Command Line Interface Reference, StarOS Release 17
740
Important:
In this release, both Inheritance and the Override Control features will be supported. Note that both
these two features should not be enabled simultaneously. If by mistake, both these features are enabled, only Override
Control is applied.
Control is applied.
The Gx interface is updated to include custom AVPs for the PCRF to send override values to P-GW. These
override values may be sent for all rules (wildcard) or for specific rule(s) or for charging action(s). In case the
override values are sent for a charging action, a rule or some of the rules may be excluded from using the
override values by sending the rules names in the Gx message. The override values will be check pointed and
recovered in case of either standalone recovery or ICSR.
This Override Control feature is expected to maintain existing active calls using inheritance post upgrade.
Inheritance feature and Override control should not be enabled simultaneously. It is necessary that
Inheritance feature be turned off once Override Control feature is enabled. Override Control once enabled
will apply only to new calls and does not effect existing calls.
Override Control feature allows the customer to dynamically modify the parameters of static or predefined
rules with parameters sent by PCRF over the Gx interface.
When multiple overrides are received from PCRF, the following is the priority in which they are applied:
override values may be sent for all rules (wildcard) or for specific rule(s) or for charging action(s). In case the
override values are sent for a charging action, a rule or some of the rules may be excluded from using the
override values by sending the rules names in the Gx message. The override values will be check pointed and
recovered in case of either standalone recovery or ICSR.
This Override Control feature is expected to maintain existing active calls using inheritance post upgrade.
Inheritance feature and Override control should not be enabled simultaneously. It is necessary that
Inheritance feature be turned off once Override Control feature is enabled. Override Control once enabled
will apply only to new calls and does not effect existing calls.
Override Control feature allows the customer to dynamically modify the parameters of static or predefined
rules with parameters sent by PCRF over the Gx interface.
When multiple overrides are received from PCRF, the following is the priority in which they are applied:
Rule level override control
Charging action level override control
Wildcard level override control
When installing a predef rule, if override control is received for that predef rule and QCI/ARP is overridden,
then the new overridden QCI/ARP values are used for bearer binding of the predef rule. If the QCI/ARP is
not overridden, then the values configured in charging action is used. The override charging and policy
parameters received from PCRF will continue to apply for the entire duration of the call. These values may be
modified by PCRF by sending the modified values with the same override control criteria (Rule name(s),
Charging Action Name(s) and Exclude Rule(s)). Any change in the Override Control criteria will be
interrupted as a new OC. There can only be one wildcard OC installed for a subscriber.
then the new overridden QCI/ARP values are used for bearer binding of the predef rule. If the QCI/ARP is
not overridden, then the values configured in charging action is used. The override charging and policy
parameters received from PCRF will continue to apply for the entire duration of the call. These values may be
modified by PCRF by sending the modified values with the same override control criteria (Rule name(s),
Charging Action Name(s) and Exclude Rule(s)). Any change in the Override Control criteria will be
interrupted as a new OC. There can only be one wildcard OC installed for a subscriber.