Flexisip

Open-source VoIP infrastructure, honestly reviewed. Built for telecom engineers, not spreadsheet-averse founders.

TL;DR

• What it is: Open-source (AGPL-3.0) SIP server suite — proxy, presence, conference, push gateway, and B2BUA in a single C++ stack. The same software that has run linphone.org since 2011 [1][4].
• Who it’s for: Telecom operators, IoT/intercom manufacturers, VoIP platform builders, and embedded systems engineers. Emphatically not a tool you point a non-technical founder at on a Tuesday afternoon.
• Cost savings: The license is free under AGPL-3.0. But “free” here means no license fee — it does not mean low deployment cost. You’re building C++ from source or running Docker images, configuring SIP trunks, and managing Redis and MySQL. Commercial support and proprietary licensing are available from Belledonne Communications at quote-based pricing [1].
• Key strength: The most complete open-source SIP server suite for building a production-grade unified communications platform — proxy, push gateway, presence, conferencing, and PSTN bridging under one roof. Proven at scale: linphone.org has run on it for 14+ years [4].
• Key weakness: 179 GitHub stars is a market signal you shouldn’t ignore. This is infrastructure software for a narrow slice of operators. The documentation lives on linphone.org and is adequate for engineers, but there is no “deploy in 30 minutes” guide for normal humans. AGPL-3.0 means any embedded or SaaS use requires either open-sourcing your product or buying the commercial license [1].

---

What is Flexisip

Flexisip is a SIP (Session Initiation Protocol) server suite written in C++17, developed and maintained by Belledonne Communications — the French company behind the Linphone open-source softphone. The README describes it as “a comprehensive, modular and scalable SIP server suite” and the scope of that description holds up: this is not a single-purpose proxy, it’s a full stack for building SIP-based communication infrastructure [README][1].

The suite breaks into six functional components:

• Proxy Server — the core routing hub for all SIP messages, including a built-in NAT traversal module and ICE/STUN/TURN support [4]
• Push Notification Gateway — routes SIP calls and messages to iOS (APNs) and Android (FCM) devices when the app is backgrounded or closed [4]
• Presence Server — tracks and distributes online status across users [README]
• Conference Server — SFU-based group audio/video calls, screen sharing, multi-party instant messaging [2]
• B2BUA (Back-to-Back User Agent) — enables PSTN trunking, caller identity translation, and media transcoding [README]
• Account Manager — SIP user account provisioning and management (separate repository: Flexisip Account Manager) [website]

The project is backed by a real commercial company — Belledonne Communications offers server installation, configuration, annual maintenance contracts, rebranding, and custom development on top of the open-source codebase [website]. The free linphone.org SIP service has run on Flexisip since 2011, which is a meaningful proof point: this isn’t a science project [1][4].

GitHub numbers put it at 179 stars and 3,703 commits on the primary repository [1][3]. The low star count relative to the commit count tells you something true about this project: it has real production deployments but a tiny developer mindshare, because the people who run SIP infrastructure at scale aren’t browsing GitHub looking for automation tools.

---

Why people choose it

There are no mainstream review sites covering Flexisip — no G2 page, no Trustpilot score, no Reddit threads from founders complaining about Zapier pricing. The third-party coverage that exists [1][2][3][4] is either technical listings or VoIP platform comparisons, and that tells you everything about the target audience.

For telecom operators and VoIP platform builders, Flexisip fills a gap that Asterisk and FreeSWITCH don’t quite cover. The website explicitly calls out compatibility with Asterisk, FreeSWITCH, and Mitel for gradual migration [website]. The pitch is: deploy Flexisip alongside your existing SIP infrastructure, migrate users incrementally, and gain push notification support and modern SIP RFC compliance without ripping out existing PBX hardware.

For IoT and intercom manufacturers, the embedded deployment story is unusually strong. Flexisip runs on a Raspberry Pi. It supports Early Media Call Forking — the feature that lets you see the caller’s video preview before accepting the call — which is specifically cited by Linhome as the reason intercom and access control manufacturers choose it [4]. The modular architecture means you can compile only the components you need, keeping the binary footprint small enough for embedded Linux hardware [4].

For organizations using Linphone, the pairing is obvious: Linphone client + Flexisip server is a self-contained, end-to-end encrypted VoIP and messaging stack under one vendor. The Tragofone comparison review [2] describes it as: “Teams that want a privacy-first, customizable SIP stack for calling, enforce specific encryption choices, run standards-based push, and own the server side.” That’s the use case in a sentence.

