Hi Kamailio community,
I've published something unusual: a philosophy course for VoIP engineers.
*"Philosophy of VoIP Infrastructure: Why Your Technical Decisions Are
Philosophical"*
Not "professional ethics 101." This is Plato, Foucault, Heidegger, and
Bergson applied to actual Kamailio/RTPEngine problems.
*Example:* The CAP theorem isn't just a technical limitation—it's the
same debate Parmenides and Heraclitus had 2500 years ago about the
nature of reality. Understanding this won't change your kamailio.cfg,
but it will change how you think about consistency vs availability
trade-offs.
*Four modules:*
- Ontology (what exists: protocols, containers, distributed state)
- Epistemology (how we know: logs as testimony, Lamport timestamps,
debugging biases)
- Ethics (who benefits: power relations in centralized vs distributed
architectures)
- Temporality (lived vs measured time: jitter buffer as phenomenology)
Each connects philosophical concepts with concrete VoIP code examples.
It's completely free. Available in English and Spanish.
Link: https://campus.mesaproyectos.com/course/view.php?id=53
*Warning:* This won't make you configure Kamailio faster. It will give
you conceptual clarity that no RFC provides. If you're looking for a
technical tutorial, this isn't it.
If you've ever wondered why certain "technical" decisions feel
philosophical, this course is for you.
Feedback welcome.
--
---
I'm SoCIaL, MayBe
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions --
[email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
