Cisco Cisco ASR 5000
Credit Control Configuration Mode Commands
▀ servers-unreachable
▄ Command Line Interface Reference, StarOS Release 18
2880
Pass traffic until interim time expiration post which continues or terminates the call.
Pass traffic until interim volume expiration post which continues or terminates the call.
During mid session:
Block traffic: Terminate the session.
Continue call: Continue by making the session offline.
Run out of session quota post which terminates the call.
Pass traffic until timer expiration post which terminates the call: Session would be offline
while the timer is running.
Pass traffic until interim time expiration post which continues or terminates the call.
Pass traffic until interim volume expiration post which continues or terminates the call.
This command works on the same lines as the
failure-handling
command, which is very generic for each
of the xxx-requests.
The
The
servers-unreachable
CLI command is specifically for TCP connection error. In the event of TCP
connection failure, the
failure-handling
and/or
servers-unreachable
commands can be used. This
way, the operator has the flexibility to configure CCFH independent of OCS-unreachable feature, that is
having two different failure handlings for same request types.
having two different failure handlings for same request types.
Important:
Please note that the flexibility to configure CCFH independent of OCS-unreachable feature is
applicable only to 12.1 and earlier releases. In 12.2 and later releases, if configured, the
servers-unreachable
takes
precedence over the
failure-handling
command.
This command can also be used to control the triggering of behavior based on transport failure, response
message timeouts or Tx expiry when OCS becomes unreachable. The OCS could be unreachable due to no
TCP connection and the message timeout could be due to network congestion or any other network related
issues.
The following are the possible and permissible configurations with respect to behavior triggering:
message timeouts or Tx expiry when OCS becomes unreachable. The OCS could be unreachable due to no
TCP connection and the message timeout could be due to network congestion or any other network related
issues.
The following are the possible and permissible configurations with respect to behavior triggering:
servers-unreachable behavior-triggers { initial-request | update-request }
transport-failure
servers-unreachable behavior-triggers { initial-request | update-request }
transport-failure response-timeout
servers-unreachable behavior-triggers { initial-request | update-request }
transport-failure tx-expiry
Of these configurations, the first one is considered to be the default configuration and it will take care of
backward compatibility with 12.0 implementation.
If the server returns the CC-Failure-Handling AVP, it would apply for transport-failure/response-timeout/tx-
expiry when the CLI command
backward compatibility with 12.0 implementation.
If the server returns the CC-Failure-Handling AVP, it would apply for transport-failure/response-timeout/tx-
expiry when the CLI command
servers-unreachable
is not configured. If the
servers-unreachable
is configured for a set of behavior-triggers, then servers-unreachable configuration will be applied for them.
For those behavior-triggers for which servers-unreachable is not configured, the CC-Failure-Handling value
provided by the server will be applied.
By default, Result-Code such as 3002 (Unable-To-Deliver), 3004 (Too-Busy) and 3005 (Loop-Detected) falls
under delivery failure category and will be treated similar to response-timeout configuration.
For those behavior-triggers for which servers-unreachable is not configured, the CC-Failure-Handling value
provided by the server will be applied.
By default, Result-Code such as 3002 (Unable-To-Deliver), 3004 (Too-Busy) and 3005 (Loop-Detected) falls
under delivery failure category and will be treated similar to response-timeout configuration.
Example
The following command configures the duration of
1111
seconds, for the subscriber session to be in offline
state, after which the initial request calls will be terminated.
servers-unreachable initial-request terminate after-timer-expiry 1111