What Flexisip is not is a Zoom alternative you deploy for your 20-person startup. The conference server component can do group calls, but the configuration surface is C++ compile flags and SIP RFC compliance tables — not a Jitsi-style web interface.

---

Features

Based on the README, official website, and third-party sources:

Core SIP proxy:

• Transport: SIP/UDP, SIP/TCP, SIP/TLS [4]
• NAT traversal with built-in media relay, ICE, STUN, and TURN [4]
• Authentication: SIP Digest and TLS client certificates [4]
• High availability and cluster mode with Redis as the shared registrar database [README]
• Load balancing for large-scale deployments [website]
• Multicast DNS (mDNS) for simplified SIP network discovery in embedded environments [4]

Push notifications:

• Integration with APNs (Apple) and FCM (Google/Firebase) [4]
• Push gateway can sit in front of legacy SIP servers that don’t natively support push [4]
• Designed for mobile apps that are backgrounded or inactive [1]

Conference and messaging:

• SFU-based group audio/video calls [2]
• Screen sharing and file sharing in multi-party sessions [2]
• Multi-party instant messaging [website]

B2BUA:

• PSTN trunking (SIP-to-PSTN gateway) [README]
• Caller identity translation [README]
• Media transcoding [README]
• SIP trunking for connecting to traditional telephony [README]

Presence server:

• Online/offline status distribution across users [README]
• Requires XercesC XML parser at compile time [README]

Account Manager:

• SIP account provisioning (separate repository) [website]
• Remote configuration delivery for fleet management [2]

Encryption:

• TLS for signaling (OpenSSL required) [README]
• SRTP for media via libsrtp2 [README]
• LIME end-to-end encryption when paired with Linphone client [2]
• Post-quantum key exchange option (via Linphone ecosystem) [2]

Deployment:

• Docker images available [1][3]
• RPM and DEB packaging supported [README]
• Embedded Linux / Raspberry Pi deployable [4]
• Horizontal scaling via Redis-backed cluster mode [README]

---

Pricing: SaaS vs self-hosted math

This is where the honest answer is “data not fully available” — and that matters.

Open-source tier (AGPL-3.0):

• License cost: $0
• You must open-source any modifications you distribute, and any SaaS built on top is subject to AGPL copyleft obligations [1]
• Infrastructure cost: a $5–20/mo VPS if you’re running a small deployment; real hardware or a Kubernetes cluster if you’re running a service for thousands of users

Commercial / proprietary license:

• Available from Belledonne Communications for closed-source projects [1][README]
• Pricing: contact sales. No public numbers anywhere in the sourced materials.
• Includes options for: server installation and configuration, annual maintenance contracts, custom development [website]

What you’re replacing: Flexisip doesn’t replace Zoom, Slack, or a UCaaS vendor in the way that an Activepieces replaces Zapier. It replaces one of these:

• A commercial SIP proxy (Kamailio with commercial support, Cisco UCM, Avaya) — these run $10K-$100K+ annually at scale
• An outsourced VoIP platform build — custom SIP infrastructure from a telecom integrator
• A managed VoIP service for an IoT product line

If you’re an IoT company that would otherwise pay a VoIP platform vendor per-device per-year for push notification delivery, replacing that with a self-hosted Flexisip deployment can mean significant savings. The math depends entirely on your volume, and Belledonne doesn’t publish it. Contact them.

For a solo founder or small team: Flexisip is not the right tool regardless of price. The deployment complexity is not the bottleneck — the fundamental question is wrong. If you need team calling, use Jitsi Meet. If you need SIP trunking for a phone number, use Twilio or a VoIP provider. Flexisip is for building those services, not using them.

---

Deployment reality check

The install story for Flexisip is not friendly to non-engineers, and the third-party sources don’t pretend otherwise.

Easiest path: Docker. Docker images are available and this is the recommended approach for anyone who doesn’t want to compile C++ from source [1][3]. You’ll still need to configure the suite — proxy routing rules, push notification credentials, Redis/MySQL connection strings — but the build step is handled.

Harder path (production deployments): Compile from source with CMake. The dependencies include OpenSSL, LibNgHttp2, libsrtp2, SQLite3, MySQL client, and optionally Redis (Hiredis), SNMP (NetSNMP), XML (XercesC), JSON (jsoncpp), and JWT support. Your C++ compiler needs to be GCC >= 13.0 or Clang >= 19.0 for C++20 support — on Debian 12, only Clang is officially supported because the default GCC is too old [README]. This is not a point-and-click operation.

