--- title: vCon | Virtualized Conversations | ECG description: ECG helps service providers, contact centers, and enterprises build for vCon now, so you don't get locked into a recording vendor you can't escape later. --- [![ECG](https://www.ecg.co/hubfs/lp/cloud-migration/logo-vector.svg)](https://www.ecg.co?hsLang=en) - Who We Are Company [**About ECG** Learn about the team behind the networks and services that solve real problems.](https://www.ecg.co/about?hsLang=en) [**Careers** Join a fun, collaborative, engineer-owned company.](https://www.ecg.co/careers?hsLang=en) Industries We Serve [**Enterprises** Optimize multi-site voice networks while meeting compliance requirements.](https://www.ecg.co/sectors/enterprise?hsLang=en) [**Universities** Professional services designed for the unique needs of campus networks.](https://www.ecg.co/sectors/universities?hsLang=en) [**Government** Engineering services built for government agency voice challenges.](https://www.ecg.co/sectors/government?hsLang=en) [**Service Providers** Deep voice expertise to maintain compliance and keep customers connected.](https://www.ecg.co/sectors/service-providers?hsLang=en) - Technologies **Carrier & Trunking Services** SIP trunking, resilience & carrier interconnect **Compliance & Call Authentication** STIR/SHAKEN, 603+ & secure signaling **Unified Communications & Collaboration** UC capabilities & platform expertise **Platform Reliability & Security** Infrastructure, capture & network fundamentals ### Carrier & Trunking Services Design, harden, and secure the carrier side of your voice network — from SIP trunking to encrypted media and compliant recording. [SIP Trunking](https://www.ecg.co/technologies/sip-trunking-consulting-expertise?hsLang=en) [SIP Trunking High Availability](https://www.ecg.co/technologies/sip-trunking-high-availability?hsLang=en) [STIR/SHAKEN](https://www.ecg.co/technologies/stir-shaken?hsLang=en) [603+](https://www.ecg.co/technologies/603-plus-do-not-originate?hsLang=en) [eSIM & FMC](https://www.ecg.co/technologies/esim-fmc?hsLang=en) [VoIP TLS & SRTP](https://www.ecg.co/technologies/voip-encryption-tls-srtp?hsLang=en) [SIPREC](https://www.ecg.co/technologies/siprec-call-recording?hsLang=en) ### Compliance & Call Authentication Meet regulatory requirements end-to-end — call authentication, robocall mitigation, lawful capture, and encrypted signaling. [STIR/SHAKEN](https://www.ecg.co/technologies/stir-shaken?hsLang=en) [603+](https://www.ecg.co/technologies/603-plus-do-not-originate?hsLang=en) [Packet Capture / PCAP](https://www.ecg.co/technologies/pcap-wireshark-packet-capture-analysis?hsLang=en) [VoIP TLS & SRTP](https://www.ecg.co/technologies/voip-encryption-tls-srtp?hsLang=en) ### Unified Communications & Collaboration Modern UC capabilities backed by deep, hands-on expertise across every major voice platform. [E911](https://www.ecg.co/technologies/e911?hsLang=en) [Business Texting](https://www.ecg.co/technologies/business-texting?hsLang=en) [Teams Replace Phone System](https://www.ecg.co/technologies/ms-teams-replace-phone-system?hsLang=en) [Provisioning & Endpoint Mgmt](https://www.ecg.co/technologies/sip-provisioning-endpoint-management?hsLang=en) [Call Control & Features](https://www.ecg.co/technologies/call-control-features?hsLang=en) [SIP Trunking HA](https://www.ecg.co/technologies/sip-trunking-high-availability?hsLang=en) [SIPREC](https://www.ecg.co/technologies/siprec-call-recording?hsLang=en) [vCon](https://www.ecg.co/technologies/vcon-virtualized-conversations) Platform Expertise [BroadWorks](https://www.ecg.co/technologies/broadworks?hsLang=en) [NetSapiens](https://www.ecg.co/technologies/netsapiens-support?hsLang=en) [Metaswitch Alianza Core](https://www.ecg.co/technologies/metaswitch-alianza-core?hsLang=en) [Oracle Communications](https://www.ecg.co/technologies/oracle-communications-support?hsLang=en) [Metaswitch Perimeta](https://www.ecg.co/technologies/metaswitch-perimeta?hsLang=en) [Sansay VSXi](https://www.ecg.co/sansay-vsxi-session-border-controller?hsLang=en) ### Platform Reliability & Security The infrastructure layer underneath your voice services — engineered, monitored, and secured by people who run it every day. [EKS / Kubernetes](https://www.ecg.co/technologies/kubernetes-eks?hsLang=en) [Critical Network Fundamentals](https://www.ecg.co/technologies/critical-network-fundamentals?hsLang=en) [Packet Capture / PCAP](https://www.ecg.co/technologies/pcap-wireshark-packet-capture-analysis?hsLang=en) [VMware & Alternatives](https://www.ecg.co/technologies/vmware-alternatives?hsLang=en) [Routing, Switching & Firewalls](https://www.ecg.co/technologies/routing-switching-firewalls?hsLang=en) [Freeswitch](https://www.ecg.co/technologies/freeswitch-open-source-call-processing?hsLang=en) - How We Do It Services [**Services Overview** Our experience and expertise in voice and data engineering.](https://www.ecg.co/services?hsLang=en) [**Network Operations** Keep your voice network running with outsourced network operations.](https://www.ecg.co/services/network-operations?hsLang=en) [**Staff Augmentation** Expert engineering support to meet deadlines and fill knowledge gaps.](https://www.ecg.co/services/staff-augmentation?hsLang=en) [**IT Consulting & Engineering** Complete short-term projects faster with a dedicated project manager.](https://www.ecg.co/services/it-consulting-and-engineering?hsLang=en) - Resources #### [Utilities Launch Delay Calculator Estimate what a potential product launch delay would cost your business. Try the calculator](https://www.ecg.co/cost-delay-calculator?hsLang=en) #### [Resource Library Guides, White Papers & Tools In-depth resources on voice engineering, compliance, and AI — built from real client work. Explore resources](https://www.ecg.co/resource-library?hsLang=en) #### [Blog Latest from the ECG Team Practical articles on SIP, UC platforms, network operations, and voice AI. Read the blog](https://www.ecg.co/blog?hsLang=en) - [Events](https://www.ecg.co/events?hsLang=en) [Login](https://portal.ecg.co) [Contact](https://www.ecg.co/contact?hsLang=en) Who We Are [About ECG](https://www.ecg.co/about?hsLang=en) [Careers](https://www.ecg.co/careers?hsLang=en) Industries We Serve [Enterprises](https://www.ecg.co/sectors/enterprise?hsLang=en) [Universities](https://www.ecg.co/sectors/universities?hsLang=en) [Government](https://www.ecg.co/sectors/government?hsLang=en) [Service Providers](https://www.ecg.co/sectors/service-providers?hsLang=en) Technologies Carrier & Trunking Services [SIP Trunking](https://www.ecg.co/technologies/sip-trunking-consulting-expertise?hsLang=en) [SIP Trunking High Availability](https://www.ecg.co/technologies/sip-trunking-high-availability?hsLang=en) [STIR/SHAKEN](https://www.ecg.co/technologies/stir-shaken?hsLang=en) [603+](https://www.ecg.co/technologies/603-plus-do-not-originate?hsLang=en) [eSIM & FMC](https://www.ecg.co/technologies/esim-fmc?hsLang=en) [VoIP TLS & SRTP](https://www.ecg.co/technologies/voip-encryption-tls-srtp?hsLang=en) [SIPREC](https://www.ecg.co/technologies/siprec-call-recording?hsLang=en) Compliance & Call Authentication [STIR/SHAKEN](https://www.ecg.co/technologies/stir-shaken?hsLang=en) [603+](https://www.ecg.co/technologies/603-plus-do-not-originate?hsLang=en) [Packet Capture / PCAP](https://www.ecg.co/technologies/pcap-wireshark-packet-capture-analysis?hsLang=en) [VoIP TLS & SRTP](https://www.ecg.co/technologies/voip-encryption-tls-srtp?hsLang=en) Unified Communications & Collaboration [E911](https://www.ecg.co/technologies/e911?hsLang=en) [Business Texting](https://www.ecg.co/technologies/business-texting?hsLang=en) [Teams Replace Phone System](https://www.ecg.co/technologies/ms-teams-replace-phone-system?hsLang=en) [Provisioning & Endpoint Mgmt](https://www.ecg.co/technologies/sip-provisioning-endpoint-management?hsLang=en) [Call Control & Features](https://www.ecg.co/technologies/call-control-features?hsLang=en) [SIP Trunking HA](https://www.ecg.co/technologies/sip-trunking-high-availability?hsLang=en) [SIPREC](https://www.ecg.co/technologies/siprec-call-recording?hsLang=en) [vCon](https://www.ecg.co/technologies/vcon-virtualized-conversations) Platform Expertise [BroadWorks](https://www.ecg.co/technologies/broadworks?hsLang=en) [NetSapiens](https://www.ecg.co/technologies/netsapiens-support?hsLang=en) [Metaswitch Alianza Core](https://www.ecg.co/technologies/metaswitch-alianza-core?hsLang=en) [Oracle Communications](https://www.ecg.co/technologies/oracle-communications-support?hsLang=en) [Metaswitch Perimeta](https://www.ecg.co/technologies/metaswitch-perimeta?hsLang=en) [Sansay VSXi](https://www.ecg.co/sansay-vsxi-session-border-controller?hsLang=en) Platform Reliability & Security [EKS / Kubernetes](https://www.ecg.co/technologies/kubernetes-eks?hsLang=en) [Critical Network Fundamentals](https://www.ecg.co/technologies/critical-network-fundamentals?hsLang=en) [Packet Capture / PCAP](https://www.ecg.co/technologies/pcap-wireshark-packet-capture-analysis?hsLang=en) [VMware & Alternatives](https://www.ecg.co/technologies/vmware-alternatives?hsLang=en) [Routing, Switching & Firewalls](https://www.ecg.co/technologies/routing-switching-firewalls?hsLang=en) [Freeswitch](https://www.ecg.co/technologies/freeswitch-open-source-call-processing?hsLang=en) How We Do It Services [Services Overview](https://www.ecg.co/services?hsLang=en) [Network Operations](https://www.ecg.co/services/network-operations?hsLang=en) [Staff Augmentation](https://www.ecg.co/services/staff-augmentation?hsLang=en) [IT Consulting & Engineering](https://www.ecg.co/services/it-consulting-and-engineering?hsLang=en) Resources [Launch Delay Calculator](https://www.ecg.co/cost-delay-calculator?hsLang=en) [Guides, White Papers & Tools](https://www.ecg.co/resource-library?hsLang=en) [Latest from the ECG Team](https://www.ecg.co/blog?hsLang=en) [Events](https://www.ecg.co/events?hsLang=en) [Login](https://portal.ecg.co) [Contact](https://www.ecg.co/contact?hsLang=en) # vCon (Virtualized Conversation) for Portable Conversation Data We help service providers, contact centers, and enterprises build for vCon now, so you don't get locked into a recording vendor you can't escape later. [consult ecg](https://www.ecg.co/contact?hsLang=en) What We Provide ## vCon Implementation, Integration, and Standards Expertise Our engineers work with the IETF vCon working group and have built vCon ingestion in production for our award-winning AI call-summary product – so we know where the standard has rough edges and how to fix them. ![icon-vcon-2-1](https://www.ecg.co/hubfs/icon-migration.svg) #### vCon Ingestion and Emission We build ingestion endpoints that accept SIPREC streams, vendor exports, or native recordings and emit well-formed vCons with correct parties, dialog, analysis, and attachments sections. ![icon-vcon-2-2](https://www.ecg.co/hubfs/ecg-site/sip%20trunking%20HA/icon-siptrunkingHA-2-3.svg) #### Transcription and Analysis Extensions We implement vCon transcription and analysis extensions that hold up as the IETF spec tightens and avoid the vendor-by-vendor drift that complicates SIPREC interop. ![icon-vcon-2-3](https://www.ecg.co/hubfs/ecg-site/E911/icon-e911-2-2.svg) #### Consent and Lawful-Basis Compliance  We design consent capture, signing, and retention end-to-end so consent metadata travels with the vCon for two-party-consent and GDPR/CCPA compliance.  ![icon-vcon-2-4](https://www.ecg.co/hubfs/ecg-site/icon-callreporter-1.svg) #### vCon Lifecycle and Audit Ledgers We build ledger integration using SCITT transparency ledgers so you can prove which vCons were processed by which AI models at which times for legal hold and auditability. ![icon-vcon-2-5](https://www.ecg.co/hubfs/ecg-site/automation-tools/icon-userfriendly.svg) #### CRM and Enterprise App Integration Once your conversation data is a vCon, we wire it into Salesforce, HubSpot, Zendesk, Slack, ServiceNow, and other systems without custom integrations. ![icon-vcon-2-6](https://www.ecg.co/hubfs/ecg-site/network-operations/icon-voicecustomerservice.svg) #### Contact Center vCon Implementation We map your contact center data model (agents, supervisors, disposition codes, campaign tagging) into the cc-extension so vCons are useful to downstream WFO, QM, and speech analytics.  Built to Fix vCon Challenges # Your Virtual Conversation Problems, Solved Call recording is fragmented across vendor silos, with each platform producing proprietary metadata formats, APIs, and export structures. ECG solves the technical and architectural complexity, so you can avoid the headaches. ![icon-vcon-3-1](https://www.ecg.co/hubfs/ecg-site/home/icon-home-5-5.svg) #### Changing Privacy and Compliance Standards Building systems without privacy-by-design means compliance rework later. We design consent capture, signing, and data-flow architecture so privacy travels with the conversation. ![icon-vcon-3-2](https://www.ecg.co/hubfs/ecg-site/home/icon-home-5-2.svg) #### Vendor Lock-In on Call Recording Don't want your data to live inside proprietary recording silos with undocumented APIs? vCon breaks the silo by providing the bridge layer that gets your data out for AI processing or migration. ![icon-vcon-3-3](https://www.ecg.co/hubfs/ecg-site/home/icon-home-5-4.svg) #### AI Integration Paralysis Audio, metadata, and APIs are often fragmented across vendors. vCon-shaped data structures give your AI pipeline a stable input contract so LLMs and ASR don't need vendor-specific logic.  ![icon-vcon-3-4](https://www.ecg.co/hubfs/icon-broadworkstechnologies-3-2%20(2).svg) #### One-Way Vendor Migration Recording vendor migration tooling doesn't exist. With vCon as the export format, migration becomes as straightforward as "produce vCons from the old system, ingest into the new system." ![icon-vcon-3-5](https://www.ecg.co/hubfs/ecg-site/Voicemail%20Transcription/icon-voicemailtranscription-3-6.svg) #### Multi-Channel Conversation Reconstruction Calls transferred from chat to voice to email live in separate systems. vCon's container model handles multiple media types and attachments, but you need integration work to join them.  ![icon-vcon-3-6](https://www.ecg.co/hubfs/ecg-site/Packet%20Capture%20+%20Network%20Visibility/icon-packetcapture-3-1.svg) #### Limited Internal Expertise vCon is new, so most engineers haven't read the Internet-Draft, don't know what a SCITT receipt is, and aren't tracking the working group mailing list. We fill the gap with engineers who are actively involved in the standard. OUR CLIENTS ## Trusted by Industry Leaders Join other organizations that enjoy expert engineering support with ECG. ![Maryland\_Logo\_rgb\_white](https://www.ecg.co/hubfs/Maryland_Logo_rgb_white.svg) ![logo-usdeptofjustice](https://www.ecg.co/hubfs/logo-usdeptofjustice.svg) ![segra](https://www.ecg.co/hubfs/segra.svg) ![momentum-logo-white](https://www.ecg.co/hubfs/momentum-logo-white.svg) ![KPU-Logo-white](https://www.ecg.co/hs-fs/hubfs/KPU-Logo-white.png?width=113&height=100&name=KPU-Logo-white.png) ![vcon-5-1](https://www.ecg.co/hubfs/ecg-site/vCon/vcon-5-1.jpg "vcon-5-1") WHY CHOOSE ECG ## vCon Expertise From the IETF Working Group **We help you actually use vCon – not just nod along at the standard.** ECG sits on the IETF Virtualized Conversations working group, where we've pushed for stricter standardization on the transcription format because we've seen what under-specified standards cause. We're not betting on vCon – we've already shipped vCon ingestion in production inside Wingman, our AI call-summary product that won a Frost & Sullivan award. When you bring ECG in, you get engineers who understand the full protocol stack (SIP, SIPREC, RTP, SBCs) and the vCon layer on top, not specialists in separate domains handing off to each other.  [learn more](https://www.ecg.co/contact?hsLang=en) ## Success Stories From Our Clients ECG is definitely the right team for our network! Nicole Rodriguez AVP Switching and Wireless Data Engineering | AT&T Mobility ECG's broad scope of clients means they know what's happening before we do. We stay competitive with ECG as our guide. Mark Hayes VP of Voice Engineering | Momentum Telecom ECG has really cool technology! Jeff Pulver Voice over IP Pioneer ECG delivers exceptional quality and service via their software products and consulting services. Speaking as someone with direct large scale enterprise delivery with their team, my personal experience has been universally positive. Joe Pfiefer Assistant Director | U.S. Department of Justice I'm happy to say I've partnered with ECG at a number of service providers. You guys have been an outstanding engineering and operations partner for my teams. Tom Faherty VP | Databank ECG is a reliable partner. Edwin Martirosyan COO | BluIP [Book Consult](https://www.ecg.co/contact?hsLang=en) [learn more](https://www.ecg.co/about?hsLang=en) GET STARTED WITH ECG TODAY ## Book Your 30-Minute Connect Call Get in touch with ECG for products and services that support your crucial voice infrastructure needs.  ## Experience the ECG Advantage Whether you’re a service provider, enterprise, or government agency, your voice infrastructure is in good hands with ECG. ![\_Ñëîé\_1](https://www.ecg.co/hubfs/_%C3%91%C3%AB%C3%AE%C3%A9_1.svg) #### Proven Expertise Our team has decades of proven experience building and supporting voice networks. ![\_Ñëîé\_1](https://www.ecg.co/hubfs/_%C3%91%C3%AB%C3%AE%C3%A9_1.svg) #### Powerful Partnerships Our strategic alliances are designed to help deliver customer-centric, total solutions to our clients. ![\_Ñëîé\_1](https://www.ecg.co/hubfs/_%C3%91%C3%AB%C3%AE%C3%A9_1.svg) #### Elevated Network Design We draw from experience with dozens of service providers to create straightforward, manageable designs. ![\_Ñëîé\_1](https://www.ecg.co/hubfs/_%C3%91%C3%AB%C3%AE%C3%A9_1.svg) #### Comprehensive Support Our team will assist in your technical projects, support your goals, automate processes, and train your team. How We Help ## End-to-End vCon Architecture, Integration, and Production Support Most "we'll just adopt vCon" projects start with a proof-of-concept that ignores compliance extensions, then hit a wall at review. We start with the wall. ![vcon-9-1](https://www.ecg.co/hs-fs/hubfs/ecg-site/vCon/vcon-9-1.jpg?width=508&height=449&name=vcon-9-1.jpg) ### Designing vCon Architecture and Integration Standing up a vCon-aware conversation infrastructure properly requires understanding the IETF standard, your recording sources, your downstream consumers, and your privacy obligations.  - We design the vCon ingestion endpoint (SIPREC receiver, vendor export adapter, or native API integration) that reliably accepts call recordings and emits well-formed vCons without affecting call quality - We map participant data model into the vCon parties section and contact center extension fields so vCons carry the metadata your downstream tools actually need for QM, WFO, and speech analytics - We make compliance auditable by implementing consent extension capture and tying it to the vCon's digital signature, so consent travels cryptographically with the data - We wire vCon emission into your CRM, archive, AI pipeline, and compliance reporting with stable schema, retry logic, and visible error states ![SIPTrunking-9-2](https://www.ecg.co/hs-fs/hubfs/ecg-site/SIP%20Trunking/SIPTrunking-9-2.jpg?width=508&height=506&name=SIPTrunking-9-2.jpg) ### Troubleshooting vCon Ingestion and Transformation Failures When vCon ingestion fails, SIPREC streams aren't getting correlated into a single vCon, participants are missing, AI-generated analysis comes back malformed, or downstream consumers reject vCons that others accept, we will: - Run packet captures on the SIPREC traffic to confirm what the SBC is actually sending versus what your vCon emitter is interpreting, and reconcile metadata mapping discrepancies between recording sources - Validate emitted vCons against the current vcon-core JSON schema and relevant extensions, identifying which producer is generating non-conformant output and chasing down schema violations before they propagate downstream - Trace participant identity across SIP From/To headers, SIPREC rs-metadata XML, and STIR PASSporT when present, so the vCon parties section reflects who was actually on the call and the identity chain is verifiable - Investigate deduplication logic when the same conversation generates multiple vCons from multiple recording paths, and select the canonical record using deterministic criteria ![vcon-9-3](https://www.ecg.co/hs-fs/hubfs/ecg-site/vCon/vcon-9-3.jpg?width=508&height=449&name=vcon-9-3.jpg) ### Optimizing vCon Infrastructure and Unlocking Analytics Once vCon emission is working, the real value comes from integration depth, cost optimization, and analytics that weren't possible when conversation data was stuck in vendor silos. We help you: - Add embedding-based vector search across your vCon archive so users can find conversations by meaning, not just keyword string-match - Stand up vCon-based exchange between systems and partners so your conversation data moves between your platform, your customer's platform, and the AI vendor's platform without custom integration each way - Implement the lifecycle extension with SCITT-style transparency ledgers so AI training, model audit, and data deletion requests have a verifiable chain of custody - Migrate from paid third-party transcription/summary APIs to self-hosted ASR (Moonshine, Parakeet, Whisper) and locally hosted LLM that emit vCons natively Frequently Asked Questions ## Common vCon Questions, Answered Get quick answers to common questions about Virtual Conversation, how it differs from existing standards, and how to implement it reliably in production. What is a vCon? A vCon (Virtualized Conversation) is an IETF working-group standard for packaging a conversation – call, chat, video meeting, or SMS exchange – into a single portable, signable, encryptable JSON object. The virtual conversation meaning is that conversation data becomes an independent, vendor-neutral artifact with four major sections: parties (who participated), dialog (the actual messages and media references), analysis (transcript, summary, sentiment, extracted metadata), and attachments (files exchanged). Think of it as analogous to vCard, but for conversations instead of contact details. The point is that your conversation data shouldn't be locked inside one vendor's recording silo. The format is still being finalized as an IETF Internet Draft, but it's already mature enough to design for. ECG is involved in the working group and has shipped vCon in production, so we know which extensions are stable and which are still evolving.  How is vCon different from SIPREC? SIPREC is the protocol that captures the audio and metadata off the call path in real time and sends it to a recording server. vCon is the file format that the recording server (or anybody downstream) emits. They're complementary, not competitive. Where SIPREC says "here's a copy of the call audio and some metadata right now," vCon says "here's the whole conversation – audio reference, participants, transcript, analysis, attachments – packaged so anybody downstream can consume it without vendor-specific integration." A typical pipeline has SIPREC flowing into a recording engine, and the recording engine emits vCons to your AI pipeline, CRM, archive, and compliance system. SIPREC is settled as an RFC; vCon is moving toward standardization.  Will vCon become the standard, or is this another format that won't catch on? Nobody knows for sure, but the trajectory looks good. The IETF working group is active, and the contact center extension was specifically driven by real contact-center vendor input. The case is similar to SMS interop in the late 1990s. Once carriers could exchange SMS between networks, the format exploded. vCon is positioned the same way for conversation data. Whether it gets to RFC status in 2026 or 2027 or later, the direction is clear: if you build for vCon-shaped data, you're set whether the spec evolves or not. Can I use vCon with my existing call recording vendor?  Yes – that's exactly the use case we've built ingestion for. Most major recording vendors are now aware of vCon, and several are working on native emission. In the meantime, we build adapters that take their proprietary export format and produce conformant vCons. Once vCons are flowing from all your recording sources, your downstream pipeline (AI, archive, CRM, compliance) only has to understand one format. That's where integration savings show up.  Will vCon eventually lead to vendor lock-in? vCon is an IETF standard developed in an open working group, not a vendor format. The whole motivation for vCon is the opposite of vendor lock-in – it's the open container that lets you move conversation data between systems regardless of which vendor produced it. That said, individual vCon implementations can be done with proprietary extensions that nobody else parses. We've already seen this play out with SIPREC, where the standard is open, but interop between vendors is a constant battle due to metadata extensions. At ECG, we design vCon implementations to stay close to the spec and to use standard extensions where they exist, so your vCons stay portable. How does vCon help with GDPR and CCPA compliance? The vCon consent extension (lawful-basis extension) captures the lawful basis under which the conversation was recorded, the exact timestamps of consent capture, and (when required) the recorded consent announcement itself. Combined with the vCon parties section, this provides the metadata to answer "show me every conversation involving this customer and the consent state for each one" – which is what GDPR and CCPA require for data subject access and deletion requests. vCon by itself doesn't make you compliant, as you also need retention policies, access controls, and a deletion workflow. However, it's the format that makes the compliance program technically feasible.  How does vCon interact with STIR/SHAKEN? STIR PASSporTs identify the origination of a call – who placed it with what authority. The vCon specification explicitly references STIR PASSporT as part of the participant identity information you can preserve in the parties section. When a call arrives with a verified A-attestation PASSporT, that identity assertion can be preserved in the vCon instead of getting lost when the recording is exported to a separate system. For organizations that care about the chain of custody between caller identity and conversation content – fraud detection, compliance forensics – this is meaningful.  What is SCITT and why does it matter for vCon? SCITT (Supply Chain Integrity, Transparency, and Trust) is an IETF effort to standardize transparency ledgers – append-only, cryptographically verifiable logs of transformations applied to data artifacts. The vCon lifecycle extension uses SCITT-style ledgers so that every transformation of a vCon leaves a verifiable receipt signed by the system that performed it. For regulated workloads – financial services, healthcare, anything where a regulator can ask "what happened to this data and when?" – this creates chain-of-custody evidence. ECG can help you decide which side of that line your project sits on and build the ledger integration when it's required.  How does vCon handle AI analysis and downstream processing? The vCon analysis section is designed to carry AI-generated content like transcripts, summaries, sentiment analysis, action items, and any other extracted structured data. Each analysis entry references the dialog section it covers, names the producer, and is timestamped. When the regulator asks which conversations were used to train which model, the vCon analysis section combined with the lifecycle extension and SCITT receipts gives you the answer. Without this, AI compliance becomes nearly impossible at scale. What does it actually cost to implement vCon? That depends on your starting point. If you're already running SIPREC into a modern recording vendor, adding vCon emission is mostly an integration and schema-mapping project – measured in weeks, not months. If you're retrofitting a legacy proprietary recording stack, it's a bigger project. At ECG, we model the integration cost against your call volume and downstream consumer set before architecture decisions get locked in.  ## Ready to Experience the ECG Difference? Get in touch for products that support your crucial voice infrastructure needs. [GET IN TOUCH](https://www.ecg.co/contact?hsLang=en) [![ecg-logo-white](https://www.ecg.co/hubfs/ecg-site/global/ecg-logo-white.svg "ecg-logo-white")](https://www.ecg.co/?hsLang=en) 505 North Toombs St. Suite A Valdosta, Georgia 31601 USA #### Headquarters - 1.866.324.0700 US Toll-free - 1.229.244.2099 International - 1.229.244.2399 Fax - [info@e-c-group.com](mailto:info@e-c-group.com) #### Services - [Overview](https://www.ecg.co/services?hsLang=en) - [Network Operations](https://www.ecg.co/services/network-operations?hsLang=en) - [Custom AI Development](https://www.ecg.co/services/custom-ai-development?hsLang=en) - [Outsourced NOC Support](https://www.ecg.co/services/outsourced-noc-support?hsLang=en) - [Staff Augmentation](https://www.ecg.co/services/staff-augmentation?hsLang=en) - [IT Consulting & Engineering](https://www.ecg.co/services/it-consulting-and-engineering?hsLang=en) #### Company - [About](https://www.ecg.co/about?hsLang=en) - [Careers](https://www.ecg.co/careers?hsLang=en) - [Blog](https://www.ecg.co/blog?hsLang=en) - [Resources](https://www.ecg.co/resource-library?hsLang=en) - [Events](https://www.ecg.co/events?hsLang=en) © ECG, Inc. [Privacy Policy](https://9353907.hs-sites.com/privacy?hsLang=en)