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
.PKTfile. - The
.TRCfile 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
.PKTfiles do not have the media of the main call. However, media packets of the SIPRec legs are logged in the.PKTfiles. - The
.TRCfile 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:
Behavior of sipRecLegsCapture based on Call Trace Filter Level
| Call Trace Filter level | State of sipRecLegsCapture flag | Result |
|---|---|---|
| Level 1/2/3 | enabled | If the main call is traced by the same call filter, the SBC captures SIPRec SIP PDUs in |
| Level 1/2/3 | disabled | The SBC captures neither SIP PDUs in |
| Level 4 | enabled/disabled | SIP PDUs only for the specified peer IP are captured in If the peer IP is same as the SRS IP, all SIP PDUs from and towards that SRS are captured. If the peer IP is an end point, all SIP PDUs from and towards that end point are captured. If the peer IP is |
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:
Content of PKT file based on SIPRec Criteria and Number of Simultaneous Sessions
| SIPRec Recording Type | Number of simultaneous SIPRec sessions | State of sipRecLegsCapture flag | Information captured in PKT file |
|---|---|---|---|
| All legs/Ingress | 1 | enabled | Egress leg media packets of the main call, and media packets of SIPREC legs. |
| All legs/Ingress | 1 | disabled | Egress leg media packets of the main call. |
| All legs/Ingress | 2 (DUAL SIPREC) | enabled | Egress leg media packets of the main call, and media packets of SIPREC legs. |
| All legs/Ingress | 2 (DUAL SIPREC) | disabled | Egress leg media packets of the main call. |
| All legs/Ingress | 4 (QUAD SIPREC) | enabled | Media packets of only SIPREC legs. |
| All legs/Ingress | 4 (QUAD SIPREC) | disabled | No media packets are captured. |
| Egress | 1 | enabled | Ingress leg media packets of the main call, and media packets of SIPREC legs. |
| Egress | 1 | disabled | Ingress leg media packets of the main call. |
| Egress | 2 (DUAL SIPREC) | enabled | Ingress leg media packets of the main call, and media packets of SIPREC legs. |
| Egress | 2 (DUAL SIPREC) | disabled | Ingress leg media packets of the main call. |
| Egress | 4 (QUAD SIPREC) | enabled | Media packets of only SIPREC legs. |
| Egress | 4 (QUAD SIPREC) | disabled | No media packets are captured. |
Overview
Content Tools