Preview Tool

Cisco Bug: CSCul18393 - CSCur13113pPGW not sending CCR-u to PCRF when OOC

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

OOC for new rating-group for the same rule is not sent to the PCRF resulting in incorrect information being sent to PCRF

Steps to reproduce the Issue / Call Flows:

2. PCRF-PGW CCA-i; Dynamic Rule RTRRule3300; RG 3300 ; Event Trigger OOC
3. PGW-OCS CCR-i; MSCC for RG 3300
4. OCS-PGW CCA-i; Quota allocated for RG 3300; FUA:RESTRICT_ACCESS; VT; filter-id:post deny

Subscriber uses up the quota

5. PGW-OCS CCR-u; QUOTA Exhausted
6. PGW-PCRF CCR-u; RTRRule3300 is TEMP_INACTIVE; Event Trigger:OOC

This is the stage where throttling is done:

7. PCRF-PGW CCA-u; Reinstall RTRRule3300; RG5300 (change in RG); APN-AMBR:200kbps (Throttling)
8. PGW-OCS CCR-u; MSCC for RG5300
9. OCS-PGW CCA-u; Quota Allocated for RG 5300

At this stage, subscriber gets throttled.

Now, billing cycle reset was simulated, meaning, OCS sent down a RAR

12. PGW-OCS CCR-u ; MSCC for RG3300 (since this RG was in Restrict Access state); MSCC for RG5300 container the quota consumed
13. OCS-PGW CCA-u; MSCC for RG3300 is allocated quota back ; MSCC for RG5300--> 0 quota, FUA:RESTRICT_ACCESS; filter-id & VT installed

Expectation at this time: Since the subscriber has come out of that billing cycle, OCS allocated quota back to RG3300 (Note: At this point although quota is given for RG3300, there is no dynamic rule present that is associated with this RG). Now, the expected behavior is since RTRRule3300 is OOC associated with RG5300, PGW makes the rule TEMP_INACTIVE (happenned as expected ) but the PGW did not go to PCRF with the OOC for the rule/rg
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.