Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to Traffic Monitoring and Statistics

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

The default information

collected during a call trace

includes the following

:

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

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 automatically logged unless

the

the stopMatch

flag

 flag in enabled

(

, whereby the number of filters logged may be less than three

)

.

The

The stopMatch

flag

 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

A callTraceTimer

configuration

 configuration is provided along with

the

the maxTriggerCount

configuration

 configuration to limit the logging of call/error filter events in the TRC file. The

SBC

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 CLI 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, see refer to Call Trace - CLI.

The SBC generates

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.

 

 

note
Info
title
Note

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.

Info

Call Trace functionality is supported using either the EMA or CLI.

  • EMA:
see .
  • CLI:
see  

Offline Call Trace Analysis Using Log Exchange (LX) Utility

Multiexcerptexcerpt
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, see refer to LXDOC.

Caption
0Figure
1LX Main User Interface

 

Pagebreak