← Back to home
Comparison · Meetings

FreeSWITCH vs mediasoup

A side-by-side editorial comparison of FreeSWITCH and mediasoup — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:webrtc

FreeSWITCH vs mediasoup: at a glance

FeatureFreeSWITCHmediasoup
SectorMeetingsMeetings
Velocity score2.56.3
Sparks · 30d01
Top themesvoip, telephony, security-hardening, legacy-removalwebrtc, sfu, rtcp, capture-time-sync
Last editorial update9d ago1d ago
WebsiteVisit →Visit →

What is FreeSWITCH?

With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes

FreeSWITCH shipped 1.11.2 in August 2026, three months after the 1.11.0 branch cut that removed roughly thirty modules and migrated the regex engine to PCRE2. Where 1.11.0 was about deleting surface area, 1.11.2 is about auditing what remains: nearly every bug line is a bounds or length check in a parser — STUN attributes, base64 decode, XML entity decoding, RTMP H.264 NAL units, XML-RPC WebSocket frames, MSRP body lengths. Alongside the fixes it adds an interface allowlist and turns on DTLS client-certificate verification against the SDP fingerprint plus opt-in STUN MESSAGE-INTEGRITY checks on inbound ICE. The build system continues moving off self-hosted infrastructure onto GitHub-published artifacts and upstream packages.

Read the full FreeSWITCH trajectory →

What is mediasoup?

After weeks of one-line subchannel patches, mediasoup rebuilt its RTCP timing model.

The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.

Read the full mediasoup trajectory →

FreeSWITCH vs mediasoup: editorial side-by-side

F
FreeSWITCH
MEETINGS
2.5

With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes

◆ Current state

FreeSWITCH shipped 1.11.2 in August 2026, three months after the 1.11.0 branch cut that removed roughly thirty modules and migrated the regex engine to PCRE2. Where 1.11.0 was about deleting surface area, 1.11.2 is about auditing what remains: nearly every bug line is a bounds or length check in a parser — STUN attributes, base64 decode, XML entity decoding, RTMP H.264 NAL units, XML-RPC WebSocket frames, MSRP body lengths. Alongside the fixes it adds an interface allowlist and turns on DTLS client-certificate verification against the SDP fingerprint plus opt-in STUN MESSAGE-INTEGRITY checks on inbound ICE. The build system continues moving off self-hosted infrastructure onto GitHub-published artifacts and upstream packages.

◆ Where it's heading

The 1.11.x line reads as a deliberate two-step: cut the maintenance surface, then harden what is left. Having removed thirty modules, the project can now afford to audit the media and signaling paths line by line, and the pattern of fixes — untrusted length fields reaching memory writes — suggests a systematic pass rather than incremental reports. The parallel thread is dependency modernization: mod_v8 moved from a custom v8-6.1 fork to upstream libnode, SpanDSP and libvpx were bumped, and Windows builds now pull pre-compiled FFmpeg and libcodec2 rather than building them. Both threads point the same direction — less bespoke code to own.

◆ Prediction

Expect the hardening pass to continue into the remaining parsers, with the opt-in STUN MESSAGE-INTEGRITY check becoming default once operators have shipped through a release. The build-system migration off files.freeswitch.org appears partway done, so the next release likely finishes moving the remaining assets to GitHub-hosted artifacts.

M
mediasoup
MEETINGS
6.3

After weeks of one-line subchannel patches, mediasoup rebuilt its RTCP timing model.

◆ Current state

The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.

◆ Where it's heading

Two threads run through this window: finishing the subchannel mechanism so pipe transports behave like direct ones, and tightening timing correctness in the media path. The new RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator classes, plus abs-capture-time rewriting in the simulcast manager, are foundations rather than endpoints — they give the worker a notion of remote capture instants it did not previously have. Expect that foundation to be used by more than Sender Reports.

◆ Prediction

The capture-time estimators look like groundwork for synchronization and delay features beyond Sender Reports; the near-term releases will likely be fixes shaking out the new timing path across simulcast and pipe transports.

Alternatives to FreeSWITCH and mediasoup

Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either FreeSWITCH or mediasoup.

See all FreeSWITCH alternatives → · See all mediasoup alternatives →

Recent activity from FreeSWITCH and mediasoup

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agomediasoupmediasoup rebuilds RTCP Sender Reports around media capture time
  2. 8d agomediasoupmediasoup verifies DataConsumer subchannels before cloning
  3. 9d agoFreeSWITCHInterface allowlist lands with a broad memory-safety sweep
  4. 12d agomediasoupmediasoup stops checking ignoredSubchannel on piped DataConsumers
  5. 15d agomediasoupmediasoup adds ignored_subchannel to DirectDataProducer.send
  6. 19d agomediasoupmediasoup makes DataProducerOptions::new_pipe_transport public
  7. 20d agomediasoupmediasoup handles subchannels in pipe DataConsumers
  8. 2mo agoFreeSWITCHHot TLS certificate reloads and SIP 603 passthrough
  9. 3mo agoFreeSWITCHPCRE2, OpenSSL 3 on Windows, and thirty legacy modules removed
  10. 2y agoFreeSWITCHARM64 support arrives, Debian 10 and CentOS dropped
  11. 2y agoFreeSWITCHCoverity fixes and a sofia-sip version bump
  12. 3y agoFreeSWITCHDebian 12, OpenSSL 3 and FFmpeg 5 support

Frequently asked questions

What is the difference between FreeSWITCH and mediasoup?

Both compete on the same themes — webrtc — within Meetings. mediasoup is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is FreeSWITCH better than mediasoup?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mediasoup is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.

What are the best alternatives to FreeSWITCH?

Top FreeSWITCH alternatives in Meetings are ranked by recent ship velocity. Browse the "FreeSWITCH alternatives" section above for the current picks, or visit /alternatives/freeswitch for the full list with editorial commentary on each.

What are the best alternatives to mediasoup?

Top mediasoup alternatives in Meetings are ranked by recent ship velocity. Browse the "mediasoup alternatives" section above for the current picks, or visit /alternatives/mediasoup for the full list with editorial commentary on each.