Cisco Cisco Packet Data Gateway (PDG)
behavior-triggers { initial-request | update-request } { result-code { any-error | result-code [ to
end-result-code ] } | transport-failure [ response-timeout | tx-expiry ] }
end-result-code ] } | transport-failure [ response-timeout | tx-expiry ] }
This keyword is used to determine when to apply server-unreachable action. This supports three configurable
options to apply server-unreachable action either at transport failure, Tx expiry or at response timeout. Out
of these three options, the transport failure is the default option.
options to apply server-unreachable action either at transport failure, Tx expiry or at response timeout. Out
of these three options, the transport failure is the default option.
• initial-request: Specifies the behavior when Diameter server(s)/OCS become unreachable during initial
session establishment.
• update-request: Specifies the behavior when Diameter server(s)/OCS become unreachable during
mid-session.
• result-code { any-error | result-code [ to end-result-code ] }: Specifies to configure any Diameter error
result code or a range of result codes to trigger entering server unreachable mode.
result-code must be an integer ranging from 3000 to 5999.
• transport-failure [ response-timeout | tx-expiry ]: This keyword specifies to trigger the behavior either
at transport failure or response timeout OR at Transport failure or Tx expiry.
initial-request { continue | terminate [ after-timer-expiry timeout_period ] }
This section applies only to 12.1 and earlier releases.
Important
Specifies behavior when Diameter server(s)/OCS become unreachable during initial session establishment.
• continue: Specifies to continue call if Diameter server(s) becomes unreachable.
• terminate: Specifies to terminate call if Diameter server(s) becomes unreachable.
after-timer-expiry timeout_period: On detecting transport failure, this keyword variable specifies the
time limit for which the subscriber session will remain in offline state before the call is terminated.
time limit for which the subscriber session will remain in offline state before the call is terminated.
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through
4294967295.
4294967295.
initial-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ]
} server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume
quota_value ] } server-retries retry_count ] | after-timer-expiry timeout_period }
} server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume
quota_value ] } server-retries retry_count ] | after-timer-expiry timeout_period }
This section applies only to 12.2 and later releases.
Important
Specifies behavior when Diameter server(s)/OCS become unreachable during initial session establishment.
• continue: Specifies to continue call if Diameter server(s) becomes unreachable.
• terminate: Specifies to terminate call if Diameter server(s) becomes unreachable.
◦after-interim-time timeout_period: Specifies to continue or terminate call after the interim timeout
period expires.
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through
4294967295.
4294967295.
Command Line Interface Reference, Modes C - D, StarOS Release 19
1066
Credit Control Configuration Mode Commands
servers-unreachable