What you actually need for a working deployment:

• Linux server with at least 2–4 GB RAM
• Docker (simplest) or a full C++ build environment
• MySQL or PostgreSQL for account storage
• Redis for the registrar database and cluster coordination (optional but recommended for HA)
• SIP domain and DNS SRV records
• TLS certificates for SIP/TLS transport
• APNs and FCM credentials if you want push notifications
• A reverse proxy if you’re exposing the account manager’s HTTP API

What can go sideways:

• The documentation is on linphone.org and is aimed at engineers already familiar with SIP. There is no “beginners guide” [website]
• SIP NAT traversal is notoriously painful in any implementation. Flexisip has ICE/STUN/TURN support but you’ll spend time debugging RTP media path issues if your network isn’t straightforward
• AGPL-3.0 has commercial implications that require a legal read if you’re building a product on top of it. The dual-licensing model exists precisely because this comes up constantly [1][README]
• 179 stars means a small community. If you hit a non-obvious bug, you’re likely opening an issue on GitLab or emailing Belledonne Communications directly — not finding a Stack Overflow answer [1]

Realistic time estimate for an experienced VoIP engineer: 4–8 hours from zero to a working Docker-based deployment with basic proxy and push notifications configured. For a developer new to SIP: budget multiple days and a copy of RFC 3261.

---

Pros and Cons

Pros

• Battle-tested at scale. The linphone.org SIP service has run on Flexisip since 2011. This is not vaporware — it handles real users at production volume [1][4].
• Full-stack SIP suite. Proxy, presence, conferencing, push gateway, B2BUA, and account management in a single coordinated suite. Most open-source SIP tools are single-purpose; Flexisip covers the whole platform [README][website].
• Embedded deployment story. Runs on Raspberry Pi, designed for IoT and intercom hardware. Early Media Call Forking for video doorbells is a genuine differentiator [4].
• Push notification integration. Native APNs and FCM support, including a push gateway mode that can sit in front of existing SIP infrastructure that doesn’t support push [4].
• High availability and clustering. Redis-backed cluster mode, load balancing for large deployments — not a toy [README][website].
• Commercial support available. Belledonne Communications offers real support contracts, installation services, and custom development. This is not an abandoned hobby project [website].
• Dual licensing. AGPL-3.0 for open-source use, commercial license for proprietary products. The model is clear [1][README].
• SIP RFC compliance. The website lists supported RFCs explicitly and claims compatibility with Asterisk, FreeSWITCH, and Mitel for coexistence deployments [website].

Cons

• 179 GitHub stars. The community is tiny. Finding answers outside official documentation means contacting Belledonne [1]. Compare to Kamailio (2K+ stars, massive community) or FreeSWITCH (3K+ stars) — both with much larger ecosystems.
• C++ compile complexity. Source builds require a modern GCC (>= 13) or Clang (>= 19), CMake, multiple system libraries, and SIP domain knowledge. Docker simplifies it but doesn’t eliminate the configuration burden [README].
• No web UI for non-engineers. There is no dashboard, no click-to-configure interface. Everything is config files and SIP routing rules [website].
• AGPL-3.0 copyleft. For any commercial product embedded or built on top of Flexisip, you either open-source your product or buy the proprietary license. This is not a permissive license like MIT [1][README].
• Commercial license pricing opaque. No public numbers for the proprietary license or support contracts. You’ll spend time in a sales conversation before knowing the cost [1].
• Niche documentation. The docs assume SIP familiarity. There’s no onboarding for developers who haven’t worked with SIP before [website].
• Not a drop-in SaaS replacement. This doesn’t replace Zoom, Slack, or Microsoft Teams for a typical business. It’s infrastructure for building or running VoIP services, not consuming them.

---

Who should use this / who shouldn’t

Use Flexisip if:

• You’re building or running a VoIP or messaging platform and need a battle-tested SIP proxy at the core.
• You’re an IoT or intercom hardware manufacturer who needs SIP proxy + push notifications + embedded deployment on a single codebase.
• You’re already running Linphone clients and want a matching server-side stack from the same vendor.
• You’re migrating from a legacy Asterisk or FreeSWITCH deployment and need a modern C++ SIP server that can coexist alongside it.
• You need push notification delivery for mobile SIP apps and don’t want to build the APNs/FCM gateway yourself.
• You’re a telecom operator or MVNO building a white-label communication service and need commercial support backing an open-source core.

Skip it (use Jitsi Meet) if:

• You want to replace Zoom for your team with minimal setup. Jitsi deploys in an afternoon with Docker Compose and has a real web UI.

