Skip to end of metadata
Go to start of metadata

To support regulatory compliance and quality control purposes for call centers and financial institutions, the SBC Core supports session recording by sending a copy of the RTP stream of the call to be recorded to an external recording device.

The SBC does not participate in the decision process of which calls need to be recorded. Instead, it receives information about calls to be recorded via an enhanced SIP interface as defined by NICE Systems. NICE uses call ID, calling DN and UCID (Unique Call ID) to identify the recording session. This format supports Avaya recording.

The SBC supports session recording functionality only if media is anchored in SBC. If direct media is applied, RTP streams do not flow through the SBC, and the SBC cannot duplicate RTP packets.

DN matching is performed based on “P-asserted-identity”, “p-preferred-identity”, “From” header or “To” header. This is configured at the SIP Trunk Group level using the ‘Recording DNpreference’ command.

The NICE recorder supports the following codecs:

  • G.711
  • G.729
  • G723_6.3
  • G723_5.3
  • G.722


NICE and Media Packet Capture cannot be used simultaneously because the Splitter resource can only be configured for one feature.


The SBC supports up to 32,000 session recordings for both SIPREC and NICE.


To enable/disable a SIP Signaling Port to allow recording, use CLI syntax:

% set addressContext <addressContext_name> zone <zone_name> sipSigPort <index> recorder <disabled | enabled>


Refer to Zone - SIP Sig Port - CLI or Signaling Ports - Sip Sig Port (EMA) for configuration details.


To enable/disable recording from SIP trunk group, use CLI syntax:

% set addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <TG_NAME> media recordable <disabled | enabled>


Refer to SIP Trunk Group - Media - CLI or SIP Trunk Group - Media (EMA) for configuration details.