Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
▀ AAA Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
62
Protocol
Secondary CCF
Hostname
Port
Protocol
CSCud32573 - All Diameter Result Code 2xxx to be interpreted as success
Applicable Products: GGSN, HA, IPSG, PDSN, P-GW
Feature Changes
Interpreting All Diameter Result Code 2xxx as Success
Currently, only result codes 2001 and 2002 are interpreted as success result codes by DCCA implementation and any
result codes above 2002 would result in invoking CCFH configuration. As per RFC 3588, all 2xxx result codes are to be
interpreted as success. DCCA implementation of 2xxx result code interpretation is now compliant to RFC 3588.
result codes above 2002 would result in invoking CCFH configuration. As per RFC 3588, all 2xxx result codes are to be
interpreted as success. DCCA implementation of 2xxx result code interpretation is now compliant to RFC 3588.
Previous Behavior: In DCCA only 2001 and 2002 were treated as success result codes. All other Diameter Result
Codes in the range of 2000 to 2999 received at command level in CCA message were terminated with cause as
“Diameter_Bad_Answer” even if the RFC 3588 defined the Result Code 2xxx as “success” Result Code.
Codes in the range of 2000 to 2999 received at command level in CCA message were terminated with cause as
“Diameter_Bad_Answer” even if the RFC 3588 defined the Result Code 2xxx as “success” Result Code.
New Behavior: As part of this enhancement, all Result Codes in the range of 2000 to 2999 are considered as “success”
both at command level and MSCC level. The same behavior is applied for Result-Code AVP sent both at command
level and at MSCC level.
both at command level and MSCC level. The same behavior is applied for Result-Code AVP sent both at command
level and at MSCC level.
To know the CCA success count, a new field “Result Code 2xxx” is added to the
show active-charging credit-
control statistics group
command output and the same is added under bulkstats as well.
Customer Impact: This helps the operator to implement different charging logic in the OCS server depending on
different business logics.
different business logics.
Performance Indicator Changes
DCCA Group Schema
The following new bulkstats variable has been added to track the total number of CCA Result-Codes that are received in
range of 2000 and 2999 at command level.
range of 2000 and 2999 at command level.
cca-2xxx-rc
show active-charging credit-control statistics group default
To know the CCA success count, the following new field has been added to the output of this show command under
“CCA Result Code 2xxx Stats”:
“CCA Result Code 2xxx Stats”:
Result Code 2xxx