T10 · T10-R03
Compliance is a reason, not a setting
Learn it in 5 minutes
- RFC 7245 says some environments record every call for regulatory, compliance, and consumer-protection reasons.
- That sentence does not name your statute, your retention period, or your consent rule.
- A recording file, a quality score, and a pause during a card number are different objects. This lab did not open a payment-card standard.
- Notification of recording is part of SIPREC for recording-aware users, and the RFC also allows other indications. Your spoken notice is a local rule.
- No privacy statute was opened for this chapter. The confirm row has no link.
Visual
What is going on
Use the recording architecture to see whether a copy was made. Use counsel and the rule that applies to the site to decide whether you may make it, how long you keep it, and what you tell the caller. This page will not invent that rule. In a contact center the agent desktop, the CUCM line, and the recorder can disagree: the desktop shows a recording icon while the fork never left the phone, or the file exists while the score was never submitted. Debug the object that failed. UCCE and Webex Contact Center do not become the same recorder because both can sit next to a CUCM.
Confirm before relying. Confirm consent, retention, and any duty to pause a recording with the rule that applies where you operate.
Worked example
A supervisor says the call was not recorded. The phone's built-in bridge forked RTP, and the recorder has a file for that time. The missing object is the quality form, not the RTP. Changing the dial plan will not create the form.
Quiz
1. RFC 7245 chooses the retention period for your contact center.
False. It explains recording architectures. It does not set your policy.
Ecosystem
Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the sibling labs.
- Recording file — The stored copy of the media.
- Quality score — A review of a call. It is not the media file.
Config. Store the call id, the recorder, and the time next to any claim that a call was recorded.
Troubleshooting. If legal asks for a call, produce the file you have. Do not describe a score as the audio.
Bridge. Workforce management forecasts how many people you need. It does not store the audio.
Mind map, sister technologies, and future hooks live on the ecosystem page.
Sources
- RFC 7245, architecture for media recording using SIP
- RFC 7866, session recording protocol
- Feature Configuration Guide for CUCM, Release 15, Recording
Product screens move. Confirm the guide for your release before you change a live system.
Sources and go deeper
Opened 2026-10. A row marked confirm has no link, because that page was not verified.
- RFC. RFC 7245, architecture for media recording using SIP last checked 2026-10
- RFC. RFC 7866, session recording protocol last checked 2026-10
- Cisco. Feature Configuration Guide for CUCM, Release 15, Recording last checked 2026-10
- Law. Call-recording consent and retention rule. confirm. No privacy or retention statute was opened. RFC 7245 names compliance as a reason some sites record. It does not say which rule applies to you. last checked 2026-10