Cisco Cisco Packet Data Gateway (PDG)
ACS Rulebase Configuration Mode Commands
▀ transactional-rule-matching
▄ Command Line Interface Reference, StarOS Release 16
762
transactional-rule-matching
This command allows you to enable or disable transactional rule matching (TRM) which allows the Enhanced Charging
Service (ECS) to bypass per-packet rule matching on a transaction once the transaction is fully classified.
Service (ECS) to bypass per-packet rule matching on a transaction once the transaction is fully classified.
Important:
The TRM feature is supported in SSI platform; earlier it was restricted only to ASR5500.
Product
ACS
ADC
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
transactional-rule-matching
[ default | no ] transactional-rule-matching
default
Configures this command with its default setting.
Default: Disabled.
Default: Disabled.
no
If already configured, disables transactional rule matching.
Usage
Use this command to enable or disable transactional rule matching. This allows the Enhanced Charging
Service (ECS) to bypass per-packet rule matching on a transaction once the transaction is fully classified.
A transaction for TRM can be defined as the entire UDP flow, the ACK of the 3-way handshake to the
FIN/RST of a TCP flow, or the HTTP request to the next HTTP request, or HTTP request to the FIN/RST for
the final request of the flow. Rule matching can be performed on IP L4 rules (UDP, TCP), HTTP, and
HTTPS.
In 16.0 and later releases, ADC and TRM/FP can be enabled together. ADC flows will be considered for
TRM optimization. Most VoIP applications that require all packets of the flow do not support TRM. When
TRM/FP is enabled with ADC, such protocols will not take TRM/FP.
Service (ECS) to bypass per-packet rule matching on a transaction once the transaction is fully classified.
A transaction for TRM can be defined as the entire UDP flow, the ACK of the 3-way handshake to the
FIN/RST of a TCP flow, or the HTTP request to the next HTTP request, or HTTP request to the FIN/RST for
the final request of the flow. Rule matching can be performed on IP L4 rules (UDP, TCP), HTTP, and
HTTPS.
In 16.0 and later releases, ADC and TRM/FP can be enabled together. ADC flows will be considered for
TRM optimization. Most VoIP applications that require all packets of the flow do not support TRM. When
TRM/FP is enabled with ADC, such protocols will not take TRM/FP.