Overview
The SBC Core can trace SIPRec legs to assist in debugging various issues associated with SIPRec legs, such as:
- Missing media packets
- Missing Signalling packets towards SIP Recording Server (SRS) in debug (
.DBG
) logs - Crank back issues in QUAD SIPREC
As part of the enhancement, the flag sipRecLegsCapture
is introduced under the callFilter
parameter of the global callTrace
object.
When the main call is traced and SIPREC is invoked based on a matching criteria, if the flag sipRecLegsCapture
is set to enabled
:
- For single and DUAL SIPRec calls:
- The media packets of the main call's leg (non-SIPRec side) and the SIPRec legs are logged in
.PKT
file. - The
.TRC
file contains SIP Protocol Data Units (PDUs) for SIPRec calls, as well as tracing data of the main call (depending on the level of the trace).
- The media packets of the main call's leg (non-SIPRec side) and the SIPRec legs are logged in
- For QUAD SIPRec calls:
- Packets are not captured for the main call and the
.PKT
files do not have the media of the main call. However, media packets of the SIPRec legs are logged in the.PKT
files. - The
.TRC
file contains SIP PDUs for SIPRec calls, as well as tracing data of the main call (depending on the level of the trace).
- Packets are not captured for the main call and the
Behavior of sipRecLegsCapture based on Call Trace Filter Level
The effect of enabling the flag sipRecLegsCapture
varies based on the level of the call trace filter, as described in the table below:
Content of PKT file based on SIPRec Criteria and Number of Simultaneous Sessions
If call trace is triggered for filter level 1, 2, or 3, the information captured in .PKT
file varies based on the SIPRec criteria and the number of simultaneous SIPRec sessions, as described in the table below:
Overview
Content Tools