Cisco Cisco ASR 5700
ACS Charging Action Configuration Mode Commands
billing-action ▀
Command Line Interface Reference, StarOS Release 17 ▄
389
If this option is configured, the system generates an EDR immediately when a packet is received and it
matches a ruledef that is associated with this charging action. Other events configured for flow end-condition,
flow action, termination, and/or session control also create the triggers for EDR generation.
matches a ruledef that is associated with this charging action. Other events configured for flow end-condition,
flow action, termination, and/or session control also create the triggers for EDR generation.
wait-until-flow-ends
: By default, the EDR is generated immediately after a ruledef hit results in this
charging action. When this keyword is specified, no EDR is generated on a ruledef hit. When the flow ends,
an attempt is made to generate an EDR with the format specified.
an attempt is made to generate an EDR with the format specified.
create-edrs { charging-edr charging_edr_format_name | reporting-edr
reporting_edr_format_name } + [ wait-until-flow-ends ]
reporting_edr_format_name } + [ wait-until-flow-ends ]
Important:
This option is available only in 12.2 and later releases.
Enables EDR billing for packets matching this charging action.
charging-edr charging_edr_format_name
: Specifies to generate charging EDR.
charging_edr_format_name
must be the name of a charging EDR format, and must be an
alphanumeric string of 1 through 63 characters.
reporting-edr reporting_edr_format_name
: Specifies to generate reporting EDR.
reporting_edr_format_name
must be the name of a reporting EDR format, and must be an
alphanumeric string of 1 through 63 characters.
If the above options are configured, the system generates an EDR immediately when a packet is received and
it matches a ruledef that is associated with this charging action. Other events configured for flow end-
condition, flow action, termination, and/or session control also creates the triggers for EDR generation.
it matches a ruledef that is associated with this charging action. Other events configured for flow end-
condition, flow action, termination, and/or session control also creates the triggers for EDR generation.
wait-until-flow-ends
: By default, the EDR is generated immediately after a ruledef hit results in
this charging action. When this keyword is specified, no EDR is generated on a ruledef hit. When
the flow ends, an attempt is made to generate an EDR with the format specified.
the flow ends, an attempt is made to generate an EDR with the format specified.
egcdr
Enables eG-CDR billing for packets matching this charging action.
If this option is configured, the system generates an eG-CDR when the subscriber session ends or an interim
trigger condition occurs. The interim triggers are configurable in the ACS Rulebase Configuration Mode. In
addition, whenever there is an SGSN-to-SGSN handoff the system treats that as a trigger.
To generate an eG-CDR the
If this option is configured, the system generates an eG-CDR when the subscriber session ends or an interim
trigger condition occurs. The interim triggers are configurable in the ACS Rulebase Configuration Mode. In
addition, whenever there is an SGSN-to-SGSN handoff the system treats that as a trigger.
To generate an eG-CDR the
accounting-mode
command in the APN Configuration Mode must be
configured with the “none” option.
The format of enhanced G-CDRs is controlled by the
The format of enhanced G-CDRs is controlled by the
inspector
CLI command in the Context
Configuration Mode.
exclude-from-udrs
By default, statistics are accumulated on a per content ID basis for possible inclusion in UDRs. The
exclude-from-udrs
keyword causes the system to not include the packet’s statistics in UDRs.
When this option is disabled, (the default setting) UDRs will be generated based on the UDR format specified
in the rulebase.
Default: Disabled.
in the rulebase.
Default: Disabled.
radius
Enables billing action as RADIUS Charging Data Records (CDRs) for packets matching this charging action,
and the data packet statistics will be included in the postpaid RADIUS accounting.
Default: Disabled.
and the data packet statistics will be included in the postpaid RADIUS accounting.
Default: Disabled.