<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>9ne.pl — knowledge base</title>
    <link>https://9ne.pl/en/knowledge/</link>
    <description>Practical guides to VoIP, SIP, WebRTC, Linux, deployments and diagnostics.</description>
    <language>en</language>
    <lastBuildDate>Fri, 07 Aug 2026 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://9ne.pl/en/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WebRTC, ICE, STUN and TURN explained</title>
      <link>https://9ne.pl/en/knowledge/webrtc-ice-stun-turn/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/webrtc-ice-stun-turn/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>WebRTC and media</category>
      <description>How the browser chooses a media path, why a public candidate is not always enough and when TURN is necessary for a reliable connection.</description>
    </item>
    <item>
      <title>Technical incident RCA — from symptom to lasting correction</title>
      <link>https://9ne.pl/en/knowledge/technical-incident-root-cause-analysis/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/technical-incident-root-cause-analysis/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>Diagnostics</category>
      <description>A good RCA does not seek someone to blame or merely recount events. It connects evidence, the failure mechanism, impact, correction and actions that prevent recurrence.</description>
    </item>
    <item>
      <title>How to plan a PBX migration without uncontrolled downtime</title>
      <link>https://9ne.pl/en/knowledge/pbx-migration-without-disruption/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/pbx-migration-without-disruption/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>VoIP and SIP</category>
      <description>A telephony platform migration needs parallel plans for configuration, registrations, routing, media, numbering, carriers and user behaviour.</description>
    </item>
    <item>
      <title>One-way audio in VoIP — NAT, RTP, SDP and firewalls</title>
      <link>https://9ne.pl/en/knowledge/one-way-audio-voip/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/one-way-audio-voip/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>VoIP and SIP</category>
      <description>One-way audio is not a single problem. It is a class of failures involving signalling, address translation, media routing, ACLs and device behaviour.</description>
    </item>
    <item>
      <title>How to read a SIP trace and identify why a call fails</title>
      <link>https://9ne.pl/en/knowledge/how-to-read-a-sip-trace/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/how-to-read-a-sip-trace/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>VoIP and SIP</category>
      <description>A practical method for analysing SIP signalling: from Call-ID and transactions, through routing and headers, to SDP, media and a precise RCA.</description>
    </item>
    <item>
      <title>Docker behind Nginx — TLS, health checks and predictable rollback</title>
      <link>https://9ne.pl/en/knowledge/docker-nginx-tls-healthcheck-rollback/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/docker-nginx-tls-healthcheck-rollback/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>Linux and infrastructure</category>
      <description>A lightweight production architecture for a web application: a locally accessible container, host Nginx, a certificate, readiness, versioned images and automatic rollback.</description>
    </item>
    <item>
      <title>A safe production server migration, step by step</title>
      <link>https://9ne.pl/en/knowledge/safe-production-server-migration/</link>
      <guid isPermaLink="true">https://9ne.pl/en/knowledge/safe-production-server-migration/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 +0000</pubDate>
      <category>Linux and infrastructure</category>
      <description>Migration does not start with copying files. It starts with an inventory, dependencies, acceptance criteria and a practical way back.</description>
    </item>
  </channel>
</rss>
