Table of Contents
Advertisement
▀ Features and Terminology
Final Unit Indication at Command Level
Gy currently does not support FUI AVP at command level. If this AVP is present at command level it is ignored. If the
FUI AVP is present at command level and the Final-Unit-Action AVP set to TERMINATE, Gy sends a CCR-Terminate
at the expiry of the quota, with all quotas in the USU AVP.
Important:
Final Unit Indication at MSCC Level
If the Final-Unit-Indication AVP is present at MSCC level, and if the Final-Unit-Action AVP is set to TERMINATE, a
CCR-Update is sent at the expiry of the allotted quota and report the usage of the category that is terminated.
For information on redirection cases refer to Redirection section.
Credit Control Failure Handling
CCFH AVP defines what needs to be done in case of failure of any type between the client and the server. The CCFH
functionality can be defined in configuration but if the CCFH AVP is present in the CCA, it takes precedence. CCFH
AVP gives flexibility to have different failure handling.
Gy supports the following Failure Handling options:
TERMINATE
CONTINUE
RETRY AND TERMINATE
CCFH with Failover Supported
In case there is a secondary server is configured and if the CC-Session-Failover AVP is set to
FAILOVER_SUPPORTED, the following behavior takes place:
Terminate: On any Tx expiry for the CCR-I the message is discarded and the session is torn down. In case of
CCR-Updates and Terminates the message is sent to the secondary server after response timeout and the
session is proceeded with the secondary server. In case there is a failure with the secondary server too, the
session is torn down.
Continue: On any Tx expiry, the message is sent to the secondary server after response timeout and the session is
proceeded with the secondary server. In case there is a failure with the secondary server too, the session is still
established, but without quota management.
Retry and Terminate: On any Tx expiry, the message is sent to the secondary server after the response timeout.
In case there is a failure with secondary server too, the session is taken down.
CCFH with Failover Not Supported
In case there is a secondary server configured and if the CC-Session-Failover AVP is set to
FAILOVER_NOT_SUPPORTED, the following behavior takes place as listed below. Same is the case if there is no
secondary server configured on the system.
Terminate: On any Tx expiry, the session is taken down.
Continue: On any Tx expiry, the session is still established, but without quota management.
Retry and Terminate: On any Tx expiry, the session is taken down.
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
352
FUI AVP at command level is only supported for Terminate action.
Gy Interface Support
Advertisement
Table of Contents
