Session Initiation Protocol (SIP) Recording Call Flows
RFC 8068

Document Type RFC - Informational (February 2017; No errata)
Last updated 2017-02-28
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Andrew Hutton
Shepherd write-up Show (last changed 2016-10-17)
IESG IESG state RFC 8068 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Andrew Hutton" <andrew.hutton@unify.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                   R. Ravindranath
Request for Comments: 8068                           Cisco Systems, Inc.
Category: Informational                                     P. Ravindran
ISSN: 2070-1721                                           Nokia Networks
                                                              P. Kyzivat
                                                                  Huawei
                                                           February 2017

         Session Initiation Protocol (SIP) Recording Call Flows

Abstract

   Session recording is a critical requirement in many communications
   environments, such as call centers and financial trading
   organizations.  In some of these environments, all calls must be
   recorded for regulatory, compliance, and consumer-protection reasons.
   The recording of a session is typically performed by sending a copy
   of a media stream to a recording device.  This document lists call
   flows with metadata snapshots sent from a Session Recording Client
   (SRC) to a Session Recording Server (SRS).

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8068.

Ravindranath, et al.          Informational                     [Page 1]
RFC 8068                SIP Recording Call Flows           February 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Overview ........................................................3
   2. Terminology .....................................................3
   3. Metadata XML Instances ..........................................3
      3.1. Sample Call Flow ...........................................3
      3.2. Call Scenarios with SRC Recording Streams without Mixing ...5
           3.2.1. Example 1: Basic Call ...............................5
           3.2.2. Example 2: Hold/Resume ..............................9
           3.2.3. Example 3:Call Transfer (RE-INVITE and
                  REFER Based) .......................................12
           3.2.4. Example 4: Call Disconnect .........................19
      3.3. Call Scenarios with SRC Recording Streams by Mixing .......20
           3.3.1. Example 1: Basic Call with SRC Mixing Streams ......20
           3.3.2. Example 2: Hold/Resume with SRC Recording
                  by Mixing Streams ..................................23
           3.3.3. Example 3: Metadata Snapshot of
                  Joining/Dropping of a ..............................25
           3.3.4. Example 4: Call Disconnect .........................28
      3.4. Call Scenarios with Persistent RS between SRC and SRS .....28
           3.4.1. Example 1: Metadata Snapshot during CS
                  Disconnect with ....................................29
      3.5. Turret-Case: Multiple CS into Single RS with Mixed
           Stream ....................................................30
   4. Security Considerations ........................................32
   5. IANA Considerations ............................................32
   6. References .....................................................33
      6.1. Normative References ......................................33
      6.2. Informative References ....................................33
   Acknowledgements ..................................................34
   Authors' Addresses ................................................34

Ravindranath, et al.          Informational                     [Page 2]
RFC 8068                SIP Recording Call Flows           February 2017
Show full document text