> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/tools/vcon-siprec-adapter.md).

# vCon SIPREC Adapter

**Repo:** [vcon-dev/vcon-siprec-adapter](https://github.com/vcon-dev/vcon-siprec-adapter)

SIPREC (RFC 7245 / RFC 7866) is the IETF standard for SIP-based call recording. This adapter consumes a SIPREC stream — both the recorded media and the signaling metadata — and produces a vCon with the [SIP Signaling extension](/extensions/sip-signaling.md) populated.

## When to use it

* You're running SIPREC in a contact center or carrier environment and want vCons as the durable output.
* You need STIR/SHAKEN attestation data, SIP Call-IDs, and SDP preserved alongside the recording for fraud investigation or TRACED Act compliance.
* You're correlating vCons with carrier-side CDRs.

## What you get

For each SIPREC session, the adapter produces a vCon with:

* A `dialog[]` entry of type `recording`, with the media as external (URL + SHA-512 hash) and the SIPREC-specific dialog fields populated (`sip_call_id`, `sip_from_tag`, `sip_to_tag`, `sip_cseq`).
* A `parties[]` array with `sip`, `sip_contact`, `sip_user_agent`, and `sip_display_name` for each participant.
* `attachments[]` containing the raw INVITE, the SDP, any STIR PASSporTs, and STIR verification reports — each tagged with the appropriate `purpose:` (`sip-invite`, `sip-sdp`, `stir-passport-extended`, etc.).
* `extensions: ["sip-signaling"]`.

## Spec status

The adapter is part of the May 2026 post-speckit-re-audit batch (commit history shows the field-name compliance pass on 2026-05-10). Output matches the current [SIP Signaling extension](/extensions/sip-signaling.md) draft.

## See also

* [SIP Signaling extension](/extensions/sip-signaling.md) — the spec the adapter produces against
* [Authenticating and Certifying Conversations](/use-cases-studies/authenticating-and-certifying-conversations.md) — the STIR/SHAKEN integration story


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.conserver.io/tools/vcon-siprec-adapter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.