You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

To support regulatory compliance and quality control purposes for call centers and financial institutions, the

Unable to show "metadata-from": No such page "_space_variables"
supports session recording by sending a copy of the RTP stream of the call to be recorded to an external recording device.

The

Unable to show "metadata-from": No such page "_space_variables"
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

Unable to show "metadata-from": No such page "_space_variables"
supports session recording functionality only if media is anchored in SBC. If direct media is applied, RTP streams do not flow through the
Unable to show "metadata-from": No such page "_space_variables"
, and the
Unable to show "metadata-from": No such page "_space_variables"
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

Note

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

Session recording is used for various purposes such as complying with regulation, monitoring quality of service of representatives as well as storing call information for quality analysis.

The SBC Core supports the following proprietary SIP recording interfaces:

  • SIPREC SIP-based session recording
  • Call monitoring MCT
  • NICE session recording

Access to the Media Capture Tool is restricted to privileged, password-protected user accounts. Tracking of its use is tracked by AUD logging.

Note

The SBC can record all the calls in the system. The number of recording sessions depends on the available interface bandwidth.

 

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>
Info

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>
Info

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

  • No labels