Cisco Cisco ASR 5000

 

This command allows you to specify how to charge for the control traffic associated with an application. 

 

ACS 

 

Security Administrator, Administrator 

 

Exec > ACS Configuration > Rulebase Configuration 

active-charging service service_name > rulebase rulebase_name

 

Entering the above command sequence results in the following prompt: 

[local]host_name(config-rule-base)# 

 

flow control-handshaking { charge-to-application { [ all-packets ] [ initial-packets ] [ 
mid-session-packets ] [ tear-down-packets ] } | charge-separate-from-application } 

default flow control-handshaking 

no flow control-handshaking [ charge-to-application ] 

 

Configures this command with its default setting. 
Default: Same as 

 

 

If previously configured, deletes the flow control-handshaking configuration from the current rulebase. The 
control packets will use whatever content-id is determined by the normal use of the 

 commands. 

In this command, the optional keyword 

 is deprecated and has no effect. 

 

Configures the charging action to include the flow control packets either during initial handshaking only or 
specified control packets during session for charging. 



 

: Specifies that the initial setup packets will wait until the application has been 

determined before assigning the content-id, and all mid-session ACK packets as well as the final 
tear-down packets will use that content-id. 



 

: Specifies that only the initial setup packets will wait for content-id assignment. 



 

: Specifies that the ACK packets after the initial setup will use the 

application's or content-id assignment. 



 

: Specifies that the final tear-down packets (TCP or WAP) will use the 

application's or content-id assignment.