Cisco Cisco Packet Data Interworking Function (PDIF) Prospecto
ACS Rulebase Configuration Mode Commands
▀ flow control-handshaking
▄ Cisco ASR 5x00 Command Line Interface Reference
690
flow control-handshaking
This command allows you to specify how to charge for the control traffic associated with an application.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
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)#
Syntax
flow control-handshaking { charge-to-application { [ all-packets ] [ initial-packets ] [
mid-session-packets ] [ tear-down-packets ] } | charge-separate-from-application }
mid-session-packets ] [ tear-down-packets ] } | charge-separate-from-application }
default flow control-handshaking
no flow control-handshaking [ charge-to-application ]
default flow control-handshaking
Configures this command with its default setting.
Default: Same as
Default: Same as
no flow control-handshaking
no flow control-handshaking [ charge-to-application ]
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
control packets will use whatever content-id is determined by the normal use of the
action
commands.
In this command, the optional keyword
charge-to-application
is deprecated and has no effect.
charge-to-application { [ all-packets ] [ initial-packets ] [ mid-session-packets
] [ tear-down-packets ] }
] [ tear-down-packets ] }
Configures the charging action to include the flow control packets either during initial handshaking only or
specified control packets during session for charging.
specified control packets during session for charging.
all-packets
: 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.
tear-down packets will use that content-id.
initial-packets
: Specifies that only the initial setup packets will wait for content-id assignment.
mid-session-packets
: Specifies that the ACK packets after the initial setup will use the
application's or content-id assignment.
tear-down-packets
: Specifies that the final tear-down packets (TCP or WAP) will use the
application's or content-id assignment.