Interworking Between Session-Based Gy And Event-Based Gy; Ocs Unreachable Failure Handling Feature - Cisco ASR 5x00 Administration Manual

▀ Features and Terminology
 On termination of the bearer/subscriber (subscriber level Gy).
 Initiation of session-based Gy session (delayed session initiation).
 Once the CCR-E transaction is complete and there are no further events to report.
For information on how to configure this feature, refer to the Gy Interface Support chapter in the administration guide
for the product that uses the Gy interface functionality.

Interworking between Session-based Gy and Event-based Gy

If both session-based Gy and event-based Gy mode are activated, then session-based Gy will take precedence i.e. all the
events will be reported through CCR-U if the corresponding triggers are enabled. Event-based Gy mode will be active
only when session-based Gy has been disabled and has never been activated previously for this session during its
lifetime.

OCS Unreachable Failure Handling Feature

The OCS Unreachable Failure Handling feature is required to handle when OCS goes down or unavailable. This feature
is otherwise noted as Assume Positive for Gy.
The OCS is considered unavailable/unreachable in the following scenarios:
 PCEF transmits a CCR-U or CCR-I message but no response is received before the specified timeout
 Diameter Watchdog request times out to the current RDR, causing the TCP connection state to be marked down
 Diameter command-level error codes received in a CCA
 If the PCEF is unable to successfully verify transmission of a CCR-T, the PCEF will not assign interim quota,
because the user has disconnected.
In 15.0 and later releases, the error result codes can be configured using the CLI command
behavior-triggers initial-request { result-code { any-error | result-code [ to end-
result-code ] } }
more information on the CLI command, see the Credit Control Configuration Mode Commands chapter of the
Command Line Interface Reference. However, if the CLI command
triggers { initial-request | update-request } result-code { any-error | result-code [ to
end-result-code ] }
The default set is:
 UNABLE_TO_DELIVER
 UNABLE_TOO_BUSY
 LOOP_DETECTED
 ELECTION_LOST
 Permanent failures
In 12.2 and later releases, existing failure handling mechanism is enhanced such that the subscriber can be allowed to
browse for a pre-configured amount of interim-volume and/or interim-time if OCS becomes unreachable due to
transport connection failure or gives an impression that OCS is unreachable owing to slow response for Diameter
request messages.
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
364
to trigger the server unreachable mode. The same is applicable for the update request also. For
is configured, then the default set of hard-coded error codes are applicable.
3002
3004
3005
4003
5001-5999 except 5002, 5003 and 5031.
servers-unreachable
no servers-unreachable behavior-
Gy Interface Support