Guest

Preview Tool

Cisco Bug: CSCvs63645 - Incorrect CDRs produced when multiple services configured

Last Modified

Apr 21, 2020

Products (1)

  • Cisco Policy Suite for Mobile

Known Affected Releases

19.3.0

Description (partial)

Symptom:
Customer's Test Scenario /* all referenced data is in the Annex_data.rar attachment */

Subscriber's Profile.
 - Subscriber IMSI 250098096000001.
 - Subscriber has two services assigned: Group4_B_B and Group3_B_B (as seen in the subscriber data.txt).
 - Subscriber has balances Group3 and Group4 with relevant quotas RQ_20Gb_1m_NR_96 and RQ_5Gb_1m_NR_1024 (as seen in the Control Center data, files СС_service.png and CC_balance.png).

Message Flow.
 - CCR-I.
 - CCR-U with consumption 100.
 - CCR-T with consumption 200.
 A full scenario can be found in the traffic-IUT_CDR_test.xml.

Produced CDRs as seen in the cdrs-PCRF_CDR-2019-12-30-160455.csv.
 - CDR fields have the following names (according to the properties in PB): imsi, msisdn, serviceCode, balanceCode, balanceUsed, balanceRemaining, quotaCode, framedIp, accessType, ratType, sgsnAddress, eventDateTime, cellSiteId, totalBytes, sessionDuration, creditStartDate, creditEndDate.
 - The serviceCode field is incorrect. The value of this field in the produced CDR is Group3_B_B, but it doesn't match consumed balance and quota Group4 and RQ_5Gb_1m_NR_1024.

Expected CDRs.
 - The serviceCode field should correspond to the service code, which balance and quota were consumed. In our case, it should be Group4_B_B.

Conditions:
Multiple services with the corresponding balances and quotas are provisioned to a subscriber. The subscriber consumes one of the balances. CDRs should reflect the service, which actually consumed traffic.
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.