Page History
| Noprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
In this section:
|
Call Trace Filtering
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:
...
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:
...
| 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.
|
Offline Call Trace Analysis Using Log Exchange (LX) Utility
| Excerpt | |||||||
|---|---|---|---|---|---|---|---|
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 LXDOC.
|
| Pagebreak |
|---|
Overview
Content Tools