Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
billing-action { edr edr_format_name [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius | rf } +
edr edr_format_name [ wait-until-flow-ends ]
edr_format_name must be the name of an existing EDR format, and must be a string of 1 through 63 characters in length.
Important: If the EDR format name supplied here is not configured in the EDR Format Configuration Mode, or has been deleted, the system accepts it without applying any EDR format for the billing action in this ACS service.
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.
To generate an eG-CDR the accounting-mode CLI command in the APN Configuration Mode must be configured with the “none” option.
The format of enhanced G-CDRs is controlled by the inspector CLI command in Context Configuration Mode.
coupon_id must be an integer from 0 through 65535.
Important: This rating-group overrides the content ID, if present in the same charging-action for the prepaid customer in DCCA. But only the content IDs will be used in eG-CDRs irrespective of the presence of rating-group in that charging-action.
units is the value set for charging unit, and must be an integer from 1 through 65535.
Important: For more information on content ID, refer to the
if-protocol command in the
Ruledef Configuration Mode Commands chapter.
charge-volume { protocol { bytes | packet-length | packets } [ downlink | uplink ] | constant value }
Default: charge-volume ip bytes
protocol must be one of the following:
•
|
dns: Charge volume for DNS
|
•
|
http: Charge volume for HTTP
|
•
|
icmp: Charge volume for ICMP
|
•
|
imap: Charge volume for Internet Message Access Protocol (IMAP)
|
•
|
mms: Charge volume for MMS
|
•
|
pop3: Charge volume for POP3
|
•
|
rtp: Charge volume for RTP
|
•
|
rtsp: Charge volume for RTSP
|
•
|
sdp: Charge volume for SDP
|
•
|
sip: Charge volume for SIP
|
•
|
smtp: Charge volume for SMTP
|
•
|
tcp: Charge volume for TCP
|
•
|
udp: Charge volume for UDP
|
•
|
wsp: Charge volume for WSP
|
•
|
wtp: Charge volume for WTP
|
units is the value set for charging, and must be an integer from 0 through 65535.
If constant 3 is configured for every invocation of this Charging Action, the system adds 3 to the downlink/uplink volume counter, depending on the direction of packet.
If charge-volume rtp packets is configured, system computes volume amounts for different options for RTP as follows:
Important: Whenever service counts volume, it counts all packets that the relevant analyzers accepted.
Important: If a TCP packet is routed to the HTTP analyzer but there is no HTTP payload, then the TCP statistics will be updated but the HTTP statistics will not be updated (except for the “packets ignored by the HTTP analyzer” statistic).
content_id is the content ID specified for credit control service in an active charging service, and must be an integer from 1 through 65535.
If the specified Ruledef uses the if-protocol command to select a value for content ID, then the
content_id specified through this command is not used for billing record generation.
Important: For more information on
content-id, refer to the
if-protocol command in the
Ruledef Configuration Mode Commands chapter.
flow action { conditional user-agent end-token end_token_name | discard [ downlink | uplink ] | random-drop interval interval_start to interval_end pkts-to-drop packet_min to packet_max | readdress [ server ip_address ] [ port port_number ] | terminate-flow | terminate-session }
end_token_name must be an alpha and/or numeric string of 1 through 32 characters in length, and is configured with this command to end the redirection condition.
downlink: Discards only downlink packets.
uplink: Discards only uplink packets.
random-drop interval interval_start to interval_end pkts-to-drop packet_min to packet_max
interval_start to interval_end: Specifies the random drop interval, in seconds, at which the voice packets will be dropped.
interval_start and
interval_end must be integers from 1 through 999.
pkts-to-drop packet_min to packet_max: Specifies the number of voice packets to be dropped at a time in a flow when the packets have to be dropped.
packet_min and
packet_max must be integers from 1 through 100.
readdress { server ip_address [ port port_number ] | port port_number }
ip_address must be the re-address server’s IP address, and must be an IPv4 address.
port_number must be the re-address server’s port number, and must be an integer from 1 through 65535.
When a re-address server is configured for a charging action, the show configuration command will show the readdress related configuration only if server address is configured. And the
show configuration verbose command will show the readdress sever if configured, else will display “no flow action”.
redirect-url url/%3furl=dynamic_field
url must be a string size of from 1 through 511 characters in http://search.com/subtarg/%3furl=#
HTTP.URL# format.
%3furl=: specifies the delimiter “?url=” between URLs.
dynamic_field indicates the dynamic fields for redirect URLs.
This would mean any SIP request that hits the sip_req ruledef, would get redirected to the url given in
ca_sip_redir. This involves creating a redirection packet with the following response line and “Contact” header in the response.
idle-timeout idle_timeout
idle_timeout must be an integer from 0 through 86400.
downlink: Flow of data towards subscriber.
uplink: Flow of data from subscriber.
bps must be an integer from 1 through 4294967295.
bytes must be an integer from 1 through 4294967295.
Important: It is recommended that this parameter be configured to at least the greater of the following two values: 1) 3 times greater than packet MTU for the subscriber connection, OR 2) 3 seconds worth of token accumulation within the “bucket” for the configured peak-data-rate.
discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the IP precedence
bps must be an integer from 1 through 4294967295.
bytes must be an integer from 1 through 4294967295.
discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
Important: This keyword is only available in StarOS 8.1 and later releases.
Important: If the exceed/violate action is set to “lower-ip-precedence”, the TOS value for the outer packet becomes “best effort” for packets that exceed/violate the traffic limits regardless of what the
ip user-datagram-tos copy command is configured to. In addition, the
lower-ip-precedence option may also override the
ip qos-dscp command configuration. Therefore, it is recommended that command not be used when specifying this option.
The following command sets an uplink peak data rate of 128000 bps and lowers the IP precedence when the committed-data-rate and the peak-data-rate are exceeded:
The following command sets a downlink peak data rate of 256000 bps and discards the packets when the committed-data-rate and the peak-data-rate are exceeded:
limit must be an integer from 1 through 4000000000.
Triggers the action of action_type on exceeding
limit for a flow type.
action_type must be one of the following:
discard: Discards the packets
redirect-url: Redirects the flow
terminate-flow: Terminates the flow to which this packet belongs
terminate-session: Terminates the session to which this packet belongs
Important: In StarOS 8.1 and later releases, this keyword is
lower-bits tos_value. In StarOS 8.0, it is
tos_value.
tos_value must be an integer from 0 through 63.
range must be an integer from 1 through 4094.
ipv4_address must be the next-hop forwarding address for this charging action, and must be specified using the standard IPv4 dotted decimal notation.
Important: This command is controlled by the dynamic-qos-renegotiation license.
priority specifies the traffic handling priority, and must be an integer from 1 through 3.
packet_filter_name specifies the packet filter’s name, and must be a string of 1 through 63 characters in length.
Important: In StarOS 8.1 and later releases, this keyword is
lower-bits tos_value. In StarOS 8.0, it is
tos_value.
value must be an integer from 0 through 63.
Important: This command is license dependent. For more information please contact your local sales representative.
format_name must be a string of 1 through 63 characters in length.
Also, see xheader-format CLI command in the
Active Charging Service Configuration Mode and the
x-header Format Configuration Mode Commands chapters.