You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

In this section:

Related article:


Summary

Core dumps that occur in the field are often the result of a new call flow. However, when these core dumps occur, it is difficult to quickly confirm which new call flow caused the crash as there is no stored information relating to the sent and received network packets that comprise the call.

This facility enables memory based storage of recently sent and received SIP packets. In order to constrain the amount of system memory used, by default, only the data for recent calls are stored. This data is captured in the SCM process. 

Whether or not to save packets for stable calls or completed calls is specified in the configuration parameters.

In the event that a crash occurs, a tool is provided to extract this saved packet data from the core dump, and to provide the full contents of each packet of the SIP call flow for each call that was present on the system when the crash occurred.

Command Syntax

% set global saveRecentCallFlowsInMemory
	maxMemoryUsage <512-1048576>
	saveCallFlows <false | true>
	storeDataForCompletedCalls <false | true>
	storeDataForStableCalls <false | true>

Defaults per Personality Type

Whether the feature is turned on by default depends on the personality type and the platform.

When the feature is turned on by default, the maxMemoryUsage is set to 5% of the available memory.

Defaults per Personality Type:

Personality

Hardware Platforms

Virtual SWe

Cloud

I-SBC

EnabledNot available in the CLIAvailable
S-SBCEnabledNot available in the CLIAvailable
M-SBCNot available in the CLINot available in the CLINot available in the CLI

Command Parameters

Parameter

Length/Range

Description

M/O
maxMemoryUsage512-10485760

Specify a maximum amount of memory, in kilobytes, to consume for packet storage.

Default = 512

O
saveCallFlowsN/A

Enable this flag to store recent SIP packets sent and received in the SCM process.

  • false (default)
  • true

If you toggle this value from true to false, all stored calls are purged.

O
storeDataForStableCallsN/A

Enable this flag to save data for stable calls and calls in setup up to the amount of memory configured in maxMemoryUsage.

  • false (default)
  • true

If you toggle this value from true to false, all stored stable calls are purged.

O
storeDataForStableCompletedCallsN/A

Enable this flag to save data for completed calls, stable calls and calls in setup up to the amount of memory configured in maxMemoryUsage.

  • false (default)
  • true

If you toggle this value from true to false, all stored completed calls are purged.


If you set storeDataForStableCalls to false, then no completed calls are stored since the calls are purged when they transition to the stable state.

O


  • No labels