LinphoneLINPHONEJOURNAL D'ACTUALITÉS · ENGLISH EDITION
No. 012 · November 2026
ENGLISH EDITION
Brand Story

Twenty-five years of open-source telephony: how Linphone survived

Most open-source communications projects that started at the same time have stopped shipping. Linphone's survival has little to do with code quality.

2026-09-25 · Editorial Desk · approx. 8 min read

Quite a few open-source communications projects started in 2001. Twenty-five years later, very few are still releasing, still have enterprise customers and still have maintainers. Linphone is one of them.

Starting point: one person wanting SIP to work

The project began as a research exercise — a SIP client implemented on Linux. Once the code was open, users spread from researchers to telecom engineers, and the requirements grew complicated: video, cross-platform, interoperability with every kind of enterprise switch.

That pattern of users dragging the project forward shaped its architecture. It is not a carefully designed product but a stack built up layer by layer from real requirements.

The key step: founding a company

The most common way an open-source project dies is maintainer exhaustion. Belledonne Communications turned maintenance into something with revenue behind it: commercial support, custom development, server products, white-label licensing. The project continued because people were paid to keep it going.

The lifespan of an open-source project is usually equal to the number of people who can draw a salary from it.

Three things it got right

Sticking to standards. No private protocol was invented; everything sits on SIP. That makes interoperability automatic and means customers can change supplier without changing endpoints.

Building the whole stack. From SDK to client to server, every link in the chain is covered, because what customers need is not a client but a system that runs.

Accepting that it is not exciting. No growth hacking, no channel programme, an interface that has stayed plain for decades. And yet it appears in a great many places that need reliable, auditable, customisable telephony.

The challenges now

Like every traditional communications product, it faces a market reshaped by cloud services and consumer apps. Users expect to open the app and start, not to configure a server address first. The open-source answer is to hide the complexity at the service-provider layer — which is exactly why the white-label business keeps growing.

The other challenge is people. Engineers who know SIP are becoming scarcer, and those willing to maintain a C communications stack for years are scarcer still. That is not one vendor's problem; it is the whole real-time communications industry's.

Brand HistoryBelledonneOpen Source
Linphone Journal · No. 012Back to contents