HEP Mode (Homer Protocol): Enterprise-Grade Ingestion
The gold standard ingestion method for centralized, multi-node contact centers.
HEP (Homer Encapsulation Protocol) is the gold standard for centralized, multi-node contact center ingestion. It provides a secure, structured method to duplicate SIP signaling and RTP media streams directly from your VoIP edge (SBCs, PBXs, Proxies) to the CXMind platform.
Why HEP?
Unlike traditional Port Mirroring or SPAN ports, HEP is an application-layer encapsulation protocol offering several strategic advantages:
Deeply integrated into industry-standard platforms including FreeSWITCH, Asterisk, Kamailio, and OpenSIPS.
Multiple edge proxies across different geographical regions can push traffic to a single, unified CXMind cluster simultaneously.
Traffic duplication occurs as a side-car process, ensuring zero impact on active call routing or latency-sensitive voice quality (QoS).
HEP v3 encapsulates raw packets with critical context, including precise timestamps, source/destination IPs, and protocol identifiers.
Encrypted HEP Transport Strategies
Standard HEP v3 typically utilizes unencrypted UDP. For architectures where data must traverse public or untrusted networks, CXMind supports the following secure transport layers:
vpn_lock WireGuard VPN
Establishes a lightweight, high-performance UDP tunnel between the PBX/Edge and the CXMind VPC. This method requires zero application-layer changes and maintains near-native performance.
lock TLS 1.3 Encryption
Runs HEP over TCP/TLS. By utilizing stunnel or HAProxy on the PBX side to wrap local UDP traffic, connections are terminated at CXMind's native TLS listener, ensuring total packet privacy.
Configuration Examples: Kamailio & OpenSIPS
loadmodule "siptrace.so"
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_version", 3)
modparam("siptrace", "duplicate_uri", "sip:cxmind_server_ip:9060")Need more help or have a specific architecture question?
Contact Engineering Support