Charging Action Configuration Mode Commands


Charging Action Configuration Mode Commands
 
 
The Charging Action Configuration Mode is used to create and manage Charging Action services.
 
Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
 
billing-action
This command configures billing actions for packets that match ruledefs.
Product
All
Privilege
Security Administrator, Administrator
Syntax
billing-action { edr edr_format_name [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius | rf } +
no billing-action [ edr | egcdr | exclude-from-udrs | radius | rf ] +
no
Disables billing-action configuration for the charging action.
Specifying one of the optional keywords disables that functionality. If you want to disable all billing-action functionality, do not specify any of the optional keywords.
edr edr_format_name [ wait-until-flow-ends ]
Enables EDR billing for packets matching this charging action.
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.
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 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.
egcdr
Enables eG-CDRs billing for packets matching this charging action.
If this option is configured, system generates an eG-CDR when the subscriber session ends or an interim trigger condition occurs. The interim triggers are configurable in the 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 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.
exclude-from-udrs
Default: Disabled.
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 declared in the rulebase.
radius
Default: Disabled.
Enables billing action as RADIUS CDRs for packets matching this charging action, and the data packet statistics will be included in the postpaid RADIUS accounting.
rf
Enables Rf accounting.
Rf accounting is applicable only for dynamic and predefined rules that are marked for it. Dynamic rules have a field offline-enabled to indicate this. To mark a predefined rule as offline-enabled, use this keyword and the billing-records CLI in the Rulebase Configuration Mode.
Usage
Use this command to enable an EDR, eG-CDR and/or RADIUS CDR type of billing for content matching this charging action.
Example
The following command enables the EDR billing type with EDR format charge1_format:
billing-action edr charge1_format
 
cca charging
This command enables Credit Control Application and configures RADIUS/Diameter prepaid charging behavior.
Product
All
Privilege
Security Administrator, Administrator
Syntax
cca charging credit [ preemptively-request | rating-group coupon_id ]
{ default | no } dcca charging
no
Disables RADIUS/Diameter Prepaid Credit Control Charging.
default
Disables RADIUS/Diameter Prepaid Credit Control Charging.
credit
Specifies RADIUS/Diameter Prepaid Credit Control Charging Credit behavior.
preemptively-request
Specifies RADIUS/Diameter prepaid credit preemptively requested charging credit behavior. If this option is used, a quota is requested for the specific type of content during the session initialization.
rating-group coupon_id
Specifies the coupon ID used in prepaid charging as rating-group which maps to the coupon ID for prepaid customer.
coupon_id must be an integer from 0 through 65535.
This option also assigns different content-types for the same charging action depending upon whether prepaid is enabled or not.
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.
Usage
Use this command to configure RADIUS/Diameter Prepaid Credit Control Charging behavior.
This command selects reservation based credit control. A CCR-Initial is used to reserve quota upon the first traffic, then a series of CCR-updates are issued as the traffic proceeds and quota dwindles. A CCR-Terminate is issued at the end of the session or at the end of the quota-hold-time.
Example
cca charging credit
 
charge-units
This command configures the unit amount counters for RADIUS/DCCA charging calculation.
Product
GGSN
Privilege
Security Administrator, Administrator
Syntax
charge-units units
{ default | no } charge-units
no
Disables the charge-units configuration.
default
Configures the default setting.
Default: 0; disables the counter, same as no charge-units
units
Sets the service-specific fixed unit counter per content ID for RADIUS/DCCA charging.
units is the value set for charging unit, and must be an integer from 1 through 65535.
Usage
This command configures the unit amount counters for charging calculation on per content ID basis for different protocols and packets regardless of packet direction (uplink or downlink).
Important: For more information on content ID, refer to the if-protocol command in the Ruledef Configuration Mode Commands chapter.
Example
The following command sets the charging unit to 1024:
charge-unit 1024
 
charge-volume
This command configures how the volume amount counter for eG-CDR and DCCA charging are calculated.
Product
All
Privilege
Security Administrator, Administrator
Syntax
charge-volume { protocol { bytes | packet-length | packets } [ downlink | uplink ] | constant value }
{ no | default } charge-volume
no
Disables the charge-volume configuration.
default
Configures the default setting.
Default: charge-volume ip bytes
protocol
Specifies the charge volume method for the specific rule definition.
protocol must be one of the following:
dns: Charge volume for DNS
ftp-control: Charge volume for FTP-Control
ftp-data: Charge volume for FTP-Data
http: Charge volume for HTTP
icmp: Charge volume for ICMP
imap: Charge volume for Internet Message Access Protocol (IMAP)
ip: Charge volume for IP
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
secure-http: Charge volume for secure-https
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
bytes
Sets charge volume for bytes.
packet-length
Sets charge volume for packet length.
packets
Sets charge volume for packets.
constant units
This sets the fixed increment value for charging.
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.
Usage
This command provides the method for charging volume calculation for different protocols and packets.
For information on supported protocols see the Ruledef Configuration Mode Commands chapter.
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).
Example
Following command sets the charging volume of downlink packets for RTP:
charge-volume rtp packets downlink
 
