для Cisco Cisco Packet Data Gateway (PDG)
Configuring the dynamic-only keyword causes the configuration to be defined, but not enabled. If enabled,
the action associated with this option will not be matched against a flow until it is enabled from a dynamic
charging interface like Gx. Gx can disable or enable this action entry in the rulebase using Gx messages.
the action associated with this option will not be matched against a flow until it is enabled from a dynamic
charging interface like Gx. Gx can disable or enable this action entry in the rulebase using Gx messages.
Default: Disabled
adc
Specifies the ruledef to-be given as ADC rule. This keyword is optional and only visible when configured
with the dynamic-only keyword.
with the dynamic-only keyword.
Default: Disabled
mute
Disables application reporting to PCRF. This keyword is optional and visible only after configuring the adc
keyword.
keyword.
Default: Disabled
static-and-dynamic
The static-and-dynamic option causes the configuration to be defined and enabled, and allows a dynamic
protocol (such as the Gx interface) to disable or re-enable the configuration.
protocol (such as the Gx interface) to disable or re-enable the configuration.
Default: Enabled
When R7 Gx is enabled, "static-and-dynamic" rules behave exactly like "dynamic-only" rules. That is,
they must be activated explicitly by the Policy and Charging Rules Function (PCRF). When Gx is not
enabled, "static-and-dynamic" rules behave exactly like static rules.
they must be activated explicitly by the Policy and Charging Rules Function (PCRF). When Gx is not
enabled, "static-and-dynamic" rules behave exactly like static rules.
Important
timedef timedef_name
This keyword is only available in StarOS 8.1 and StarOS 9.0 and later releases.
Important
Associates the specified time definition with the ruledef / group-of-ruledefs. Timedefs activate or deactivate
ruledefs / groups-of-ruledefs, making them available for rule matching only when they are active.
ruledefs / groups-of-ruledefs, making them available for rule matching only when they are active.
timedef_name must be the name of a timedef, and must be an alphanumeric string of 1 through 63 characters.
A timedef can be used with several ruledefs / group-of-ruledefs. When a packet is received, and a ruledef /
group-of-ruledefs is eligible for rule matching, if a timedef is associated with the ruledef / group-of-ruledefs,
before rule matching the packet-arrival time is compared with the timeslots configured in the timedef. If the
packet arrived in any of the timeslots configured in the associated timedef, rule matching is undertaken, else
the next ruledef / group-of-ruledefs is considered.
group-of-ruledefs is eligible for rule matching, if a timedef is associated with the ruledef / group-of-ruledefs,
before rule matching the packet-arrival time is compared with the timeslots configured in the timedef. If the
packet arrived in any of the timeslots configured in the associated timedef, rule matching is undertaken, else
the next ruledef / group-of-ruledefs is considered.
The time considered for timedef matching is the system's local time.
Important
Command Line Interface Reference, Modes A - B, StarOS Release 19
590
ACS Rulebase Configuration Mode Commands
action priority