Skip to main content

Contact Center Use Cases and Requirements for VCON
draft-rosenberg-vcon-cc-usecases-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Jonathan Rosenberg , Andrew Siciliano
Last updated 2024-01-09 (Latest revision 2023-07-08)
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This document outlines use cases and requirements for the exchange of VCONs (Virtual Conversation) within contact centers. A VCON is a standardized format for the exchange of call recordings and call metadata. Today, call recordings are exchanged between different systems within the contact center. Often, these are done using proprietary file formats and proprietary APIs. By using VCONs, integration complexity can be reduced.

Authors

Jonathan Rosenberg
Andrew Siciliano

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)