content-filtering processing server-group
This command enables/disables content filtering in the charging action.
Product
CF
Privilege
Security Administrator, Administrator
Syntax
content-filtering processing server-group
{ default | no } content-filtering processing
default
Configures the default setting.
Default: content filtering configured for the rulebase is attempted
no
Specifies to bypass content filtering.
This configuration should only be specified for charging actions that are performed when known safe sites are being accessed.
Usage
Use this command to enable/disable content filtering in the charging action.
This command works as second level filter to process the HTTP/WAP GET request with ICAP after ruledef matching. The first level filtering is in the rulebase configuration. This CLI command is only effective when the rulebase is configured with content-filtering mode server-group.
Example
The following command enables content filtering in the current charging action:
content-filtering processing server-group
 
content-id
This command specifies an optional content ID to use in the generated billing records, as well as the AVP used by the credit control application, such as the Rating-Group AVP for use by DCCA.
Product
All
Privilege
Security Administrator, Administrator
Syntax
content-id content_id
no content-id
no
Removes the content ID configuration from the charging action.
content_id
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.
Usage
This command specifies an optional content ID to use in the generated billing records. This identifier assists the carrier’s billing post processing and also used by credit-control system to use independent quotas for different value of content-id.
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.
Example
The following command sets the content ID in the current charging action to 23:
content-id 23
 
end
This command returns the CLI prompt to the Exec mode.
Product
All
Privilege
Security Administrator, Administrator
Syntax
end
Usage
Use this command to change to the Exec mode.
 
exit
This command exits the Charging Action Configuration mode and returns to the Active Charging Service Configuration mode.
Product
All
Privilege
Security Administrator, Administrator
Syntax
exit
Usage
Use this command to return to the Active Charging Service Configuration mode.
 
flow action
This command specifies the actions for packets that match a rule definition. This command also specifies action on packet and flow for Session Control functionality.
Product
All
Privilege
Security Administrator, Administrator
Syntax
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 }
no flow action
no
Disables the flow action configured in this charging action.
conditional user-agent end-token end_token_name
Conditionally redirects the HTTP packets matched to a configured user-agent to a specified URL. The user agent is configured using the redirect user-agent command in the Active Charging Service Configuration Mode.
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.
discard [ downlink | uplink ]
Discards the packet associated with this charging action.
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
Specifies random drop as a charging action to degrade voice quality.
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 }
Specifies the re-address server’s IP address/port number for this charging action. Enables readdressing of packets based on the destination IP address in the packets.
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.
terminate-flow
Specifies the flow action to terminate flow.
Terminates the TCP connection gracefully between the subscriber and external server and sends a TCP FIN to the subscriber and a TCP RST to the server. If the flow does not use TCP, this option simply discard the packets. This option is used for flows that use TCP only.
terminate-session
Specifies the flow action to terminate session.
When a rule pointing to a charging action configured with the terminate-session keyword is hit, then the corresponding session will be terminated.
Usage
Use this command to set the flow actions; e.g. discard, terminate, or conditional redirect.
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”.
Example
The following command sets the flow action to terminate:
flow-action terminate-flow
 
