A high-performance RTP and media traffic proxy designed for Kamailio SIP proxy, supporting IPv4/IPv6 bridging, SRTP, ICE, and in-kernel packet forwarding.
Rtpengine is a media proxy for RTP and UDP-based traffic, designed to work with the Kamailio SIP proxy. It handles real-time media streams in VoIP systems, providing features like IPv4/IPv6 bridging, SRTP encryption, ICE support, and transcoding. It solves the problem of managing complex media routing, security, and compatibility in SIP-based communication networks.
Telecommunications engineers, VoIP system administrators, and developers building or maintaining SIP-based real-time communication platforms, especially those using Kamailio.
Developers choose rtpengine for its high performance with in-kernel packet forwarding, extensive protocol support (SRTP, ICE, RTP/AVPF), and seamless integration as a drop-in replacement for other media proxies, reducing deployment complexity.
The Sipwise media proxy for Kamailio
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
In-kernel packet forwarding provides low-latency, low-CPU media handling with automatic fallback to userspace, as detailed in the README's features for high-performance scenarios.
Includes SRTP with SDES and DTLS-SRTP, ICE bridging, and support for RTP/AVPF profiles, making it versatile for secure and complex VoIP environments.
Designed as a drop-in replacement for rtpproxy and mediaproxy, it integrates directly with Kamailio modules, reducing deployment effort in SIP-based systems.
Offers transcoding, DTMF handling, recording, and media forking, enabling sophisticated media processing as highlighted in the README's feature list.
Limited to GNU/Linux platforms, excluding deployment on Windows, macOS, or other operating systems, which narrows its applicability.
The README explicitly states that ZRTP is not supported, creating a gap for end-to-end encrypted communication without SRTP alternatives.
Optimal performance depends on a kernel module, adding installation and maintenance complexity compared to pure userspace proxies.