Cisco Cisco ASR 5700
ACS Charging Action Configuration Mode Commands
▀ flow action
▄ Command Line Interface Reference, StarOS Release 17
404
Specifies the round-robin approach to select the server list from the readdress server list. This is the
default approach.
default approach.
discard-on-failure
Important:
This option is available only in StarOS 14.0 and later releases.
Specifies to discard the packets if readdressing fails due to duplicate key. If this keyword is not
configured, no action is taken and the packets are allowed to pass.
configured, no action is taken and the packets are allowed to pass.
If already configured, to revert the behavior, configure the
flow action readdress
command
again without the
discard-on-failure
keyword.
dns-proxy-bypass
Important:
This option is available only in StarOS 12.3 and later releases.
Specifies the DNS packets to bypass interception at the session manager when readdressing for flow
occurs, and go through ECS-based DNS redirection. If this keyword is not configured, DNS
redirection from ECS is disabled.
occurs, and go through ECS-based DNS redirection. If this keyword is not configured, DNS
redirection from ECS is disabled.
redirect-ocs-url
Important:
This option is available only in StarOS 12.3 and later releases.
Specifies to redirect to the URL provided by OCS only for post-processing dynamic rules.
redirect-url redirect_url [ [ encryption { blowfish128 | blowfish64 } | { {
aes128 | aes256 } [salt] } } [ encrypted ] key key ] [ clear-quota-retry-timer ]
[ first-request-only [ post-redirect { allow | discard | terminate } ] ] ]
aes128 | aes256 } [salt] } } [ encrypted ] key key ] [ clear-quota-retry-timer ]
[ first-request-only [ post-redirect { allow | discard | terminate } ] ] ]
Specifies to return a redirect response to the subscriber, and terminate the TCP connections (to the subscriber
and server). The subscriber's Web browser should automatically send the original HTTP packet to the
specified URL. Redirection is only possible for certain types of HTTP packets (for example, GET requests),
which typically are only sent in the uplink direction. If the flow is not HTTP, the
and server). The subscriber's Web browser should automatically send the original HTTP packet to the
specified URL. Redirection is only possible for certain types of HTTP packets (for example, GET requests),
which typically are only sent in the uplink direction. If the flow is not HTTP, the
redirect-url
option is
ignored, that is the packet is forwarded normally, except for SIP. For SIP, a Contact header with the redirect
information is inserted.
The redirect-url consists of the redirect url and may additionally include one or more dynamic fields. Earlier,
the dynamic fields could be encrypted using 128 and 256 bit blowfish encryption. The new functionality
provides the additional AES-CBC encryption ofthe dynamic fields as well.
information is inserted.
The redirect-url consists of the redirect url and may additionally include one or more dynamic fields. Earlier,
the dynamic fields could be encrypted using 128 and 256 bit blowfish encryption. The new functionality
provides the additional AES-CBC encryption ofthe dynamic fields as well.
redirect_url
specifies the redirect URL.
redirect_url
must be an alphanumeric string of 1
through 511 characters. It may include one or more dynamic fields (up to 16 may be specified). For
example, http://search.com/subtarg=#HTTP.URL#.
example, http://search.com/subtarg=#HTTP.URL#.
Dynamic fields must be enclosed in “#” (hash).
Up to 16 dynamic fields out of the following 23 are allowed:
#BEARER.CALLED-STATION-ID#
#BEARER.CALLING-STATION-ID#
#BEARER.NAS-IP-ADDRESS#
#BEARER.USER-NAME#