flow action redirect-url
This command specifies the redirection of URL for packets that matches a rule definition. This command also specifies the redirect-URL action on packet and flow for Session Control functionality.
Product
All
Privilege
Security Administrator, Administrator
Syntax
flow action redirect-url url/%3furl=dynamic_field [ clear-quota-retry-timer ]
{ default | no } flow action redirect-url
no
Disables the configured flow action in this charging action.
default
Disables the flow action and forward the packets normally.
redirect-url url/%3furl=dynamic_field
Redirects the HTTP packets matched to this Ruledef to the specified URL.
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.
Note that user cannot supply “?” through CLI so %3f is the value for “?”.
dynamic_field indicates the dynamic fields for redirect URLs.
Dynamic fields must be enclosed in '#'. Up to 16 dynamic fields are allowed in the redirect string.
Allowed dynamic fields are:
clear-quota-retry-timer
This option resets the Credit Control Application quota retry timer for specific subscriber upon redirection.
Usage
Use this command to set the redirection of URL as flow actions upon matching of a Ruledef.
This CLI can be used to redirect SIP requests as well. The following is a sample configuration:
configure
  active-charging service s1
     charging-action ca_sip_redir
        content-id 10
        flow action redirect-url sip:test@sip.org
        exit
     ruledef sip_req
        sip request packet = TRUE
        exit
     rulebase plan1
        action priority 08 ruledef sip_req charging-action ca_sip_redir
        /* other rules, routing rules for sip, etc */
        end
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.
SIP/2.0 302 Moved Temporarily
302 Moved Temporarily
Most of the header fields are copied directly from the request, so that the mandatory SIP headers are present. If content-length header was seen in the original message, it is replaced in the reply with ‘Content-Length: 0’.
Example
The following command resets quota retry timer upon redirection of flow to HTTP URL http://search.com/?url=#http://msn.com#:
flow action redirect-url http://search.com/%3url=#http://msn.com# clear-quota-retry-timer
 
flow idle-timeout
This command configures the maximum duration a flow can remain idle after which the system automatically terminates the flow.
Product
All
Privilege
Security Administrator, Administrator
Syntax
flow idle-timeout idle_timeout
{ no | default } idle-timeout
no
Disables the idle-timeout configuration; sets the idle-timeout to 0 seconds.
default
Configures the default setting.
Default: 300 seconds
idle-timeout idle_timeout
Specifies the maximum duration, in seconds, a flow can remain idle.
idle_timeout must be an integer from 0 through 86400.
Usage
Use this command to configure the maximum duration a flow can remain idle after which the system automatically terminates the flow.
Example
The following command configures the idle-timeout setting to 400 seconds:
flow idle-timeout 400
 
flow limit-for-bandwidth
This command enables and configures bandwidth limits for Session Control functionality to the subscriber. Uplink and downlink limits are configured separately.
Product
All
Privilege
Security Administrator, Administrator
Syntax
flow limit-for-bandwidth { { direction { downlink | uplink } peak-data-rate bps peak-burst-size bytes violate-action { discard | lower-ip-precedence } [ committed-data-rate bps committed-burst-size bytes [ exceed-action { discard | lower-ip-precedence } ] ] } | { id id } }
{ default | no } flow limit-for-bandwidth { direction { downlink | uplink } | id }
no
Disable bandwidth control traffic policing for the specified direction for the current subscriber.
default
Resets the bandwidth control policy to default mode.
direction { downlink | uplink }
Specifies the direction of flow downlink/uplink to apply bandwidth limit.
downlink: Flow of data towards subscriber.
uplink: Flow of data from subscriber.
peak-data-rate bps
Default: 256000
Specifies the peak data-rate for the subscriber, in bps (bits per second).
bps must be an integer from 1 through 4294967295.
peak burst-size bytes
Default: 3000
The peak burst size allowed, in bytes.
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.
violate-action { discard | lower-ip-precedence }
Default: Discard.
Specifies the action to take on packets that exceed both the committed-data-rate and the peak-data-rate. The following actions are supported:
discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the IP precedence
committed-data-rate bps
Default: 144000
The committed data rate (guaranteed-data-rate) in bps (bits per second).
bps must be an integer from 1 through 4294967295.
committed-burst-size bytes
Default: 3000
The committed burst size allowed, in bytes.
bytes must be an integer from 1 through 4294967295.
exceed-action { discard | lower-ip-precedence }
Default: lower-ip-precedence
The action to take on the packets that exceed the committed-data-rate but do not violate the peak-data-rate. The following actions are supported:
discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
If exceed-action is not configured, the packets are forwarded.
id id
Important: This keyword is only available in StarOS 8.1 and later releases.
Specifies identifier for bandwidth limiting, and must be an integer from 1 through 65535.
This identifier enables traffic policing based on a separate identifier other than content ID. This identifier will always take priority over content ID. If this identifier is not configured, traffic policing will be based on content ID.
Usage
Use this command to limit the bandwidth a subscriber uses in the uplink and downlink directions under Session Control.
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.
Details of the QoS Traffic Policing feature is available in the System Enhanced Feature Configuration Guide.
Example
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:
flow limit-for-bandwidth uplink peak-data-rate 128000 violate-action lower-ip-precedence
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:
flow limit-for-bandwidth downlink peak-data-rate 256000 violate-action discard
 
