Preview Tool

Cisco Bug: CSCup39763 - create a dynamic Gx dictionary with Credit-Control-Group AVP

Last Modified

Mar 22, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

For the roaming decoupling project the PCRF selects a DCCA peer out of a bunch of peers. In another words PCRF sends in CCA-I
      [V] [M]  Charging-Information
         Code:      0x0000026a (618) Charging-Information
         Flags:     0xc0       (192) [V]  [M]
         Length:    0x000064   (100)
         Vendor-Id: 0x000028af (10415) 3GPP
          [V] [M]  Primary-Event-Charging-Function-Name
             Code:      0x0000026b (619) Primary-Event-Charging-Function-Name
             Flags:     0xc0       (192) [V]  [M]
             Length:    0x000057   (87)
             Vendor-Id: 0x000028af (10415) 3GPP
             Data: aaa://serverName:3868;transport=tcp;protocol=diameter
 The bunch of DCCA peers represents the bunch of roaming partners. It can be from one to many, but all of them must be configured under the same diameter endpoint because all of them will be used under the same APN. An APN can be linked to only one credit-control-group and the credit-control group can be linked only to one diameter endpoint.
 Now, in a working case there is no problem. The PCRF supplies the DCCA FQDN and the PGW goes to that DCCA. Fine...
 But, if the FQDN is wrong or the targeted DCCA is down the PGW selects another available peer and starts the credit-control there.
 There is no configuration (at least I didn't find it) that could prevent the PGW from doing so, i.e. drop the session or start offline charging session.
 From VF point of view this is an absolute show stopper because the various roaming partners are different companies and it cannot be that the subscriber of company A will be sent to company B.
 We need a way that it prevents the PGW from attempting to start the DCCA session with another DCCA peer than the one received from PCRF (or AAA or configured locally in credit-control group)

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.