▀ Configuring Pre-paid Billing With Custom Behavior
Configuring Pre-paid Billing With Custom Behavior
This section describes how to enable Pre-paid billing support with custom behavior.
Important:
RADIUS attributes take precedence.
Important:
parameters for a local subscriber from the CLI, these settings have no effect on a subscriber session.
Important:
that the most common or likely commands and/or keyword options are presented. In many cases, other optional
commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete
information regarding all commands.
Enable custom pre-paid billing for the default subscriber by applying the following example configuration:
configure
context <context_name>
subscriber default
prepaid custom
end
Enable custom pre-paid billing for the default subscriber of a domain alias by applying the following example
configuration:
configure
context <context_name>
subscriber name <alias_def_sub>
prepaid custom
end
Notes:
Optional: To have custom pre-paid byte credits based on the flow of compressed traffic, use the following
command:
prepaid custom byte-count compressed
Optional: Set the low-watermark for remaining byte credits. This is a percentage of the subscriber session's total
credits. When the low-watermark is reached a new RADIUS access-request is sent to the RADIUS server to
retrieve more credits. To set the low watermark percentage, enter the following command:
prepaid custom low-watermark percent <percentage>
▄ Cisco ASR 5000 IP Services Gateway Administration Guide
152
If RADIUS attributes are present that conflict with the custom pre-paid settings, the values set by the
Pre-paid billing support is not available for local subscribers. Even though you can set pre-paid
Commands used in the configuration samples in this section provide base functionality to the extent
Pre-paid Billing
OL-27210-02