SIPREC Mode (RFC 7245 SRS): Standard SIP Recording Integration
Establishing active, persistent recording sessions via standard SIPREC.
CXMind operates as a standard SIP Recording Server (SRS). If your primary Session Border Controller (SBC), such as Oracle/Acme Packet, AudioCodes, Ribbon, or Cisco, supports SIPREC, you can establish an active, persistent recording session for every call.
compare_arrows SIPREC vs. HEP
Unlike HEP (Homer), which passively mirrors underlying network packets, SIPREC is an active architectural integration.
- Active Integration: In a SIPREC environment, the Recording Client (SRC, typically your SBC) dynamically establishes a dedicated SIP session for every call, targeting CXMind’s SIPREC listener on port
5060. - Reliability: Because SIPREC is session-based, it provides superior signaling integrity and media stream control compared to raw packet mirroring.
Architectural Flow
The SRC intercepts an established session between the caller and the agent and determines the recording requirement based on predefined policies.
The SRC generates an XML-based metadata payload (compliant with RFC 7865) containing session participant identities, call IDs, directionality, and precise timestamps.
The SRC sends a multipart INVITE to CXMind’s Ingestion Engine containing:
- XML Metadata: Describing the context of the conversation.
- SDP Details: Describing the dual RTP audio streams (typically a stereo feed representing both legs of the call).
The Ingestion Engine processes the SDP and automatically allocates DSP thread pool resources to mix and decode the RTP. It natively supports G.711 μ-law/A-law, G.722, G.729, and Opus, delivering the normalized PCM arrays to the ASR clusters for real-time transcription.
Core Advantages
Unlike single-channel packet captures, SIPREC guarantees perfect separation of agent and customer audio, drastically improving ASR accuracy.
By transmitting only specific recording streams rather than mirroring entire network segments, SIPREC significantly reduces the backplane load on core switches.
Adherence to IETF standards ensures seamless interoperability within multi-vendor hybrid SBC environments.
Need more help or have a specific architecture question?
Contact Engineering Support