FEATUREDLatestOpenSIPSTOP STORIESVOIPWebRTC

OpenSIPS vs Kamailio: How the Two SIP Servers Differ

OpenSIPS and Kamailio are the two best-known open-source SIP servers. Both are used as SIP proxies, registrars, load balancers and the front end of large VoIP platforms. They share a common ancestor, which is why they look alike, but they have been developed separately since 2008. This article sets out where they differ.

Shared history

Both projects descend from SIP Express Router (SER), developed at the Fraunhofer FOKUS institute and published under the GPL in 2002. OpenSER forked from SER in 2005. In 2008 OpenSIPS forked from OpenSER, and OpenSER was renamed Kamailio because of a trademark claim; Kamailio later merged its code base with SER. The Kamailio project history gives the dates.

Where they differ

  • Routing scripts. Both use their own configuration language to write SIP routing logic. Since version 5.0, Kamailio can also run that logic in embedded languages through its KEMI framework, including Lua, Python, JavaScript and Ruby; Kamailio has published performance tests of the KEMI languages. OpenSIPS has modules for calling Lua and Python from its script.
  • Built-in B2BUA and clustering. OpenSIPS includes a back-to-back user agent module and a clustering layer for sharing state between nodes, which suits it to building SBC-like services.
  • IMS. Kamailio has a large set of IMS modules, which is why it appears in mobile operator and VoLTE work.
  • Load balancing. Both have a dispatcher module; OpenSIPS also has a separate load_balancer module that takes call capacity into account.
  • Management. OpenSIPS publishes a Control Panel and a command-line tool for managing running instances; Kamailio uses its own command-line tools and RPC interface.

What they have in common

  • Both handle registration, authentication, NAT traversal, TLS and SIP over WebSocket for WebRTC clients.
  • Neither handles media itself. For WebRTC, both are normally paired with a media proxy such as rtpengine, which converts DTLS-SRTP to plain RTP, and clients on restrictive networks need a TURN server such as coturn.
  • Both have active mailing lists, regular releases and commercial support from companies that work on the projects.

Choosing

The choice usually depends on the team more than the software. If your engineers already know one of them, that is normally the right one. Kamailio’s embedded languages suit teams who would rather write routing logic in Lua or Python; OpenSIPS suits teams who want B2BUA functions and clustering in the same server. For WebRTC front ends, either works well with a media proxy.

For background, see our articles on what a SIP proxy is and the OpenSIPS Summit 2025. The Siperb knowledge base (published by the team behind SoftPage) explains how OpenSIPS works with WebRTC.


Corrected 18 November 2026: the earlier version reversed the scripting comparison (it is Kamailio that runs Lua, Python and JavaScript through KEMI), credited OpenSIPS with Kamailio’s dispatcher module, gave GitHub star counts and performance claims without sources, simplified the projects’ history, and used decorative emoji in the title and headings.

Leave a Reply

Your email address will not be published. Required fields are marked *