The SBC supports logging PES call trace messages in tracing files (.TRC). Trace information is used for debugging policy and routing of a call. Processing information such as pre-processing, applying services, routing and post processing is logged. For identifying traces of a call, the call identifier is also logged in the .TRC file.
The default information collected during a call trace includes the following:
The global callTrace signalingPacketCapture
command allows you to create and configure Call Trace Filters using criteria to determine call events added to the system trace data event log (which uses the ".TRC" file extension). The first three Call Trace filters are logged unless the stopMatch
flag in enabled (whereby the number of filters logged may be less than three). The stopMatch
flag will halt filter profile matching once a match is found.
When call trace filter criteria is provisioned and a call meets the criteria, trace information is written to a tracing file. Call trace is enabled using the provisioning interface.A callTraceTimer
configuration is provided along with the maxTriggerCount
configuration to limit the logging of call/error filter events in the .TRC file. The SBC may be configured to stop call tracing if either of following criteria is met:
maxTriggerCount
is reached or,callTraceTimer
expiresTo set the callTraceTimer, use CLI syntax:
set global callTrace callTraceTimer <minutes>
To restart the call trace without changing the callTrace configuration, use the CLI command:
request global callTrace action command start
To enable call trace logging using CLI, see Call Trace - CLI.
The SBC generates sonusSbxNodeResourceCallTraceActiveNotification
alarm when the callTrace starts. When the callTrace stops, either due to maxTriggerCount reach or callTraceTimer expiry, SBC generates sonusSbxNodeResourceCallTraceDisabledNotification
trap and clears the sonusSbxNodeResourceCallTraceActiveNotification
alarm.
A system reboot, an application restart or a Live Software Upgrade (LSWU) causes the callFilter, mediaPacketCapture, callDetailCapture, and signalingPacketCapture filters to go offline. To overcome this, disable and then re-enable these filters.
Call Trace functionality is supported using either the EMA or CLI.