<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kamailio on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/kamailio/</link>
    <description>Recent content in Kamailio on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/kamailio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted RTP Proxy Comparison: RTPengine vs RTPproxy vs Sippy B2BUA (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-17-rtp-proxy-rtpengine-rtpproxy-sippy-b2bua-voip-guide/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-17-rtp-proxy-rtpengine-rtpproxy-sippy-b2bua-voip-guide/</guid>
      <description>&lt;p&gt;When deploying a self-hosted VoIP or SIP infrastructure, the RTP (Real-time Transport Protocol) media path is just as critical as the SIP signaling path. An RTP proxy sits between the SIP proxy (Kamailio, OpenSIPS, Asterisk) and the media endpoints, handling NAT traversal, codec transcoding, media recording, and DTMF relay. In this guide, we compare three major open-source RTP media handling solutions: &lt;strong&gt;RTPengine&lt;/strong&gt;, &lt;strong&gt;RTPproxy&lt;/strong&gt;, and &lt;strong&gt;Sippy B2BUA&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
