Cisco Cisco ASR 5000
ACS Rulebase Configuration Mode Commands
udr trigger ▀
Command Line Interface Reference, StarOS Release 18 ▄
791
udr trigger
This command allows you to configure additional triggers for generating UDRs.
Important:
This command is only available in StarOS 8.3 and later releases.
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
udr trigger { first-hit-content-id | tariff-time minute minutes hour hours | nemo-prefix-
update }
update }
no udr trigger { first-hit-content-id | tariff-time | nemo-prefix-update }
default udr trigger [ nemo-prefix-update ]
no
Disables first-hit-content-id UDR trigger.
default
Configures this command with its default setting.
Default: Disabled; no additional triggers.
Default: Disabled; no additional triggers.
first-hit-content-id
Specifies to generate interim UDR on first packet hit per rating group/content ID.
tariff-time minute minutes hour hours
This keyword allows to configure tariff time trigger to close ongoing UDR buckets and save all data traffic up
to tariff time in a single UDR file. By default, this CLI keyword is disabled.
Configuring this keyword enables the PDSN/PCEF to generate content base UDR record for each concurrent
online subscriber in each of day cross and place them in a single UDR file. The charging records include
content based service (by duration and by volume).
Tariff time is stored at rulebase level. Therefore if the tariff time is updated while there are ongoing calls in
the network, the old tariff time will be ignored and the new tariff time will be applied to the existing as well
as upcoming calls.
to tariff time in a single UDR file. By default, this CLI keyword is disabled.
Configuring this keyword enables the PDSN/PCEF to generate content base UDR record for each concurrent
online subscriber in each of day cross and place them in a single UDR file. The charging records include
content based service (by duration and by volume).
Tariff time is stored at rulebase level. Therefore if the tariff time is updated while there are ongoing calls in
the network, the old tariff time will be ignored and the new tariff time will be applied to the existing as well
as upcoming calls.