Preview Tool

Cisco Bug: CSCte79276 - CSG2 CCR-I prepaid-request-number not zero

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Service and Application Module for IP

Known Affected Releases

12.4(22)MDA 12.4(24)MD

Description (partial)


CSG2 sporadically sends a CCR-I message with CC-Request-Number AVP which is not set to Zero.
Some PCRF implementation do expect a Zero value. These vendors have implemented the recommendation in a strict way based on RFC 4006. The PCRF will reject or ignore the CCR-I from the CSG2 which results in a subscriber connection failure.

From RFC 4006:

8.2.  CC-Request-Number AVP

   The CC-Request-Number AVP (AVP Code 415) is of type Unsigned32 and
   identifies this request within one session.  As Session-Id AVPs are
   globally unique, the combination of Session-Id and CC-Request-Number
   AVPs is also globally unique and can be used in matching credit-
   control messages with confirmations.  An easy way to produce unique
   numbers is to set the value to 0 for a credit-control request of type
   INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the
   first UPDATE_REQUEST, to 2 for the second, and so on until the value
   for TERMINATION_REQUEST is one more than for the last UPDATE_REQUEST.


CSG2 Software revision: 12.2(22)MDA1, CSG2 Release 3.5
This has been verified in a mutli-PCRF enviroment
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.