Home / Open-source telephony core / rtpengine and the integration map
rtpengine and the integration map
rtpengine proxies RTP, rewrites SDP, and can bridge ICE and SRTP. It runs on GNU/Linux and is meant to sit with Kamailio.
Learn in 5 minutes
- List media features the README states
- Draw the SIP server beside the media proxy
- Keep kernel forwarding as an optimization the README describes
Visual
SIP stays on Kamailio. RTP can be forwarded by rtpengine, in kernel or in userspace.
Worked example
Read the rewritten c= line The offer points at the phone. The answer points at the proxy. That is the anchoring idea.
- Negotiate.
- Compare c=.
- Say which address the caller will send RTP toward.
Fault
The kernel module failed to load. RTP still flows. An alarm says rtpengine is dead because kernel forwarding is off.
Fallback to userspace is a documented behavior, not proof the process exited.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
CRM Screen pop uses data the contact center already has: ANI, DNIS, case id. Those values may arrive in SIP headers or in a CTI event after the call is up. The CRM is not a SIP element.
Sources and go deeper
- rtpengine README — last checked 2026-10
- RFC 8445 — last checked 2026-10
- RFC 5764 — last checked 2026-10
- Kamailio SIP server — last checked 2026-10
- Asterisk res_pjsip configuration — last checked 2026-10
- RFC 3264 — last checked 2026-10