Skip it (use Asterisk or FreeSWITCH) if:

• You need a PBX with broad community documentation, thousands of Stack Overflow answers, and decades of production case studies. Both have far larger ecosystems.

Skip it (use a hosted SIP provider) if:

• You need SIP trunking for phone numbers without running your own infrastructure. Twilio, Vonage, or Telnyx give you this without any server management.

Skip it (use Kamailio) if:

• You need a highly extensible SIP proxy with a massive community and extensive third-party module ecosystem. Kamailio has more stars, more modules, and more deployment documentation for pure proxy use cases.

Skip it entirely if:

• You’re a non-technical founder who saw “open-source VoIP” and thought this would save money on Zoom. It won’t — not without a VoIP engineer on staff or a significant budget for Belledonne’s professional services.

---

Alternatives worth considering

Based on the third-party sources and the SIP server landscape:

• Kamailio — the most widely deployed open-source SIP proxy. Larger community, more modules, GPL license. More complex configuration syntax (Kamailio scripting language) but better ecosystem documentation. Choose Kamailio if you’re building a pure proxy/registrar without needing the full Flexisip suite.
• FreeSWITCH — open-source softswitch focused on media handling, IVR, conferencing, and PSTN bridging. Larger star count, broader community, MPL license. Choose FreeSWITCH if your primary need is voice conferencing or PSTN integration rather than SIP routing.
• Asterisk — the original open-source PBX. GPL licensed, massive community, extensive commercial support ecosystem. Less modern than Flexisip for mobile/push-native deployments but unmatched documentation depth.
• Routr — listed alongside Flexisip on hostedsoftware.org [3]. Lightweight SIP proxy and registrar under MIT license. 5K stars, Kubernetes-native, more developer-friendly for modern deployments. Choose Routr if you want a lighter-weight proxy without the full Flexisip suite.
• Jitsi Meet — open-source video conferencing, Apache license, Docker deployable in an afternoon. Not a SIP server but covers the “we need video calls without Zoom” use case for non-technical teams.
• FusionPBX — FreeSWITCH with a web UI (MPL-1.1, 23K+ stars on the comparison listing) [3]. If you want a FreeSWITCH-based PBX with a point-and-click configuration interface, FusionPBX is the route.
• Linphone (client only, without Flexisip) — for teams that just need a cross-platform SIP client with end-to-end encryption and no server to run [2].

For organizations in the embedded/IoT space specifically, Flexisip has few real competitors that cover push notifications and embedded deployment in the same package. That’s the strongest reason to choose it over the alternatives.

---

Bottom line

Flexisip is serious infrastructure software built by a serious company, and it’s genuinely good at what it does. The 14-year production history at linphone.org is more credibility than most open-source projects ever accumulate. If you’re building a SIP-based communication platform, a white-label VoIP service, or an intercom product that needs push notifications on embedded hardware, Flexisip is worth a serious evaluation — especially because the commercial license option means you can get professional deployment support from the team that wrote the code.

But for the typical unsubbed.co reader — a non-technical founder trying to cut a SaaS bill — Flexisip is a category error. This isn’t a Zoom replacement or a Slack alternative. It’s the server software that VoIP providers build their services on. You’d be better served by Jitsi Meet for video, Matrix/Element for messaging, or simply a hosted SIP provider for phone calls. The self-hosting benefit of Flexisip is real, but it only materializes if you already know what SIP is and have a reason to operate your own telephony infrastructure.

---

Sources

1. Libre Self-hosted — Flexisip project listing (libreselfhosted.com). https://www.libreselfhosted.com/project/flexisip/
2. Tragofone — “Tired of Zoiper’s Glitches? Top 6 Zoiper Alternatives in 2025” (tragofone.com). https://tragofone.com/top-zoiper-alternatives-android-ios-windows-mac-linux/
3. Hosted Software — Flexisip (hostedsoftware.org). https://hostedsoftware.org/tools/flexisip/
4. Linhome — Flexisip SIP proxy server (linhome.org). https://www.linhome.org/software-products/flexisip/
5. Awesome Selfhosted HTML listing (open-source.world). https://open-source.world/github.com__awesome-selfhosted__awesome-selfhosted-html/

Primary sources:

• GitHub repository (mirror): https://github.com/belledonnecommunications/flexisip (179 stars, AGPL-3.0)
• Official source repository: git://git.linphone.org/flexisip.git
• Official website and feature documentation: https://www.linphone.org/en/flexisip-sip-server/