flow limit-for-flow-type
This command controls the action in the event of number of flows exceeds for a type of flow under Session Control feature.
Product
All
Privilege
Security Administrator, Administrator
Syntax
flow limit-for-flow-type limit over-limit-action action_type
[ no ] limit-for-flow-type
no
Disables limit for the total number of flow for a type.
limit
Sets the maximum number of flows of a type exceeding which action triggers.
limit must be an integer from 1 through 4000000000.
over-limit-action action_type
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
Usage
Use this command to control the action for the total number of flow of a type.
Example
The following command terminates the flow if total number of flows of a type exceeds 1024:
flow limit-for-flow-type 1024 over-limit-action terminate-flow
 
ip tos
This command sets the IP Type of Service (ToS) octets being used in the charging action.
Product
All
Privilege
Security Administrator, Administrator
Syntax
ip tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ uplink | downlink ]
no ip tos [ uplink | downlink ]
no
Disables IP ToS being used in the charging action.
afxx
Specifies the use of an assured forwarding xx PHB.
be
Specifies the use of best effort forwarding PHB.
ef
Specifies the use of expedited forwarding PHB.
lower-bits tos_value
Important: In StarOS 8.1 and later releases, this keyword is lower-bits tos_value. In StarOS 8.0, it is tos_value.
Sets the least-significant 6 bits in the TOS byte with the specified numeric value.
tos_value must be an integer from 0 through 63.
downlink
Specifies the ToS for downlink packets only.
uplink
Specifies the ToS for uplink packets only.
Usage
Use this command to set the IP Type of Service (ToS) octets used in the charging action. If one of the enumerated values is set, the DSCP bits which are the six most-significant bits in the TOS byte are marked. If the integer value is set, it will be written into the six least-significant bits of the TOS byte.
Example
The following command sets the IP ToS to be with downlink:
ip tos be downlink
 
ip vlan
This command configures the VLAN identifier to be associated with the IP address for the session.
Product
All
Privilege
Security Administrator, Administrator
Syntax
ip vlan range
{ default | no } ip vlan
default | no
These options delete or disable the IP VLAN configuration.
range
range must be an integer from 1 through 4094.
Usage
This command configures the subscriber VLAN ID which is used with the assigned address for the subscriber session to receive packets. If the IP pool from which the address is assigned is configured with a VLAN ID, then this subscriber configured VLAN ID overrides it.
Subscriber traffic can be routed to specific VLANs based on the configuration of their user profile. Using this functionality provides a mechanism for routing all traffic from a subscriber over the specified VLAN. All packets destined for the subscriber must also be sent using only IP addresses valid on the VLAN or they will be dropped.
Example
The following command sets the IP VLAN range to go up to 500:
ip vlan 500
The following command sets the IP VLAN range back to default.
default ip vlan
 
nexthop-forwarding-address
This command configures the next-hop forwarding address for this charging action.
Product
All
Privilege
Security Administrator, Administrator
Syntax
nexthop-forwarding-address ipv4_address
no nexthop-forwarding-address
no
Removes the next-hop forwarding address, if previously configured.
ipv4_address
ipv4_address must be the next-hop forwarding address for this charging action, and must be specified using the standard IPv4 dotted decimal notation.
Usage
Use this command to configure the next-hop forwarding address for a charging action. When an uplink packet matches a rule and a charging action is applied to it this next-hop forwarding address is used.
There are different methods to configure a next-hop forwarding address, they are prioritized as follows:
Example
The following command sets the next-hop forwarding address for the current charging action to 1.1.1.1:
nexthop-forwarding-address 1.1.1.1
 
qos-class-identifier
This command sets the QoS Class Identifier.
Product
All
Privilege
Security Administrator, Administrator
Syntax
qos-class-identifier identifier
no qos-class-identifier
no
Removes QoS Class Identifier, if previously configured.
identifier
Specifies the QoS Class Identifier, and must be an integer from 1 through 9.
Usage
Use this command to set the QoS Class Identifier.
Example
The following command sets the QoS Class Identifier as 3:
qos-class-identifier 3
 
