In this section:


Related articles:


Overview

The SIP Call Tracing feature allows the SBC to trace all SIP calls when the system is not in an overload situation. Ribbon Analytics ingests the call's tracing data by collecting and importing the data for immediate use and then stores it in a database at periodic intervals. Ribbon Analytics uses the ingested data for building ladder (call flow) diagrams that span across Ribbon products and for data analysis after the call completes.


The SBC Core's "Dump Pdu" command is enhanced in release 11.1.1R7 to offer the option to print the DIAMETER PDUs (Protocol Data Units) to either the TRC or DBG log file. Previously, the "Dump Pdu" command controlled printing DIAMETER PDUs in just the DBG log file.


The Call Trace and Packet Capture page specifies the following log file level of detail captured once the trace is complete. 

  • Level 1 - Everything
  • Level 2 - Everything but raw hex dump
  • Level 3 - Only external message information and errors
  • Level 4 - Only SIP PDU events and GW-GW PDU events in Level 4 trace, when enabled.  

Note

When you upgrade to 11.1.1R7 or later, the Dump Pdu flag settings change as follows:

Dump Pdu Setting
Before Upgrade		Dump Pdu Setting
After Upgrade
disabled (default)off (default)
enableddbg

SIP Call Trace Functionality

SIP call tracing functionality is controlled by the Call Trace Filter profile. The SBC applies Call Trace Filter profiles on receiving the call. If the criteria matches, the SBC writes call details into call trace (TRC) file according to the following configured level of detail:

  • Level 1 to 3 tracing:  If the Call Trace Filter criteria match, the SBC generates a call trace key for each call and then writes the call details into the TRC file.
  • Level 4 tracing: Level 4 tracing is used to trace all calls; only SIP PDUs are written into the TRC file. The SBC does not generate a call trace key at this level.

DIAMETER Message Tracing

In addition to expanding the "Dump Pdu" command to include TRC log files, the SBC Core call tracing functionality now includes the ability to trace DIAMETER messages as described below.

  • Level 1 to 3 tracing: The SBC prints DIAMETER logs and PDUs along with SIP PDUs and other call logs for the traced call. The call trace key generated during call processing controls DIAMETER PDU logging in the trace file. 
  • Level 4 tracing:  Level 4 tracing is used to trace all calls, registration and other OODs SIP PDUs.
    • The Level 4 configuration in the Call Trace Filter Profile does not control the writing of all DIAMETER PDUs into the trace file.
    • To achieve Level 4 functionality for DIAMETER PDUs (e.g., to print all the DIAMETER PDUs into a TRC file), you must set the Diameter Node's Dump Pdu parameter to "Trc."    

Correlating DIAMETER PDUs

The SBC Core uses the GCID to correlate the DIAMETER PDUs with the SIP PDUs for a given call. However, the SBC 11.1.R7 uses the CORRID (Correlation Identifier used to track and manage sessions) to correlate the DIAMETER PDUs with the SIP PDUs for a SIP REGISTRATION transaction. The CORRID is printed only for REGISTRATIONS (not for the call).

Note

The preexisting functionality prints the CORRID/GCID against  the SIP PDUs.

Notes
  • Use the EMA Configure Trace and Media Packet Capture window to both configure Call Trace Filters and to initiate call traces to use in debugging policy and call routing issues.  
  • Use the EMA DIAM NODE window to set the Diameter Node's Dump Pdu parameter to "Trc" to achieve Level 4 functionality for DIAMETER PDUs (e.g., to print all the DIAMETER PDUs into a TRC file).


  • No labels