How it Works
Failure handling works in the following way:
-
If there is a failure, the Diameter endpoint fetches the applicable failure handling profile.
-
If the failure handling profiles are not defined or if a profile is defined with no message and failure type that should match the failed request, then the default failure handling is applied. The default failure handling is no retry with the action terminate and subaction as with-term-req , which implies with no termination request.
-
Diameter endpoint reattempts request with the alternate peers or routes until the request is successful or the reattempt the reaches the configured retry count as specified by applicable failure handling profile.
-
If the applicable peer or route count is lower than the retry count, then remaining retries are discarded after all the applicable peers or routes are attempted.
-
Retry count, which is determined during the first failure after the request is sent out, is used. If there is a failure during retries and that failure corresponds to a different failure handling profile with a different retry count, then also Diameter endpoint continues with the retry count that is determined during the first failure.
-
Retry counting starts only after a minimum of one request is sent. Failure before the retry count is not considered.
-
Even after all the reattempts or all peers or routes reattempts, if the request is not successful, then the Diameter endpoint send the action and subaction as part of response to the service.
-
Action and subaction applicable for the most recent failure is used in the response.
No additional handling is done on the Diameter endpoint for any action or subaction because action for those are taken on the service side as follows:
Action
-
continue : Continue with the session
-
terminate : Terminate the session. This action is the default action.
-
discard-traffic : Block or discard the data traffic. This subaction is associated with action with the continue . action and is applicable only for the Gy interface.
-
local-fallback : Apply local policies. This subaction is associated with the continue action.
-
none : No action. This subaction is associated with the Associated with continue action and is applicable only for the Gy interface. none is the default option for the Gy calls for the continue action.
-
retry-server-on-event : Reconnect to server on credit control update requests. This subaction is associated with the continue action and is applicable only for the Gx interface.
-
send-ccrt-on-call-termination : Send CCR-T request to PCRF for credit control update request failure. This subaction is associated with the continue action and is applicable only for the Gx interface. send-ccrt-on-call-termination is the default option for Gx calls for continue action.
-
with-term-req : Terminate the session by sending the termination request (CCR-T). This subaction is associated with the terminate action and is applicable only for the Gx interface. with-term-req is the default option for the Gx calls for terminate action.
-