Cisco Cisco Packet Data Gateway (PDG)
Global Configuration Mode Commands (threshold ppp - url-blacklisting)
unexpected-scenario session drop-call ▀
Command Line Interface Reference, StarOS Release 16 ▄
5853
unexpected-scenario session drop-call
Configures behavior when an unexpected call processing scenario is encountered. Enabling this command sets call
clearing logic that replaces the automatic generation of asserts and core dumps for an initial assert.
clearing logic that replaces the automatic generation of asserts and core dumps for an initial assert.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
unexpected-scenario session drop-call [ disable-core ]
default unexpected-scenario session drop-call
default
Disables call clearing logic for a graceful assert. This results in automatic core dump generation for
unexpected scenarios resulting in control and data outage for the task instance until the core is fully
generated.
unexpected scenarios resulting in control and data outage for the task instance until the core is fully
generated.
[ disable-core ]
This option disables the automatic generation of core dumps when a call is dropped for a specific session.
Usage
Use this command to enable call clearing logic that will minimize the automatic generation of asserts and
core dumps during a specific call processing session that may lead to data outage and session manager
recovery.
The call clearing logic is only applied to the first assert generated during a call processing session. When that
assert occurs, a zero-second timer lets the current stack unwind to avoid reentrancy issues. The call is then
dropped from all interfaces. This is considered to be a graceful assert.
A core dump is generated along with any application supplied debug info. The line number and file index of
the ASSERT appears in the call-line; the current call-line is marked as being in “assert_hit” scenario.
With the disable-core option set, a core dump is not generated following a graceful assert.
An assert generated after a graceful assert for the same unexpected scenario will cause the call to be dropped
and trigger an automatic core dump. Depending on the length of time required to generate the associated core
dump, a session manager recovery may be initiated. This is a highly unlikely possibility.
core dumps during a specific call processing session that may lead to data outage and session manager
recovery.
The call clearing logic is only applied to the first assert generated during a call processing session. When that
assert occurs, a zero-second timer lets the current stack unwind to avoid reentrancy issues. The call is then
dropped from all interfaces. This is considered to be a graceful assert.
A core dump is generated along with any application supplied debug info. The line number and file index of
the ASSERT appears in the call-line; the current call-line is marked as being in “assert_hit” scenario.
With the disable-core option set, a core dump is not generated following a graceful assert.
An assert generated after a graceful assert for the same unexpected scenario will cause the call to be dropped
and trigger an automatic core dump. Depending on the length of time required to generate the associated core
dump, a session manager recovery may be initiated. This is a highly unlikely possibility.
Important:
The graceful assert call clearing logic can only be applied to call processing events, such as VoLTE.
It cannot be used for ICSR-SRP scenarios.