Cisco Cisco ASR 5000
Credit Control Configuration Mode Commands
diameter msg-type ▀
Command Line Interface Reference, StarOS Release 18 ▄
2833
ccrt
This keyword disables FINAL reporting for MSCC which are in no-quota and FUI Redirect/Restrict-access
state.
state.
suppress-final-reporting
Important:
This keyword is available only in 18.3, 19.2 and later releases.
When used with the
diameter msg-type ccru
command, this keyword disables immediate FINAL
reporting for result code 4010/4012. When used with the
diameter msg-type ccrt
command, this
keyword disables FINAL reporting for no-quota FUA Redirect/Restrict-access.
suppress-blacklist-reporting
Important:
This keyword is available only in 18.3, 19.2 and later releases.
Disables FINAL reporting for blacklisted (4010/4012) content in CCR-T.
Usage
With this CLI command “
diameter msg-type ccrt suppress-final-reporting
” configured:
Before MSCC enters into FUI Redirect or Restrict-Access state, all the used quota is reported using the
Reporting-Reason as “OTHER_QUOTA_TYPE”. Since all the quota is reported, there is no need to send any
other FINAL reporting to OCS.
Releases prior to 16.0, even if there is no quota utilization, the gateway sends FINAL with USU as ‘0’ octets
in CCR-T. In this release, the FINAL reporting in CCR message is controlled when there is no quota usage to
report to the OCS server during the FUI Redirect/Restrict-access scenario.
With this CLI command “
Reporting-Reason as “OTHER_QUOTA_TYPE”. Since all the quota is reported, there is no need to send any
other FINAL reporting to OCS.
Releases prior to 16.0, even if there is no quota utilization, the gateway sends FINAL with USU as ‘0’ octets
in CCR-T. In this release, the FINAL reporting in CCR message is controlled when there is no quota usage to
report to the OCS server during the FUI Redirect/Restrict-access scenario.
With this CLI command “
diameter msg-type ccru suppress-final-reporting
” configured:
In releases prior to 15.0, CCR-U is sent immediately on receiving 4010 or 4012 Result-Code at MSCC level.
This new CLI command controls sending of immediate CCR-U with FINAL as Reporting-Reason. All other
behaviors remain almost same like a Rating-group being blacklisted.
If this CLI command is configured, on receiving the result-code 4010/4012 at MSCC-level, immediate CCR-
U with FINAL as Reporting-Reason will not be sent. All USU corresponding to that rating group is reported
in CCR-T message.
In releases prior to 18, configuration control was available for filtering FINAL USU reporting in CCR-U for
blacklisted content and in CCR-T for Final-Unit-Indication (REDIRECT/RESTRICT-ACCESS) activated
content. In the case of CCR-T message, there is no way to ignore the FINAL reporting for blacklisted
(4010/4012) content if the FINAL was previously disabled in CCR-U.
In 18 and later releases, the current CLI configuration is enhanced to disable FINAL reporting in CCR-T
message for blacklisted (4010/4012) content. The
This new CLI command controls sending of immediate CCR-U with FINAL as Reporting-Reason. All other
behaviors remain almost same like a Rating-group being blacklisted.
If this CLI command is configured, on receiving the result-code 4010/4012 at MSCC-level, immediate CCR-
U with FINAL as Reporting-Reason will not be sent. All USU corresponding to that rating group is reported
in CCR-T message.
In releases prior to 18, configuration control was available for filtering FINAL USU reporting in CCR-U for
blacklisted content and in CCR-T for Final-Unit-Indication (REDIRECT/RESTRICT-ACCESS) activated
content. In the case of CCR-T message, there is no way to ignore the FINAL reporting for blacklisted
(4010/4012) content if the FINAL was previously disabled in CCR-U.
In 18 and later releases, the current CLI configuration is enhanced to disable FINAL reporting in CCR-T
message for blacklisted (4010/4012) content. The
diameter msg-type ccrt
CLI command includes an
additional keyword
suppress-blacklist-reporting
to support this enhancement. The default behavior
of CCR-T is to send the FINAL reporting to be sent for blacklisted (4010/4012) content, if not reported
already in CCR-U.
already in CCR-U.
Important:
This feature is available only in 18.3, 19.2 and later releases.