qos-renegotiate
This command configures the QoS traffic class for the charging action for the Layer 7 QoS Renegotiation feature, enabling triggering QoS renegotiation from an active-charging rule.
Important: This command is controlled by the dynamic-qos-renegotiation license.
Product
All
Privilege
Security Administrator, Administrator
Syntax
qos-renegotiate traffic-class { background | conversational | interactive priority | streaming }
no qos-renegotiate
no
Removes any previously configured traffic class setting.
background
Specifies the traffic class as Background.
For traffic patterns in which the data transfer is not time-critical (for example e-mail exchange).
conversational
Specifies the traffic class as Conversational.
For traffic patterns in which there is a constant flow of packets.
interactive priority
Specifies the traffic class as Interactive.
For traffic patterns in which there is an intermittent flow of packets.
priority specifies the traffic handling priority, and must be an integer from 1 through 3.
streaming
Specifies the traffic class as Streaming.
For traffic patterns in which there is a constant flow of data in one direction, either upstream or downstream.
Usage
Use this command to configure the QoS traffic class for a charging action for the Layer 7 QoS Renegotiation feature, enabling triggering QoS renegotiation from an active-charging rule.
Layer 7 QoS Renegotiation is an extension of the Dynamic QoS Renegotiation feature. Upon matching a particular layer 7 rule, for example the access of a particular URL, the GGSN triggers the renegotiation of the PDP context.
Example
The following command sets the QoS traffic class for the charging action to streaming:
qos-renegotiate traffic-class streaming
 
retransmissions-counted
This command enables the charging action to count the number of retransmissions.
Product
All
Privilege
Security Administrator, Administrator
Syntax
[ no | default ] retransmissions-counted
no | default
Disables the count retries from the charging action.
Usage
Use this command to enable counting of the number of retransmissions.
Example
retransmissions-counted
 
service-identifier
This command configures the service identifier for a service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
service-identifier service_id
no service-identifier
no
Removes any previously configured service ID.
service_id
Specifies the service identifier, and must be an integer from 1 through 65535.
Usage
Use this command to configure the service identifier for a service.
Example
The following command sets the service identifier for a service as 99:
service-identifier 99
 
tft packet-filter
This command configures the packet filter to be sent to the MS.
Product
All
Privilege
Security Administrator, Administrator
Syntax
[ no ] tft packet-filter packet_filter_name
no
Removes the specified packet filter, if previously configured.
packet_filter_name
packet_filter_name specifies the packet filter’s name, and must be a string of 1 through 63 characters in length.
Usage
Use this command to configure the packet filter to be sent to the MS. Up to eight packet filters can be specified in a charging action.
Example
The following command configures the packet filter filter23 to be sent to the MS:
tft packet-filter filter23
 
tos
This command sets the Type of Service (ToS) octets used in the charging action.
Product
All
Privilege
Security Administrator, Administrator
Syntax
tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ downlink | uplink ]
no tos [ downlink | uplink ]
no
Disables the ToS being used in the charging action.
afxx
Specifies the use of an assured forwarding xx Per Hop Behavior (PHB).
be
Specifies use of Best Effort forwarding PHB.
ef
Specifies use of Expedited Forwarding PHB.
lower-bits tos_value
Important: In StarOS 8.1 and later releases, this keyword is lower-bits tos_value. In StarOS 8.0, it is tos_value.
Sets the least-significant 6 bits in the TOS byte with the specified numeric value.
value must be an integer from 0 through 63.
downlink
Specifies the ToS only for downlink packets.
uplink
Specifies the ToS only for uplink packets.
Usage
Use this command to set the ToS octets used in the charging action. If one of the enumerated values is set, the DSCP bits which are the six most-significant bits in the TOS byte are marked. If the integer value is set, it will be written into the six least-significant bits of the TOS byte.
Example
The following command sets the ToS to be for downlink packets:
tos be downlink
 
xheader-insert
This command specifies the extension-header (x-header) format name whose fields are to be inserted in HTTP GET and POST request packets.
Important: This command is license dependent. For more information please contact your local sales representative.
Product
All
Privilege
Security Administrator, Administrator
Syntax
xheader-insert xheader-format xheader_format_name [ first-request-only ] [ -noconfirm ]
no xheader-insert
no
Removes previously configured x-header format name.
xheader-format format_name
Enables x-header mode configuration, and specifies name of the x-header format whose fields are to be inserted in the packets.
format_name must be a string of 1 through 63 characters in length.
first-request-only
Specifies x-header insertion only for the first HTTP request in the IP flow. If not configured, the default behavior is insertion for all requests.
-noconfirm
Specifies that the command must execute without any prompts and confirmation from the user.
Usage
Use this command to enable x-header mode, and specify the x-header format name whose fields are to be inserted in HTTP GET and POST request packets.
Also, see xheader-format CLI command in the Active Charging Service Configuration Mode and the x-header Format Configuration Mode Commands chapters.
Example
The following command enables x-header mode, and specifies the x-header format name as test12:
xheader-insert xheader-format test12
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883