для Cisco Cisco Packet Data Gateway (PDG)
Diameter Failure Handling Template Configuration Mode Commands
▀ msg-type
▄ Command Line Interface Reference, StarOS Release 16
3462
send-ccrt-on-call-termination
– Sends CCR-T to PCRF on call termination for
failure-handling CONTINUE.
Important:
This option is valid only for credit-control-update request
though it is allowed to configure for all the requests.
without-retry
– Continue the session without retrying to the secondary PCRF.
retry-and-terminate
– In the event of a failure the user session continues for the duration of one
retry attempt with the server. If this retry attempt also fails, the session is terminated.
max-transmissions number-of-retries
: Specifies the maximum number of retries to
the server. The maximum server retries that can be configured is 5 and the default value for
retries is 1. When max-retries are exhausted, session termination happens.
retries is 1. When max-retries are exhausted, session termination happens.
CCR-U is retried for a maximum of number of retries configured in the failure handling
template when experimental result code (4198 -
DIAMETER_PENDING_TRANSACTION) is received from PCRF in CCA-U.
template when experimental result code (4198 -
DIAMETER_PENDING_TRANSACTION) is received from PCRF in CCA-U.
without-term-req
– Terminate the session without sending the termination request (CCR-
T).
terminate
– In the event of a failure the user session is terminated.
without-term-req
– Terminate the session without sending the termination request (CCR-
T).
Usage
Use this command to specify the behavior in the event of a communication failure with the prepaid server. If
there are different failure handling configurations present within the template for the same message type, the
action is applied as per the latest error encountered.
Lookup is done first to identify if there is an exact match for
there are different failure handling configurations present within the template for the same message type, the
action is applied as per the latest error encountered.
Lookup is done first to identify if there is an exact match for
message-type
and
failure-type
. If not
present, lookup is done for 'any' match for message and failure type.
That is, when there are multiple matches, it is preferred to find a match to a specifically configured value over
a match to something configured with
That is, when there are multiple matches, it is preferred to find a match to a specifically configured value over
a match to something configured with
any
or
any-error
. If there are multiple best matches, the one with a
specifically configured
msg-type
over a match to
msg-type any
is preferred.
There are two levels of possible communication failure:
The TCP connection failed
DIAMETER routing failed to deliver a request or failed to receive a response.
The specified behavior is used for sessions when no behavior is specified by the server, such as by the CC-
Failure-Handling AVP in DIAMETER messages. This command may be entered once for each type of
message.
The following are the default action for Diameter result codes:
Failure-Handling AVP in DIAMETER messages. This command may be entered once for each type of
message.
The following are the default action for Diameter result codes:
For all protocol error codes 3000 to 3999, the default action is
terminate
. For all transient error codes
4000, 4001, 4004 to 4180, and 4182 to 4999, the default action is
continue
.
For transient error codes 4002, 4003, and 4181, the default action is retry-and-
terminate
.
For error code 4001, the default action is
terminate
.
For permanent error codes 5000 to 5999, the default action is
terminate
.
Example
The following command configures to terminate the session when the Diameter application encounters a
failure due to Diabase error in the Credit-Control Initial Request (CCR-I) message:
failure due to Diabase error in the Credit-Control Initial Request (CCR-I) message: