Home / Toll fraud, E911, recording, and QoS / Disclosed recording with SIPREC
Disclosed recording with SIPREC
RFC 7866 is the recording protocol. RFC 7865 is the metadata. Notice and retention are legal questions.
Learn in 5 minutes
- Name SRC and SRS roles at a high level
- Keep metadata with RFC 7865
- Treat notice and retention as outside the RFC
Visual
The SBC may fork a session to a recording server. The parties are told.
Worked example
Separate the two Call-IDs Which Call-ID belongs to the recording session toward the SRS?
- Press Play.
- Step until the hop named in the question.
- Inspect that message and answer the check.
Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.
Fault
The SRS rejected the recording session. The ticket adds an XML tag that RFC 7865 was not opened to check, and it shortens retention in the same change.
488 says this SRS did not accept the session description or the recording body. Retention is not an RFC field.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Analytics Amazon Connect can attach conversational analytics to an external voice system with a SIPREC connector. The analytics plane is not a second SIP proxy for the customer call.