Page History

...

• LI and SIPREC can be used simultaneously on a call if LI is using MCAST. However, if LI uses Splitter, SIPREC config is ignored by the

  Spacevars
  0 product

  .
• Old NICE and SIPREC recordings cannot co-exist because both use Splitter. If SIPREC recording is in progress, NICE INVITE generally comes late (after the call is answered) and rejected by

  Spacevars
  0 product

  if other is present.
• MCT and SIPREC use the same trigger logic from PSX. PSX returns the recorder profile of the best matched criteria. When matching criteria, SIPREC is given the highest score. So if both SIPREC and MCT are configured, PSX returns the recorder profile of SIPREC. So, if a SIPREC call has to be debugged, MCT has to be triggered by CLI using GCID and in this case MCT uses MCAST.
• Call trace with Packet capture feature stops when any of the other features are being used.
• When Call Trace with the filter Media Capture is enabled, it captures the media packets into .PKT files for both Ingress and Egress legs.
• Features like LI, SIPREC, and NICE can be triggered after the call is established and Call Trace starts capturing packets for both Ingress and Egress legs. In this case, the requested leg for higher priority Call Recording feature is intercepted/recorded, and other legs are captured in .PKT file.

• Once the higher priority Call Recording ends for the call, the SBC does not go back to Call Recording of lower priority for the same call.

  When the Call Trace feature is enabled and any of the recording features are triggered, the behavior of the SBC is as shown in the table below:

  Caption
  0 Table 1 Behavior of the SBC when Call Trace is enabled and Call Recording is triggered.
  Feature   Behavior of the SBC when Call Trace is enabled and Call Recording is triggered LI   IMS LI TCP/UDP Calling number target: Ingress leg is intercepted to LI server. Egress leg packet is captured in a .PKT file as Call Trace is enabled. Called number target: Egress leg is intercepted to LI server. Ingress leg media streams are captured in a .PKT file as Call Trace is enabled. Calling & Called number target: Both Ingress and Egress legs are intercepted to LI server. In this case, capturing of media packets to .PKT files are not take place even if Call Trace is enabled. Verizon LI TCP/UDP LI request in INVITE: Ingress leg is intercepted to LI server. Egress leg packet is captured in a .PKT file as Call Trace is enabled. LI request in 18x/200: Egress leg is intercepted to LI server. Ingress leg media streams are captured in a .PKT file as Call Trace is enabled. LI request in Re-INVITE:  For initial Invite, both legs are captured to a .PKT file as Call Trace is enabled. After Re-Invite, the media streams of the Ingress leg is intercepted to LI server. The media stream of the Egress leg continues to be captured by Call Trace feature. Comcast LI UDP P-DCS-LAES header received in 18x: Media streams of the Egress leg are sent to the recorder. Media streams of the Ingress leg are captured in .PKT files as the state of Call Trace is enabled. NICE/SIPREC NICE Request to record Ingress leg: Media streams of Ingress leg are sent to NICE server. Media streams of Egress leg are captured in .PKT files as Call Trace is enabled. Request to record Egress leg: Media streams of Egress leg are sent to NICE server. Media streams of Ingress leg are captured in .PKT files as Call Trace is enabled. Request to record both legs: Media streams of both Ingress and Egress leg are sent to NICE server.  In this case, capturing of media packets in a .PKT file due to Call Trace does not take place. SIPREC PSX TRIGGER to record Ingress leg: Media streams of Ingress leg are sent to SIPREC server. Media streams of Egress leg are captured in .PKT files as Call Trace is enabled. PSX TRIGGER to record Egress leg: Media streams of Egress leg are sent to SIPREC server. Media streams of Ingress leg are captured in .PKT files as Call Trace is enabled. CLI trigger to record Ingress leg: Unless a CLI trigger is received, media of both Ingress and Egress legs are captured in .PKT file. Once a SIPREC CLI trigger is received for the Ingress leg, media streams of the Ingress leg are sent to SIPREC server. Egress leg continues to be captured in .PKT files. CLI trigger to record Egress leg: Unless a CLI trigger is received, media of both Ingress and Egress legs are captured in .PKT files. Once a SIPREC CLI trigger is received for Egress leg, media streams of Egress leg are sent to SIPREC server. Ingress leg continues to be captured in .PKT files. MCT PSX TRIGGER to record Ingress leg: Media streams of Ingress leg are sent to SIPREC server. Media streams of Egress leg are captured in .PKT files. MCT captures media on the Ingress leg using MCAST. Packet Capture will capture media on both the legs using Splitter. PSX TRIGGER to record Egress leg: Media streams of Egress leg are sent to SIPREC server. Media streams of Ingress leg are captured in .PKT files. MCT captures media on the Egress leg using MCAST. Packet Capture will capture media on both the legs using Splitter. PSX TRIGGER to record both legs: Media streams of both Ingress and Egress leg are sent to SIPREC server.  In this case, capturing of media packets in a .PKT file due to Call Trace does not take place MCT captures media on both the legs using MCAST. Packet Capture will capture media on both the legs using Splitter.

  Note
  MCT uses MCAST when Splitter is used by another recorder.

SBC Configuration

SIPREC configuration is based on the current MCT configuration available in PSX/ePSX using the same Recording Criteria and Recorder profiles to control which calls are to be recorded.

...