Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 5

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

In this section:

Table of Contents
maxLevel4

Call Trace Filtering

Multiexcerpt
MultiExcerptNameCall Trace Filtering

The

Spacevars
0product
supports configuring Call Trace Filters using the Signaling Packet Capture command to establish criteria to determine call events and logging PES call trace messages (using the ".TRC" file extension) to the system trace data event log. This information is used for debugging policy and call routing issues.

The following default information is collected during a call trace:

  • Service group configuration
  • DSP T.38 event information, if applicable
  • DSP channel statistics
  • DEBUG/SYS log information

The first three Call Trace filters are automatically 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

Spacevars
0product
may be configured to stop call tracing if either of following criteria is met:

  • Configured maxTriggerCount is reached or,
  • Configured callTraceTimer expires
 

To set the callTraceTimer from the CLI, use the syntax:

Code Block
languagenone
set global callTrace callTraceTimer <minutes>

 

To restart the call trace without changing the callTrace configuration, use the CLI command:

Code Block
languagenone
request global callTrace action command start

 

To enable call trace logging using CLI, refer to Call Trace - CLI.

The

Spacevars
0product
 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.

 

 

Info
titleNote

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.

Offline Call Trace Analysis Using Log Exchange (LX) Utility

Multiexcerpt
MultiExcerptNameLX

The TRC files can be analyzed offline using the Sonus LX tool, which generates a SIP ladder diagram from the TRC or DBG files. The LX tool is a Windows PC application available free of charge to all customers and partners with a license agreement, and can be downloaded as part of your software download request. For details, refer to LXDOC.

Caption
0Figure
1LX Main User Interface

 

Pagebreak