<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>9ne.pl — knowledge base</title>
  <id>https://9ne.pl/en/knowledge/</id>
  <link href="https://9ne.pl/en/knowledge/" />
  <link href="https://9ne.pl/en/atom.xml" rel="self" type="application/atom+xml" />
  <updated>2026-08-07T08:00:00Z</updated>
  <author><name>Jarosław Staroń</name><uri>https://9ne.pl/en/</uri></author>
  <entry>
    <title>WebRTC, ICE, STUN and TURN explained</title>
    <id>https://9ne.pl/en/knowledge/webrtc-ice-stun-turn/</id>
    <link href="https://9ne.pl/en/knowledge/webrtc-ice-stun-turn/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="webrtc-media" label="WebRTC and media" />
    <summary>How the browser chooses a media path, why a public candidate is not always enough and when TURN is necessary for a reliable connection.</summary>
  </entry>
  <entry>
    <title>Technical incident RCA — from symptom to lasting correction</title>
    <id>https://9ne.pl/en/knowledge/technical-incident-root-cause-analysis/</id>
    <link href="https://9ne.pl/en/knowledge/technical-incident-root-cause-analysis/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="diagnostyka" label="Diagnostics" />
    <summary>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.</summary>
  </entry>
  <entry>
    <title>How to plan a PBX migration without uncontrolled downtime</title>
    <id>https://9ne.pl/en/knowledge/pbx-migration-without-disruption/</id>
    <link href="https://9ne.pl/en/knowledge/pbx-migration-without-disruption/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="voip-sip" label="VoIP and SIP" />
    <summary>A telephony platform migration needs parallel plans for configuration, registrations, routing, media, numbering, carriers and user behaviour.</summary>
  </entry>
  <entry>
    <title>One-way audio in VoIP — NAT, RTP, SDP and firewalls</title>
    <id>https://9ne.pl/en/knowledge/one-way-audio-voip/</id>
    <link href="https://9ne.pl/en/knowledge/one-way-audio-voip/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="voip-sip" label="VoIP and SIP" />
    <summary>One-way audio is not a single problem. It is a class of failures involving signalling, address translation, media routing, ACLs and device behaviour.</summary>
  </entry>
  <entry>
    <title>How to read a SIP trace and identify why a call fails</title>
    <id>https://9ne.pl/en/knowledge/how-to-read-a-sip-trace/</id>
    <link href="https://9ne.pl/en/knowledge/how-to-read-a-sip-trace/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="voip-sip" label="VoIP and SIP" />
    <summary>A practical method for analysing SIP signalling: from Call-ID and transactions, through routing and headers, to SDP, media and a precise RCA.</summary>
  </entry>
  <entry>
    <title>Docker behind Nginx — TLS, health checks and predictable rollback</title>
    <id>https://9ne.pl/en/knowledge/docker-nginx-tls-healthcheck-rollback/</id>
    <link href="https://9ne.pl/en/knowledge/docker-nginx-tls-healthcheck-rollback/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="linux-infrastruktura" label="Linux and infrastructure" />
    <summary>A lightweight production architecture for a web application: a locally accessible container, host Nginx, a certificate, readiness, versioned images and automatic rollback.</summary>
  </entry>
  <entry>
    <title>A safe production server migration, step by step</title>
    <id>https://9ne.pl/en/knowledge/safe-production-server-migration/</id>
    <link href="https://9ne.pl/en/knowledge/safe-production-server-migration/" />
    <published>2026-08-07T08:00:00Z</published>
    <updated>2026-08-07T08:00:00Z</updated>
    <category term="linux-infrastruktura" label="Linux and infrastructure" />
    <summary>Migration does not start with copying files. It starts with an inventory, dependencies, acceptance criteria and a practical way back.</summary>
  </entry>
</feed>
