In this section:
What is SIP Recording (SIPREC)?
SIPREC is a recording capability which can be utilized for various purposes: to comply with regulation, to monitor quality of service of representatives, or to store call information for quality analysis. The
Unable to show "metadata-from": No such page "_space_variables"
supports SIPREC towards multiple recorders based on the Internet Engineering Task Force (IETF) standard.SIPREC supports the RFC standard for a SIP recording interface. To support SIPREC, the
Unable to show "metadata-from": No such page "_space_variables"
acts as a Session Recording Client (SRC) initiating a Recording Session (RS) towards a Session Recording Server (SRS). The Unable to show "metadata-from": No such page "_space_variables"
initiates a recording session for all the Communication Sessions (CS) to be recorded; it is established over SIP from the SRC to the SRS. The CS output is based on the Unable to show "metadata-from": No such page "_space_variables"
's WebUI configuration for enabling recording.SIP Recording (SIPREC) is supported in the
Unable to show "metadata-from": No such page "_space_variables"
for the following purposes: - Store call information for quality analysis.
- Record call and media sessions on a third party recording server.
- Check the call detail records and determine if a call is being recorded or not.
- Provide call detail records for recorded calls.
Terminology
Term | Definition |
---|---|
CS | Communication Session |
RS | Recording Session |
SRC | Session Recording Client |
SRS | Session Recording Server |
SIPREC does not support Fax.
Use Cases
Unable to show "metadata-from": No such page "_space_variables"
supports the following use cases (based on SIPREC RFC 7866 and RFC 6341)- Recording Sessions for a single audio media stream towards a single SRS (NICE SIPREC Server).
- Recording Sessions towards SRS for a basic call with priority given to the calling party side (ingress leg).
- Recording Sessions for Call Hold and Retrieve.
- Recording Sessions for Transferred calls.
- For all the call related use cases mentioned above, the appropriate metadata XML and SDP information is relayed to the SRS as part of the RS.
- Recording Encrypted RTP (SRTP) streams and sending related keys in the SDP towards the SRS as part of RS.
- Only Proxy (non-transcoding) media towards the SRS is supported.
- Only statically configured (non-dynamic) Recording Sessions are supported.
- Recording Signaling group polls the SRS server using existing OPTIONS mechanism; if SRS is unreachable, the corresponding alarm will be generated.
- Recording Signaling Group uses a subset of existing Signaling Group and SIP Server Table functionality to use listen ports, destination IP/FQDN, protocol and port etc., to communicate with the SRS.
- SWe Edge rejects INVITE, OPTIONS requests originating from SRS Servers.
Overview
Content Tools