Guest

Preview Tool

Cisco Bug: CSCuj84894 - KT EPC : PGW, missing Charging-Rule-Name for CBResp with TEMP_REJECT

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

14.0(41)

Description (partial)

Symptom:
When the RAR is received to create 2 dedication bearers in same time, 
if the CREATE_BEARER_REQUEST is failed by EGTP_CAUSE_TEMP_REJECTED_DUE_TO_HANDOVER_IN_PROGRESS,
then PGW reports CCR-U with only 1 Charing-Rule-Name in Charing-Rule-Report, 1 Charing-Rule-Name is missed.

        [V] [M] Charging-Rule-Report: 
          [V] [M] Charging-Rule-Name: icmp_dedi1			<<<<<<<<<<<<<<<<<<<<<<
          [V] [M] PCC-Rule-Status: INACTIVE (1)
          [V] [M] Rule-Failure-Code: RESOURCE_ALLOCATION_FAILURE (10)

In case the CREATE_BEARER_REQUEST is failed by EGTP_CAUSE_REQUEST_REJECTED,
PGW reports successfully CCR-U with the 2 Charing-Rule-Name in Charing-Rule-Report

        [V] [M] Charging-Rule-Report: 
          [V] [M] Charging-Rule-Name: icmp_dedi2                   <<<<<<<<<<<<<<<<<<<<<<<<
          [V] [M] Charging-Rule-Name: icmp_dedi1                   <<<<<<<<<<<<<<<<<<<<<<<<
          [V] [M] PCC-Rule-Status: INACTIVE (1)
          [V] [M] Rule-Failure-Code: RESOURCE_ALLOCATION_FAILURE (10)

Please look into the attached 2 mon profile for each cases and SSD files.

Conditions:
when the CBResponse fails
Bug details contain sensitive information and therefore require a Cisco.com 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.