Timer Used in Base Diameter:

(This is the configuration under diameter endpoint configuration on ST40)

connection timeout <1..30> :

Configures the timer for establishing a transport layer connection (TCP
connection). If the connection is not established during this time expiry, we close this
connection that we initiated at the ST16 end.

connection retry-timeout <1...900> : (Tc)

This is also at TCP level. This timer is used to delay the connection
establishment/re-establishment of ST16 with Diameter server. The connections that are
closed or the ones that go in IDLE state, we attempt to re-establish those connections
again and connection retry-timeout sets this time-limit after which the TCP connection
will be attempted to be opened again.

response-timeout <1 .. 300> :

Response timeout timer is used by the base layer to set the maximum allowed
response time for messages sent from ST16 to Diameter server. ST40 maintains a queue
of all the DCCA messages sent out. Ones that are not responded to within the response-
timeout duration, will get expired. This is at diabase level for diabase messages.

watchdog-timeout <6 .. 30> : (Twinit)

This timer is used to send the Device-Watch-Dog to the Diameter Server
periodically to test its availability.

route-failure deadtime <1 .. 86400> :

This configures the time duration for which we keep the FAILED status of a
route. When this time expires, we change the status to AVAILABLE.

Times Used in Diameter Credit Control Mode:

(This is the configuration under credit-control in ECS)

diameter pending-timeout <1 .. 300> : (Tx)
This timer is used by the DCCA application to set the maximum allowed response
time for messages sent from ST16 to Diameter Server. This is at DCCA application level
and for DCCA application messages.

quota holding-time <1 .. 4000000000> : (QHT)

The maximum allowed time for a granted quota by the server to remain
Idle(unused). On expiry of this timer we report the amount of quota used to the server.

quota validity-time <1 .. 65535> :

 The maximum time upto which the granted quota by the server is Valid.

cca quota retry-time <0 .. 86400> : Used in rulebase configuration mode.

This timer is used to delay the quota request by the ST16 to the Diameter server
for a specific category(rating-group), when that category is already blacklisted.

cca quota time-duration algorithm consumed-time <1..4294967295> :

This timer is used to close the time usage envelope. If the user is not using the
granted quota continuously for QCT time period, we will close this envelope once this
timer expires and the total usage is calculated as “First packet to last packet + QCT

cca quota time-duration algorithm parking-meter <1..4294967295> :

This timer is also used to close the time usage envelope. The granted quota is
consumed discretely in “chunks” of the base time interval at the start of each base time
interval. Traffic is then allowed to flow for the period of the consumed quota. If quota is
exhausted completely or the threshold is hit, then the request for more quotas occurs only
at the end of the base time interval.

cca quota time-duration algorithm continuous-time-periods <1..4294967295> :

Continuous time period mechanism constructs time envelope out of consecutive
base-time intervals in which the traffic occurred up to and including a base time interval
which contains no traffic.