Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
AAA Enhancements for 16.1 ▀
Release Change Reference, StarOS Release 16 ▄
49
Command Changes
diameter pending-timeout
The existing CLI command “
diameter pending-timeout
” under Credit Control Configuration mode has been
modified such that the time can be specified in deciseconds along with different message types. The default time will be
100 deciseconds (10 seconds).
100 deciseconds (10 seconds).
configure
require active-charging
active-charging service service_name
credit-control group group_name
diameter pending-timeout timer_value deciseconds msg-type { any | ccr-event |
ccr-initial | ccr-terminate | ccr-update }
ccr-initial | ccr-terminate | ccr-update }
default diameter pending-timeoutvariable
end
Notes:
The feature implementation ensures that the modified timer configuration is backward compatible. If the CLI
command is configured without “
desiseconds
” and “
msg-type
”, the configured time will be taken as
seconds and while displaying the CLI it will be converted to deciseconds and msg-type will be “
any
”.
CSCuj10006 - PGW not sending CCR-E to the OCS on receiving Trigger Type
Grouped AVP
Applicable Products: GGSN, HA, IPSG, PDSN, P-GW
Feature Changes
Failure Handling for CCR-E Messages
Previous Behavior: Earlier, there was no failure handling support for CCR-E messages (Event based Gy). Any failed
CCR-E request was not retried to secondary server.
CCR-E request was not retried to secondary server.
New Behavior: Failure handling for CCR-E is now supported and implemented as follows:
Diabase Error - For Diabase error, Event-based Gy session will retry sending the CCR-E to configured
secondary peer. If CCR-E fails with secondary peer, failure is ignored and the Event-based Gy session will
continue to report any further updates.
continue to report any further updates.
Tx timeout/ Response Timeout - On Tx timeout/ Response Timeout (which ever fires first) CCR-E will be
retried to secondary peer. If CCR-E fails with secondary peer, failure is ignored and the Event-based Gy
session will continue to report any further location updates.
session will continue to report any further location updates.