LinphoneLINPHONEJOURNAL D'ACTUALITÉS · ENGLISH EDITION
No. 012 · November 2026
ENGLISH EDITION
BRAND · LA MAISON

Linphone: twenty-five years of open-source telephony from a French team

An open-source SIP suite from Belledonne in France: client, SDK and server, so the whole path from handset to backend stays under your control.

Editorial desk · updated 2026-11-01

Linphone is a SIP softphone that runs on phones and computers. Its purpose is plain: one account, any device, voice calls, video meetings and instant messaging. Its weight in European communications, though, is considerably more than 'a free app'.

It began as a research project

In 2001 the French engineer Simon Morlat started the Linphone project during his research, initially to get the SIP protocol running on Linux. Released under the GPL, it gradually gathered developers, a good share of them from telecom and the open-source community.

As the project grew, maintenance grew with it. To make that sustainable, the team founded Belledonne Communications around 2008, based in Grenoble, providing commercial support, custom development and server products around Linphone.

It is more than an app

Today Linphone usually refers to a suite:

  • Linphone Softphone — the end-user client, covering iOS, Android, Windows, macOS, Linux and the web.
  • Liblinphone — the core SDK, wrapping SIP signalling, media negotiation and call management into an API you can embed in any application.
  • Flexisip — the SIP proxy and server suite, handling registration, routing, push notification, conferencing and presence.
  • Mediastreamer2 — the media engine: capture, codecs, mixing, echo cancellation.
  • bcg729 — an open implementation of G.729, solving narrowband interoperability with the traditional telephone network.

Any open-source communications project that survives long enough ends up as a full stack, not an app.

Full brand profile →

THIS ISSUE · SOMMAIRE

20 November 2026 · 7 articles
01

How a white-label softphone actually gets built: Linphone's shortcut for carriers

Between Liblinphone and a shippable branded client the gap is not the interface. It is push notification, background keep-alive, codecs and compliance as one engineering package.

2026-11-16Product & Technology
02

After Adullact 2026: how 'digital sovereignty' reaches the telephone

At the French public-sector open-source congress, communications sovereignty came up repeatedly. It is not an abstract slogan but a list of requirements inside procurement terms.

2026-11-08Industry News
03

Flexisip: the inconspicuous but critical server in the Linphone suite

The client delivers the experience; the server decides whether calls connect at all. Understanding Flexisip's role is how you understand the true cost of a self-hosted SIP system.

2026-10-22Product & Technology
04

Liblinphone SDK: putting call capability inside your own app

A good SDK is not measured by API count but by whether it has wrapped up the messy business of mobile calling on your behalf.

2026-10-09Product & Technology
05

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-25Brand Story
06

G.729, Opus and end-to-end encryption: what really decides softphone audio

Users only care whether they can hear you. Underneath, codec choice, jitter buffering, echo cancellation and encryption are pulling in four directions at once.

2026-09-10Product & Technology
07

Why European public bodies increasingly prefer open communications: a procurement view

Not because it is cheaper and not out of idealism, but because 'replaceable' has entered the risk model.

2026-08-28Industry Watch
Linphone Journal · No. 012Compiled from public sources