UC LabFree University

T10 · T10-R02

SIPREC and CUBE as the recording client

ExportSVGPNGHTMLSheet

Learn it in 5 minutes

  • RFC 7245 describes architectures for recording in a SIP environment by sending a copy of a media stream to a recording device.
  • RFC 7865 describes the metadata the session recording server sees. RFC 7866 is the session recording protocol.
  • RFC 7866 introduces the siprec option tag. An SRC puts it in Require so a peer that does not support the extension can reject the INVITE.
  • The CUBE IOS XE 17.6 guide says CUBE acts as the session recording client and any third-party recorder acts as the recording server.
  • That guide cites RFC 7245 section 3.1.1, and it cites the SIPREC metadata and protocol drafts. Confirm the guide for the release you run.
ExportSVGPNGHTMLSheet

Visual

SIPREC and CUBE as the recording client diagram
ExportSVGPNGHTMLSheet

What is going on

Keep the call and the recording session apart. The human call is one dialog. The recording session is another SIP relationship whose job is to carry a copy and the metadata. RFC 7866 says a recording-aware participant can use the record-aware option and the SDP a=record attribute, and that a participant who is not recording-aware still needs an indication by some other means, such as a tone. The CUBE guide says that if SIPREC is not configured, CUBE falls back to its network-based recording implementation. It also says CUBE supports the siprec option tag and the src feature tag, and does not support the SDP extensions in the protocol draft it cites. Do not tell an operator the draft and the RFC are the same text.

Confirm before relying. Confirm the metadata draft or RFC your recorder and IOS release actually implement.

ExportSVGPNGHTMLSheet

Worked example

A recorder answers the recording INVITE and the agent hears the caller. The file has audio and no party names. Metadata is the missing piece RFC 7865 is about. A tone, or the absence of one, is a different requirement from RFC 7866, not a codec problem.

ExportSVGPNGHTMLSheet

Quiz

1. The recording INVITE is the same dialog as the call being recorded.

ExportSVGPNGHTMLSheet

Ecosystem

Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the sibling labs.

  • SRC — Session recording client. The CUBE guide says CUBE takes this role when SIPREC is configured.
  • SRS — Session recording server. RFC 7865 describes metadata from the server's point of view.

Config. Name the dial peer toward the recorder and whether the profile says siprec.

Troubleshooting. If the recorder returns 420 Bad Extension, it rejected the siprec option. That is the RFC 7866 failure, not a WAN drop.

Bridge. CUCM network-based recording and CUBE SIPREC can both be present. Say which box starts the recording session.

Mind map, sister technologies, and future hooks live on the ecosystem page.

ExportSVGPNGHTMLSheet

Sources

Product screens move. Confirm the guide for your release before you change a live system.

ExportSVGPNGHTMLSheet

Sources and go deeper

Opened 2026-10. A row marked confirm has no link, because that page was not verified.

sources.json Markdown